正在加载……

GE Ethernet

参见购买信息了解更多详情
Download Free Demo

产品概览

GE Intelligent Platforms Ethernet 设备驱动与 KEPServerEX 结合使用,在 OPC 客户端与 GE PLC 之间提供数据交换。KEPServerEX 基于客户端需求自动优化您的数据采集过程。我们强大的错误处理能力可确保数据完整性。GE Ethernet 驱动已更新,支持与主要 HMI 应用程序兼容,让项目转换变得简单起来。此更新包括寄存器的位访问和寄存器内存的字符串支持。

此驱动与 VersaPro、Logic Developer 和 Proficy ME 编程包完全集成。智能标签导入向导让您可以在两秒内加载 PLC 应用程序中的所有标签,从而支持任何启用 OPC 或 DDE 的程序轻松访问您的所有应用程序数据。

此驱动还支持具备符号变量支持的 PACSystems 型号 Rx3i 和 RX7i。

资源

性能

  • 自动生成标签数据库
  • 数据可以在最多 2048 字节的数组中传输
  • 支持的内存类型:I、Q、G、M、T、S、R、AI、AQ
  • 支持 %l 和 %P 程序变量
  • 支持对系统参数的访问,包括 PRIVLEVEL、_SWEEPTIME、_SNPID、_PROGNAME、_SNUM_PROGS、_SPROG_FLAGS、_TIME、_OVERSWEEP、_CONSWEEP、_NEWFT、_NEWIOFT、_FTSTATUS、_IOSTATUS 和 _PROGATTACH
  • 支持所有数据类型,包括字符串
  • 寄存器数据支持位访问
  • 支持数组结构标签
  • 支持结构数据类型
  • 2-D 标签导入
  • 可配置的 TCP/IP 端口设置支持复杂的网络路由
  • 与 VersaPro、Logic Developer 和 Proficy ME 编程包完全集成
  • 支持具备符号变量的 PACSystem 型号 Rx3i 和 RX7i

支持的设备

  • 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

可用语言

  • 英语

应用程序支持

  • 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

发行说明

6.8.796.0

2019/12/17

  • 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).

6.3.273.0

2017/9/27

  • 修复了对离散型 UDT 中的字符串进行写入失败的问题。

5.17.495.0

2015/2/24

  • 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.

5.15.585.0

2014/7/22

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

5.13.191.0

2013/10/15

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

5.12.140.0

2013/6/18

  • 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

5.11.250.0

2013/3/5

  • 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.

5.10.205

2012/11/13

  • 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.

5.9.170

2012/6/26

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.

5.4.131.0

2010/10/28

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

5.3.118.0

2010/6/9

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

5.2.133.0

2010/2/18

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

5.1.71.0

2009/10/21

  • 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.