Supported Drivers and Protocols
The sections in this topic summarize Geo SCADA Expert's driver support by both protocol and driver. Select the relevant heading to display the information in either protocol or driver order. Be aware that the Supported Drivers section also includes non-protocol drivers.
Supported Protocols
Use this topic alongside the corresponding Supported Drivers topic to find out about the protocols with which Geo SCADA Expert can interface and the Geo SCADA Expert drivers that exist to enable communications via those protocols.
With some open protocols, several Geo SCADA Expert drivers exist; typically a main driver designed to enable communications with protocol-compliant devices, along with ‘extension’ drivers that provide additional application-specific functionality for particular types of device. To run an extension driver, you also need to run the main driver, which acts as a ‘parent’ driver to the extension driver. Unless stated otherwise, the extension driver supports the same features as the parent driver, along with additional application-specific features and functionality.
With some protocols, both ‘advanced’ and ‘simple’ drivers exist. The advanced drivers provide more functionality than the simple drivers, such as support for extension drivers and more control over the way in which data is retrieved. As such, an advanced driver might take longer to initially set up than the simple driver equivalent. If both drivers provide the functionality you require, we recommend that you use the advanced driver rather than the simple driver. Using the advanced driver will give you more flexibility should your system requirements change in the future.
Regardless of the protocol or driver, if your system requires multiple similar configurations, remember that Geo SCADA Expert supports a comprehensive ‘Template’ and ‘Instance’ feature set to enable rapid configuration of like sections of the database. For more information, see Group Templates and Group Instances.
Listed below are the protocols for which Geo SCADA Expert supports one or more drivers, along with the names of those drivers.
For more information about a particular driver, select the link in the ‘Protocol Drivers’ column. This will take you to the introductory topic about that driver. With some drivers we also provide links to specific information in the ‘Further Information’ column.
Use this table in conjunction with the Supported Drivers table, which lists the entries by driver, rather than protocol, and provides information about several other drivers that Geo SCADA Expert supports.
| Protocol | Protocol Drivers | Driver Type | Intended Use | Further Information |
|---|---|---|---|---|
|
CFX |
For use with flow measurement data. Enables data to be exported for use in any of Flow-Cal’s measurement data management applications. |
|
||
|
DB2 |
Monitoring and processing of gas flow data via ABB Totalfow flow computers. |
|||
|
DF1 |
Enables communications with Allen-Bradley PLCs. |
|||
|
DNP3 |
Enables Geo SCADA Expert to communicate with other devices using the DNP3 protocol. The driver provides both master and slave functionality, and supports DNP3 Secure Authentication. When using the slave functionality, this driver uses Filtered Value Maps (rather than points) to represent I/O data address ranges. |
You can use this driver on its own, or as the ‘parent’ driver for DNP3 extension drivers. Use the ‘standard’ and ‘Generic’ DNP3 database items provided by this driver unless an extension driver provides application-specific functionality. |
||
|
Extension (of the DNP3 driver) |
Enables communications with SCADAPack E outstations. |
|||
|
Extension (of the DNP3 driver) |
Enables communications with field devices using the WITS-DNP3 protocol (one of the Worldwide Industrial Telemetry Standards). |
|||
| DNP3 T4 WITS | Extension (of the DNP3 WITS driver) | Enables full configuration of Schneider Electric Talus T4 RTUs without using a separate configuration application. | Documentation for the T4 WITS driver is separate to the Geo SCADA Expert documentation suite. Please see the Schneider Electric Talus T4 documentation for information. | |
|
Incorporated into the DNP3 Driver |
Enables Geo SCADA Expert to operate as a DNP3 outstation and report any changes back to another SCADA Master. |
|
||
| SCADAPack x70 | Extension (of the DNP3 driver) | Enables communications with SCADAPack x70 devices. | ||
|
EcoStruxure Web Services (EWS) |
EcoStruxure Web Services Client – Advanced (Known as the ‘Advanced EWS Driver’ in the online Help) |
Enables Geo SCADA Expert to read or write to data on other Schneider EWS servers. |
This Advanced driver provides additional functionality to the Simple driver, such as support for combined current data and historic data |
|
|
EcoStruxure Web Services Client – Simple (Known as the ‘Simple EWS Driver’ in the online Help) |
Enables Geo SCADA Expert to read or write to data on other Schneider EWS servers. |
|
||
| EtherNet/IP | EtherNet/IP | Advanced | Enables Geo SCADA Expert to communicate with Allen-Bradley controllers using the EtherNet/IP protocol. | |
|
HCAL |
Enables you to export historic data from Geo SCADA Expert to the historians in various AVEVA applications, including AVEVA Historian (formerly Wonderware Historian) and AVEVA Insight (formerly Wonderware Online). |
|||
|
ICMP |
Monitors and detects whether network-connected remote devices are reachable. |
|
||
|
IEC 1131-3 |
Geo SCADA Expert supports 4 of the languages included in this standard using its Logic driver. For more information, see Supported Logic Languages. |
|||
|
IEC 60870-5-101 |
This driver provides both master and slave functionality. In the online Help, the functionality is explained in two guides. The IEC 60870-5 Driver Guide explains the functionality when Geo SCADA Expert acts as a master. This functionality enables communication with Controlled Stations (such as RTUs) using the supported protocol. The Geo SCADA Expert Guide to the IEC 60870-5 Slave Driver explains the functionality that applies when Geo SCADA Expert acts as a slave. This functionality enables Geo SCADA Expert to act as an IEC60870-5 Controlled Station (outstation) and report any changes back to its Controlling Station (SCADA Master). |
You can use this driver on its own, or as the ‘parent’ driver for IEC 60870-5 extension drivers Use the ‘core’ IEC 60870-5 database items provided by this driver unless an extension driver provides application-specific functionality. When using the slave functionality, this driver uses Filtered Value Maps (rather than points) to represent 'Information Object' data address ranges. |
||
|
Extension (of the IEC 60870-5 driver) |
Enables communication with KEMA compliant devices over a direct, PSTN, or GSM connection. |
|
||
|
Extension (of the IEC 60870-5 driver) |
Enables communication with Phoenix Contact devices over a PSTN or GSM connection. |
|
||
|
IEC 60870-5-104 |
The driver supports communications via this protocol for both master and slave functionality. For more information, see above. |
|||
| IEC 61850-8-1 mapping to MMS | IEC 61850 | Advanced | Enables Geo SCADA Expert to communicate with IEC 61850 compatible IEDs (Intelligent Electronic Devices) using MMS. | |
|
Kingfisher |
Enables communications with Kingfisher RTUs either directly or remotely. |
|||
| LACBUS-RTU | Sofrel | Enables Geo SCADA Expert to communicate with Sofrel advanced outstations, S500 range. | ||
|
LinkMX |
Enables you to export historic data from Geo SCADA Expert to Wonderware eDNA. |
|
||
|
MELSEC A |
Enables communications with Mitsubishi and other third-party Slaves and PLCs using the supported protocol and transmission format. |
|||
|
Enables Geo SCADA Expert to act as a Mitsubishi A PLC and report any changes back to its Master. |
Supported Transmission Protocol Format As a slave, this driver uses Value Maps (rather than points) to represent Mitsubishi device data address ranges. |
|||
| MMS: see IEC 61850 | ||||
|
Modbus |
(Known as the ‘Advanced Modbus Driver’ in the online Help) |
For communication with Modbus controllers, using the Modbus protocol suite. You can use this driver on its own, or as the ‘parent’ driver for Advanced Modbus extension drivers. Use the ‘core’ and ‘Generic’ Modbus database items provided by this driver unless an extension driver provides application-specific functionality. |
||
|
Extension (of the Advanced Modbus driver) |
For use with oil field pumping. Enables uploading of rod pump and other data from Lufkin SAM controllers to Geo SCADA Expert. |
|
||
|
Extension (of the Advanced Modbus driver) |
Enables communications with SCADAPack controllers, including retrieval and storage of DLOG (stored SCADAPack) data records. |
|||
|
Extension (of the SCADAPack Modbus driver) |
Monitoring and processing of gas, liquid, or water flow data via Realflo-enabled SCADAPack controllers. |
|||
|
Extension (of the Advanced Modbus driver) |
For use with oil field pumping. Enables uploading of rod pump data to Geo SCADA Expert. |
|
||
|
(Known as the ‘Simple Modbus Driver’ in the online Help) |
For communication with Modbus controllers on a system with a simple configuration, using a manual scanner address. |
|||
|
Enables Geo SCADA Expert to act as a Modbus PLC and report any changes back to a Master. |
Supported Modbus Function Codes. As a slave, this driver uses Value Maps (rather than points) to represent Modbus data address ranges. |
|||
|
MQTT |
For communications between small sensors and mobile devices in remote locations, where bandwidth is limited or unreliable. The MQTT driver is designed to run alongside the relevant MQTT extension driver. |
Supported communications versions. You use this driver as the ‘parent’ driver for MQTT extension drivers. |
||
|
Extension (of the MQTT driver) |
For retrieving data using either of two MQTT JSON Schema A message formats. |
|||
| MQTT Text | Extension (of the MQTT driver) | For processing text or JSON payloads. | ||
| Sparkplug | Extension (of the MQTT driver) | For communications with Sparkplug™ compliant MQTT brokers. | ||
| Sparkplug Publisher | Extension (of the MQTT driver) | For communications with MQTT brokers to publish data to Sparkplug host applications. | ||
|
Multitone |
Sending information, such as alarm messages, to pagers and mobile phones. |
|||
|
NTP |
Monitoring the accuracy with which system clocks are being synchronized. |
|
||
|
ODBC |
Transferring data from another ODBC-compliant application into the Geo SCADA Expert database. |
|
||
|
OPC DA |
(Known as the ‘Advanced OPC Driver’ in the online Help) |
Communication with other OPC DA servers. |
||
|
(Known as the ‘Simple OPC Driver’ in the online Help) |
Communication with other OPC DA servers. |
|||
| OPC UA | OPC UA | Communication with OPC UA compliant servers. | ||
|
OPC XML-DA |
Communication with other XML-DA servers. |
|||
| Remote Diagnostics Protocol (Version 1 and Version 2) |
(Known as the ‘Advanced Trio Diagnostics Driver’ in the online Help) |
Advanced | Enables Geo SCADA Expert to interrogate Trio radios for diagnostic data, and control relay outputs in base radios. |
Trio Radio Series Supported by the Advanced Trio Diagnostics Driver |
|
(Known as the ‘Simple Trio Diagnostics Driver’ in the online Help) |
Simple | Enables Geo SCADA Expert to interrogate Trio radios for diagnostic data. |
Trio Radio Series Supported by the Simple Trio Diagnostics Driver |
|
|
ROC |
Enables communications with FloBoss flow computers. |
|
||
|
ROC Plus |
Monitoring and processing of gas flow data via Emerson Remote Operations Controller (ROC) devices. |
|||
|
SCADAPack 50 |
Enables communication with SCADAPack 50 wireless data loggers. |
|||
|
SDI-12 |
Enables Geo SCADA Expert to become an SDI-12 data recorder and read data from intelligent sensors using the supported protocol. |
|
||
|
SMS |
Sending information, such as alarm messages, to pagers and mobile phones. |
|||
|
SNMP |
Enables Geo SCADA Expert to communicate with SNMP agents. |
|
||
| SOFBUS-PL | Sofrel | Enables Geo SCADA Expert to communicate with Sofrel outstations configure to use this protocol, S50 and S500 range . | ||
|
TAP |
Sending information, such as alarm messages, to pagers and mobile phones. |
|||
|
TBox |
Enables communications with the TBox range of RTUs. |
|
||
|
UCP |
Sending information, such as alarm messages, to pagers and mobile phones. |
|||
Supported Drivers
Geo SCADA Expert provides support for the drivers that are listed below. The drivers are typically licensed separately to the ‘core’ Geo SCADA Expert product. ViewX, Virtual ViewX, and Original WebX clients only display information about the drivers and modules that are installed on your system.
For more information about a particular driver, select the link in the Driver Name column. This will take you to the introductory topic about that driver. With some drivers we also provide links to specific information in the Further Information column.
Where a driver is listed as an extension driver, you need to install and run both the ‘parent’ driver (and, where applicable, the ‘grandparent’ driver) in additional to the extension driver.
For those protocols for which Geo SCADA Expert supports multiple drivers, consider using this table in conjunction with the Supported Protocols table, which lists entries by protocol, rather than driver.
| Driver Name | Driver Category | Protocol | Driver Type | Intended Use | Further Information |
|---|---|---|---|---|---|
|
ABB: see Totalflow |
|||||
| Alarm Provider: see Wonderware Alarm Provider | |||||
|
Allen-Bradley: see DF1 |
|||||
|
Export |
HCAL |
Enables you to export historic data from Geo SCADA Expert to the historians in various AVEVA applications, including AVEVA Historian (formerly Wonderware Historian) and AVEVA Insight (formerly Wonderware Online) |
|||
|
Brio: see the SCADAPack 50 Driver |
|||||
|
Export and analysis |
CFX |
For use with flow measurement data. |
|
||
|
Reporting, Export and analysis |
|
For producing professional reports that contain information obtained from the Geo SCADA Expert database |
Requires a licensed supported version of the third-party SAP Crystal Reports application |
||
|
CSE Semaphore: see TBox |
|||||
|
Monitoring and control |
DF1 |
Enables communications with Allen-Bradley PLCs |
|||
|
Monitoring and control (With Slave functionality enabling reporting to, and control by, another SCADA Master) |
DNP3 |
Enables Geo SCADA Expert to communicate with other devices using the DNP3 protocol. The driver provides both master and slave functionality, and supports DNP3 Secure Authentication. When using the slave functionality, this driver uses Filtered Value Maps (rather than points) to represent I/O data address ranges. |
This driver provides support for DNP3 extension drivers—drivers that provide additional application-specific functionality for certain types of device. |
||
|
Monitoring and control |
DNP3 (using an application-specific extension) |
Extension (of the DNP3 driver) |
Enables communications with SCADAPack E outstations |
||
|
Monitoring and control |
DNP3 (using an application-specific extension) |
Extension (of the DNP3 driver) |
Enables communications with field devices using the WITS-DNP3 protocol (one of the Worldwide Industrial Telemetry Standards). |
||
| DNP3 T4 WITS | Monitoring and control | DNP3 (using an application-specific extension) | Extension (of the DNP3 WITS driver) | Enables full configuration of Schneider Electric Talus T4 RTUs without using a separate configuration application. |
Documentation for the T4 WITS driver is separate to the Geo SCADA Expert documentation suite. Please see the Schneider Electric Talus T4 documentation for information. |
| DNP3: also see the SCADAPack x70 Driver | |||||
|
EcoStruxure Web Services Client – Advanced (Known as the ‘Advanced EWS Driver’ in the online Help) |
Monitoring and control |
EcoStruxure Web Services |
Enables Geo SCADA Expert to read or write to data on other Schneider EWS servers |
This Advanced driver provides additional functionality to the simple driver, such as support for combined current data and historic data |
|
|
EcoStruxure Web Services Client – Simple (Known as the ‘Simple EWS Driver’ in the online Help) |
Monitoring and control |
EcoStruxure Web Services |
Enables Geo SCADA Expert to read or write to data on other Schneider EWS servers |
|
|
|
eDNA: see Wonderware eDNA |
|||||
|
Emerson: see FloBoss, ROC Plus, and SCADAPack Modbus Realflo |
|||||
|
Monitoring and control |
EtherNet/IP |
Enables communication with Allen-Bradley controllers, using the EtherNet/IP protocol. |
|||
|
EWS: see the appropriate EcoStruxure Web Services Client Driver |
|||||
|
Monitoring and control |
ROC |
Enables communications with FloBoss flow computers |
|
||
|
Flow-Cal: see CFX Export |
|||||
|
Foxboro: see SCADAPack Modbus Realflo |
|||||
|
Monitoring and diagnostics |
ICMP |
Monitors and detects whether network-connected remote devices are reachable |
|
||
|
Monitoring and control (With Slave functionality enabling reporting to, and control by, another SCADA Master) |
IEC 60870-5-101, and IEC 60870-5-104 | Advanced |
This driver provides both master and slave functionality. In the online Help, the functionality is explained in two guides. The Geo SCADA Expert Guide to the IEC 60870-5 Driver explains the functionality when Geo SCADA Expert acts as a master. This functionality enables communication with Controlled Stations (such as RTUs) using the supported protocol. The Geo SCADA Expert Guide to the IEC 60870-5 Slave Driver explains the functionality that applies when Geo SCADA Expert acts as a slave. This functionality enables Geo SCADA Expert to act as an IEC60870-5 Controlled Station (outstation) and report any changes back to its Controlling Station (SCADA Master). |
This driver provides support for IEC 60870-5 extension drivers—drivers that provide additional application-specific functionality for certain types of Controlled Station. When using the slave functionality, this driver uses Filtered Value Maps (rather than points) to represent 'Information Object' data address ranges. |
|
|
Monitoring and control |
IEC 60870-5-101 (using an application-specific extension) |
Extension (of the IEC 60870-5 driver) |
Enables communication with KEMA compliant devices over a direct, PSTN, or GSM connection |
|
|
|
Monitoring and control |
IEC 60870-5-101 (using an application-specific extension) |
Extension (of the IEC 60870-5 driver) |
Enables communication with Phoenix Contact devices over a PSTN or GSM connection |
|
|
| IEC 61850 | Monitoring and control | IEC 61850-8-1 mapping to MMS | Advanced | Enables Geo SCADA Expert to communicate with IEC 61850 compatible IEDs (Intelligent Electronic Devices) using MMS. | |
|
KEMA: see the IEC 60870-5 KEMA Driver |
|||||
|
Monitoring and control |
Kingfisher |
Enables communications with Kingfisher RTUs either directly or remotely |
|||
|
Data retrieval |
Modbus (using an application-specific extension) |
Extension (of the Advanced Modbus driver) |
For use with oil field pumping. Enables uploading of rod pump and other data from Lufkin SAM controllers to Geo SCADA Expert |
|
|
|
Monitoring and control |
MELSEC A |
Enables communications with Mitsubishi and other third-party Slaves and PLCs using the supported protocol and transmission format |
|||
|
Reporting to, and control by, another SCADA Master |
MELSEC A |
Enables Geo SCADA Expert to act as a Mitsubishi A PLC and report any changes back to its Master |
Supported Transmission Protocol Format As a slave, this driver uses Value Maps (rather than points) to represent Mitsubishi device data address ranges. |
||
|
(Known as the ‘Advanced Modbus Driver’ in the online Help) |
Monitoring and control |
Modbus |
For communication with Modbus controllers, using the Modbus protocol suite. This driver also provides support for Modbus extension drivers—drivers that provide additional application-specific functionality for certain types of Modbus controller. |
||
|
(Known as the ‘Simple Modbus Driver’ in the online Help) |
Monitoring and control |
Modbus |
For communication with Modbus controllers on a system with a simple configuration, using a manual scanner address range |
||
|
Reporting to, and control by, another SCADA Master |
Modbus |
Enables Geo SCADA Expert to act as a Modbus PLC and report any changes back to a Master |
Supported Modbus Function Codes. As a slave, this driver uses Value Maps (rather than points) to represent Modbus data address ranges. |
||
|
Modbus—also see:
|
|||||
|
Monitoring and control |
MQTT |
For communications between small sensors and mobile devices in remote locations, where bandwidth is limited or unreliable. The MQTT driver is designed to run alongside the relevant MQTT extension driver. |
Supported communications versions This driver provides support for MQTT extension drivers—drivers that provide additional functionality to receive messages in the format that is supported by the MQTT clients that publish the messages. |
||
|
Data retrieval |
MQTT (using an application-specific extension) |
Extension (of the MQTT driver) |
For retrieving data using either of two MQTT JSON Schema A message formats. |
||
| MQTT Text | Monitoring and control | MQTT (using an application-specific extension) | Extension (of the MQTT driver) | For processing text or JSON payloads. | |
| MQTT: also see the Sparkplug Driver | |||||
|
NTMon: see the Performance Monitor Driver |
|||||
|
Monitoring and diagnostics |
NTP |
Monitoring the accuracy with which system clocks are being synchronized |
|
||
|
Data transfer |
ODBC |
Transferring data from another ODBC-compliant application into the Geo SCADA Expert database |
|
||
|
(Known as the ‘Advanced OPC Driver’ in the online Help) |
Monitoring and control |
OPC DA |
Communication with other OPC DA servers |
||
|
(Known as the ‘Simple OPC Driver’ in the online Help) |
Monitoring and control |
OPC DA |
Communication with other OPC servers |
||
| OPC UA | Monitoring and control | OPC UA | Advanced | Communications with OPC UA compliant servers | |
|
Monitoring and control |
OPC XML-DA |
Communication with other XML-DA servers |
|||
|
Data transmission |
Multitone, SMS, TAP, and UCP |
Sending information, such as alarm messages, to pagers and mobile phones |
|||
|
Monitoring and diagnostics |
|
Monitor system performance |
|
||
|
Phoenix: see the IEC 60870-5 Phoenix Driver |
|||||
|
Realflo: see the SCADAPack Modbus Realflo driver |
|||||
|
Monitoring and control |
ROC Plus |
Monitoring and processing of gas flow data via Emerson Remote Operations Controller (ROC) devices |
|||
|
Rod Pump Controller: see the SE Rod Pump Controller Driver |
|||||
|
RPC: see the SE Rod Pump Controller Driver |
|||||
|
Data retrieval |
SCADAPack 50 |
Enables communication with SCADAPack 50 wireless data loggers |
|||
|
Monitoring and control |
Modbus (using an application-specific extension) |
Extension (of the Advanced Modbus driver) |
Enables communications with SCADAPack controllers, including retrieval and storage of DLOG (stored SCADAPack) data records |
||
|
Monitoring and control |
Modbus (using an application-specific extension) |
Extension (of the SCADAPack Modbus extension driver) |
Monitoring and processing of gas, liquid, or water flow data via Realflo-enabled SCADAPack controllers |
||
| SCADAPack x70 | Monitoring and control | DNP3 (using an application-specific extension) | Extension (of the DNP3 driver) | Enables communication with SCADAPack x70 devices | |
|
SCADAPack: Also see the DNP3 SCADAPack E Driver |
|||||
|
Data retrieval |
SDI-12 |
Enables Geo SCADA Expert to become an SDI-12 data recorder and read data from intelligent sensors using the supported protocol |
|
||
|
Data retrieval |
Modbus (using an application-specific extension) |
Extension (of the Advanced Modbus driver) |
For use with oil field pumping. Enables uploading of rod pump data to Geo SCADA Expert |
|
|
|
Siemens: see Simatic S7 |
|||||
|
Monitoring and control |
|
Enables communications with various S7 series of Simatic PLCs |
|
||
|
Geo SCADA Expert supports the following Slave drivers:
On systems on which Geo SCADA Expert runs a slave driver, Geo SCADA Expert is the slave device that reports its data and/or is controlled by another SCADA master. See the individual entries elsewhere in this table for more information. |
|||||
|
Monitoring and control |
SNMP |
Enables Geo SCADA Expert to communicate with SNMP agents |
|
||
| Sofrel | Monitoring and control | LACBUS-RTU SOFBUS-PL |
Enables Geo SCADA Expert to communicate with Sofrel range of devices. |
||
| Sparkplug |
Monitoring and control |
MQTT (using an application-specific extension) |
Extension (of the MQTT driver) |
For communications with Sparkplug™ compliant MQTT brokers. |
|
| Sparkplug Publisher |
Export |
MQTT (using an application-specific extension) |
Extension (of the MQTT driver) |
For communications with MQTT brokers to publish data to Sparkplug Host Applications. |
|
|
Export |
SQL |
Enables the results of SQL queries that interrogate the Geo SCADA Expert database to be exported to other applications. |
|
||
|
Monitoring and control |
TComm |
Enables communications with the TBox range of RTUs. |
|
||
|
Monitoring and control |
DB2 |
Monitoring and processing of gas flow data via ABB Totalfow flow computers. |
|||
|
(Known as the ‘Advanced Trio Diagnostics Driver’ in the online Help) |
Diagnostics | Remote Diagnostics Protocol (Version 1 and Version 2) | Advanced | Enables Geo SCADA Expert to interrogate Trio radios for diagnostic data, and control relay outputs in base radios. |
Trio Radio Series Supported by the Advanced Trio Diagnostics Driver |
|
(Known as the ‘Simple Trio Diagnostics Driver’ in the online Help) |
Diagnostics |
Remote Diagnostics Protocol (Version 1 and Version 2) |
Enables Geo SCADA Expert to interrogate Trio radios for diagnostic data. |
Trio Radio Series Supported by the Simple Trio Diagnostics Driver |
|
|
Wade 310: see the SCADAPack 50 Driver |
|||||
|
WITS: see the DNP3 WITS Driver |
|||||
| Wonderware Alarm Provider | Export | Stand-alone |
Enables you to view and manage Geo SCADA Expert alarms from within Wonderware InTouch |
||
|
Export |
LinkMX |
Enables you to export historic data from Geo SCADA Expert to Wonderware eDNA |
|
||
| Wonderware Historian driver: see the AVEVA Historic Data Export driver (this is the name by which the Wonderware Historian driver in Geo SCADA Expert is now known). | |||||