GE Ethernet

Manufacturing Suite Get GE Ethernet as a part of this suite. Learn More GE Suite Get GE Ethernet as a part of this suite. Learn More

Product Overview

The GE Intelligent Platforms Ethernet device driver provides data exchange between OPC clients and GE PLCs. Kepware automatically optimizes your data acquisition based on client demand. Data integrity is ensured with our extensive error handling. The GE Ethernet driver has been updated to support compatibility with major HMI applications making project conversion simple. This upgrade includes bit within register access and string support within register memory.

This driver is fully integrated with VersaPro, Logic Developer, and Proficy ME programming packages. A smart tag import wizard makes loading all of the tags in your PLC application a two-second operation, allowing simple access to all of your application data for any OPC or DDE enabled program.

This driver also supports PACSystems models RX3i and RX7i with Symbolic Variable support.

  • Automatic Tag Database Generation
  • Data can be transferred in arrays of up to 2048 bytes
  • Memory Types Supported: I, Q, G, M, T, S, R, AI, AQ
  • Supports %l and %P program variables
  • All data types are supported including string
  • Register data supports bit access
  • Array structure tag support
  • Structure data type support
  • 2-D tag import
  • Configurable TCP/IP Port setting allows for complex network routing
  • Fully integrated with VersaPro, Logic Developer, and Proficy ME programming packages
  • PACSystem support for the RX3i and RX7i models with Symbolic Variables
  • GE OPEN - Wide range model support
  • Horner OCS
  • PACSystem RX3i
  • PACSystem RX7i
  • Series 90-30 311
  • Series 90-30 313
  • Series 90-30 331
  • Series 90-30 341
  • Series 90-30 350
  • Series 90-30 360
  • Series 90-70 731
  • Series 90-70 732
  • Series 90-70 771
  • Series 90-70 772
  • Series 90-70 781
  • Series 90-70 782
  • Versamax Family
  • English
  • DDE Format CF_Text and AdvancedDDE
  • NIO Interface for iFIX
  • OPC .NET Service (OPC .NET) Version 1.00
  • OPC Alarms and Events (OPC AE) Version 1.10
  • OPC Data Access (OPC DA) Versions 1.0a, 2.0, 2.05a, and 3.0
  • OPC Unified Architecture (OPC UA) Clients
  • SuiteLink and FastDDE for Wonderware



  • Fixed a math error when calculating block lengths that could lead to blocks with bad quality under some circumstances.



  • Fixed an issue where values would not update after downloading a new program or changing the CPU in the device and restarting.



  • Enhanced the driver to support the ability to Read and Write Symbolic type tags when OEM Protection is enabled in the physical controller.
  • Resolved an issue with reading String data type format for register-based address types (R, P, L, W, AI, and AQ).


  • Fixed an issue where writes to strings in a discrete UDT failed.



  • Fixed an issue where the driver posted the error message "Device returned error code 0xFDFF reading symbolic variable data" when certain devices respond with unexpected bytes. The driver was updated to handle these responses.



  • Fixed an issue where data quality was bad when using only symbolic addressing for a PAC Systems device.


  • Improved performance of the PACSystems model by requesting bytes instead of byte per bit when reading symbolic variables that are in discrete memory.


  • Corrected an issue that occurred when reading symbolic variables with the PACSystems model, where symbolic array and array element tags might not be included in the same request


  • Enhanced the driver to support the reading of Symbolic addresses (for PACSystems devices) via multiple blocks within a single read packet, which dramatically improves the driver's read performance in large projects. Changed the default value of the Maximum Bytes Per Request device property from 256 to 2048.
  • Enhanced the driver to support Bit-level access within Symbolic addresses within the PACSystems model selection of the driver. This change affects the following data types: BYTE, INT, UINT, WORD, DINT, DWORD, and array elements of those data types (in both discrete and non-discrete memory). Added new error messages for invalid bit index and invalid data type for bit access.



  • Added support for %W addresses above 65,535 for the PACSystems model type.
  • Added support to Read/Write Symbolic Variables that are mapped to reference addresses for the PACSystems model type.
  • Resolved an issue where the driver was not locking a process thread correctly, which could cause the driver to stop issuing polls to devices.
  • Fixed a data alignment issue that occurred when reading and writing symbolic discrete array variables.
    • Symbolic discrete array element tags require two symbolic information requests in order to calculate the start byte based on the base array address and the array index.
    • Recalculate the native data size of symbolic discrete array and array elements depending on data type.
    • Fail request and report warning message occur if the symbolic discrete array native data size exceeds the maximum request size (because it cannot be caught in the address parser).
    • Corrected a pre-existing issue in the tag import to force the "{" on array element tag addresses.
    • Handle nested symbolic discrete array variables.
    • Clear previously collected symbol information after an invalid PVT version.



Fixed an issue with importing tags from GE Proficy's tag database (.CSV and .SNF formats). The driver was failing to correctly import symbolic structure tags that were part of a ladder block.


  • Fixed an issue wherein Symbolic Tags were being forced to Read/Write.


  • Fixed issue where PACSystem UDT discrete data types were not being read or written properly.


  • Fixed issue where PACSystem UDT Booleans were not being read or written properly


  • Fixed issue where symbolic Float and Double tags were showing 1.#INF (invalid Float) instead of "0" value.
  • Added new double addressing to hints
  • Now allow for the alias tag data types that are specified as BOOL to assume the source tag data type.
  • Fixed issue where address parsing of non-register, non-string memory types allowed a "-" in the address field.
  • Added support for DOUBLE data types.