GE PAC Systems TCP/IP Ethernet通讯手册：EGD与MODBUS指南

5星 · 超过95%的资源需积分: 50 166 浏览量更新于2024-07-18 1 收藏 2.04MB PDF 举报

"GE 以太网通讯手册，GFK2224F PAC系统 TCP/IP以太网通讯手册，EGD通讯与MODBUS通讯使用说明" 该文档是GE Fanuc Intelligent Platforms公司为PAC Systems™（可编程自动化控制器系统）用户提供的TCP/IP Ethernet通信用户手册，版本GFK-2224F，发布于2007年11月。手册旨在详细介绍如何在PAC系统中实现以太网通信，包括EGD（GE专有的通讯协议）和MODBUS这两种常见的工业通信协议。 1. **TCP/IP Ethernet通信**： TCP/IP（传输控制协议/互联网协议）是互联网上广泛使用的通信协议，它定义了数据在网络中的传输方式。在PAC Systems中，通过TCP/IP可以实现控制器与其他设备间的远程通信，如数据交换、设备监控和控制。 2. **EGD通讯**： EGD（Ethernet for GE Devices）是GE专为其设备设计的一种通信协议，它允许GE的控制器与各种设备进行高效的数据交互。EGD协议可能包含特定的报文结构和错误处理机制，以确保在PAC系统中的可靠通信。 3. **MODBUS通讯**： MODBUS是一种公开的串行通信协议，最初由MODICON公司开发，现在广泛应用在各种工业设备中。MODBUS协议允许设备间进行数据交换，通常用于PLC（可编程逻辑控制器）和SCADA（监控与数据采集）系统。在PAC Systems中，支持MODBUS意味着可以与大量第三方设备兼容，扩大了系统的互操作性。 4. **安全注意事项**：文档中提到了“警告”、“注意”和“提示”三种类型的提示信息。警告用于强调可能存在危害人身安全的电压、电流、温度或其他条件；注意提醒用户如果不小心操作可能会导致设备损坏；而提示则是为了突出对理解和操作设备至关重要的信息。 5. **内容覆盖**：虽然手册基于发布时的信息，并尽力保持准确性，但不涵盖所有硬件或软件的细节和变化，也不预见到所有安装、操作和维护过程中可能出现的情况。手册可能会描述一些特性，这些特性在实际应用中可能会有所变化或更新。 6. **适用范围**：该手册适用于需要通过以太网连接PAC Systems与其他设备的工程技术人员，无论是进行系统集成、设备调试还是日常维护，都能从中获取必要的通信配置和故障排查指南。通过这份手册，用户将能够掌握如何配置PAC Systems的网络设置，建立和维护EGD和MODBUS通信链路，以及如何解决可能出现的通信问题。对于那些需要在GE平台上实现高效工业网络通信的工程师来说，这是一份非常有价值的参考资料。

1-8 TCP/IP Ethernet Communications for PACSystems™ – November 2007 GFK-2224F

Ethernet Redundancy Operation

The Redundant IP feature of the Ethernet Interface allows a single IP address called the

Redundant IP address to be assigned to two Ethernet modules. The two modules are in two

different PLCs that are configured as a redundant system.

The Redundant IP Address is configured in addition to the normal unique (direct) IP address

of each interface.

Only one of the two Ethernet interfaces that share the Redundant IP address may use the

Redundant IP address at any time; this is the “active” unit. When commanded by its PLC

CPU, this Ethernet interface activates the Redundant IP address and starts responding to the

Redundant IP address in addition to its direct IP address. The active unit continues

responding to the Redundant IP address until it is commanded to deactivate the Redundant

IP or until the Ethernet interface determines that it has lost communications with the

PLC CPU.

The other unit (the “backup” unit) does not initiate communications or respond on the network

using the Redundant IP address. It can only use the Redundant IP address if it is commanded

by its CPU to become the active unit.

Both the active and backup unit may continue to use their individual direct IP addresses,

permitting programmer connection to the active or backup PLC at any time.

PLC A

PLC B

Redundant S

stem

Programmer

Remote host

(HMI, PLC, etc.)

Redundant

IP Address

Direct IP

Addresses

The Redundant IP feature is supported by Hot Standby (HSB) CPUs and non-HSB CPUs.

HSB CPU Redundancy

An HSB system uses redundancy CPUs that provide the coordination between the PLC units

in the system and determine which is the active unit and which is the backup unit. HSB

redundancy requires dedicated links to provide communications between the units in a

redundancy system. Redundancy CPUs that include an embedded Ethernet Interface have a

“CRE” designation, for example IC698CRE040. For information about HSB architectures,

refer to the PACSystems Hot Standby CPU Redundancy User’s Guide, GFK-2308.

1-10 TCP/IP Ethernet Communications for PACSystems™ – November 2007 GFK-2224F

Effect of Redundancy Role Switching on Ethernet Communications

When a redundancy role-switch occurs, Ethernet communications switch to the backup unit,

which has no knowledge of any communication state at the previously-active unit. The

application must include logic to detect loss of communication during a redundancy role

switch and to then reinitiate communication.

To remote hosts on the network, the redundant system is viewed as a single PLC with high

reliability; the remote host neither knows nor cares which PLC is the active unit. By using the

Redundant IP address, the remote host always communicates with the active unit. When a

redundancy role switch occurs, the formerly-active PLC gives up ownership of the Redundant

IP address and takes down all connection-oriented communications currently using the

Redundant IP address. The applications in the redundant system and remote hosts must

reestablish any such communications; the new Redundant IP connections will use the newly

active PLC.

The programmer can still communicate directly with each PLC in the redundant system (for

example, to store new logic or configuration) using the direct IP address of each Ethernet

Interface.

Role Switching In HSB Redundancy Systems

In HSB redundancy systems, a role switch is initiated automatically by the redundancy CPU

when the active unit detects a fatal fault, is placed in Stop mode, or is powered off. An HSB

role switch can also be initiated manually or by the application logic. For additional information

about role switches in HSB systems, refer to the PACSystems Hot Standby CPU Redundancy

User’s Guide, GFK-2308.

Role Switching in Non-HSB Redundancy Systems

When redundant IP is enabled for an Ethernet module in a non-HSB CPU system, it is the

responsibility of application logic to set the redundancy mode of the Ethernet module. The Set

Application Redundancy Mode Service Request (SVC_REQ 55) instruction is used to inform

the Ethernet module of the current redundancy role of the host CPU. This SVC_REQ should

be used to provide redundancy role switch notification to all Ethernet interfaces in the

controller that are configured for redundant IP operation.

After commanding a role switch for an Ethernet interface, the application logic can monitor the

module’s LAN Interface Status (LIS) block to determine when it has activated the Redundancy

IP address. For details about the LIS, refer to “Monitoring the Ethernet Interface Status Bits” in

chapter 10.

Note: The application must allow sufficient time for Redundant IP activation (at least

120 msec) before commanding another redundancy role switch.

GFK-2224F Chapter 1 Introduction 1-11

When an Ethernet interface recognizes that a redundant IP address has been configured for

it, the module sends a mail message to the CPU to register for redundancy role switch

notification. In non-HSB systems, the Ethernet interface is initially put into backup mode. After

power up, the application logic must use a SVC_REQ to set the redundancy state to the

desired value. Once running, the CPU remembers the last commanded redundancy role sent

to that Ethernet interface. When an Ethernet interface is restarted, the CPU automatically

commands the Ethernet interface to its last redundancy state without explicit action by the

application logic.

Going to Stop Mode

When a non-HSB CPU goes to Stop mode, Ethernet interfaces that are configured for

redundant IP are automatically set to backup mode. When the CPU is subsequently returned

to Run mode, the Ethernet interfaces remain in backup mode until the application logic sets

the redundancy mode to active.

Stop/IO Scan Enabled Mode

In this mode, I/O scanning including EGD service continues when the non-HSB CPU is

stopped. However, Ethernet interfaces configured for redundant IP operation are

automatically set to backup mode and normal EGD production for those interfaces is stopped.

Only the EGD exchanges with Produce in backup mode enabled are produced while the CPU

is in Stop/IO Scan Enabled mode. To stop production for all EGD produced exchanges

including Produce in backup mode exchanges, choose the Stop/IO Scan Disabled mode of

operation.

Commanding a Role Switch in a Non-HSB Redundancy System

Use the Set Application Redundancy Mode service request (SVC_REQ 55) with non-HSB

CPUs to request that the CPU send redundancy role switch commands to all Ethernet

interfaces in that PLC that are configured for redundant IP operation. For details on using the

Service Request function, refer to the PACSystems CPU Reference Manual, GFK-2222.

This function has an input parameter block with a length of one word.

address

0=Backup redundancy role

1=Active redundancy role

SVC_REQ 55 is recognized in non-HSB CPUs only. This service request sends a role switch

command to all Ethernet interfaces in the PLC that are configured for redundant IP operation.

The application must monitor the LAN Interface Status (LIS) word for each Ethernet interface

to determine whether the Redundant IP address is active at that interface.

SVC_REQ 55 has no effect on Ethernet interfaces that are not configured for redundant IP

operation.

1-12 TCP/IP Ethernet Communications for PACSystems™ – November 2007 GFK-2224F

SRTP Server Operation in a Redundancy System

Only the active unit maintains SRTP Server connections at the Redundant IP address and is

able to respond to SRTP requests. The backup unit does not respond to the Redundant IP

address. When an Ethernet interface changes from active to backup state, it takes down all

SRTP Server connections and their underlying TCP connections that use the Redundant IP

address.

Both the active and backup units maintain SRTP Server connections at the direct IP address

for network communication with the programmer. Other remote hosts should use the

Redundant IP address when communicating to a redundant system. Existing SRTP Server

connections at the direct IP address are not disturbed when the Ethernet interface switches

between active and backup states.

SRTP Client Operation in a Redundancy System

Only the active unit establishes and maintains SRTP Client connections (channels). The

backup unit does not initiate any SRTP Client operations. If SRTP Client operations are

attempted, a COMMREQ error status is returned to the local logic program. When the

Ethernet interface changes from active to backup state, it takes down all SRTP Client

connections and their underlying TCP connections.

Because it can take some time to take down a TCP connection, the redundant system should

reserve a spare SRTP Client connection for each connection using the Redundant IP

address. That will prevent temporary resource problems when establishing new SRTP Client

connections to the new active unit while the previous connections to the old active unit are

being taken down.

Modbus/TCP Server Operation in a Redundancy System

Only the active unit maintains Modbus/TCP Server connections at the Redundant IP address

and is able to respond to Modbus/TCP requests. The backup unit does not respond to the

Redundant IP address. When an Ethernet interface changes from active to backup state, it

takes down all Modbus/TCP Server connections and their underlying TCP connections that

use the Redundant IP address.

Remote hosts should use the Redundant IP address when communicating to a redundant

system. Existing Modbus/TCP Server connections at the direct IP address are not disturbed

when the Ethernet interface switches between active and backup states.

剩余254页未读，继续阅读

lweidream

粉丝: 0

GE PAC Systems TCP/IP Ethernet通讯手册：EGD与MODBUS指南

GEFanuc工业以太网通讯详解

GE Fanuc 以太网手册：通道命令与网络通信

GE Fanuc以太网通讯编程与网络概念解析

GE 90-30系列modbusTCP通讯手册.docx

GE 90-30系列modbusTCP通讯手册.pdf

GE网络手册

GE_Fanuc网络及通讯用户手册.pdf

GE-PACSystem手册2012.2.27

GE PLC CPU参考手册

GEFanuc自动化网络及通讯手册

最新资源