General Electric Relay System Controller IC695ETM001ER

Description

SRTP and EGD Performance Differs from Series 90-30 SRTP and EGD performance in the RX3i differs slightly from the Series 90-30. Each RX3i Ethernet Interface supports a greater number of SRTP connections and EGD exchanges. The RX3i currently has several SRTP and EGD operational restrictions compared to the Series 90-30. When migrating Series 90-30 Ethernet applications to the RX3i, please carefully read the Ethernet Operational Notes.

Series 90-30 LAN Interface Module (IC693CMM321) Not Supported by RX3i The Series 90-30 LAN Interface Module (IC693CMM321) is not supported by the RX3i and should not be placed in an RX3i rack. (Series 90-30 CPUs with embedded LAN Interface, IC693CPU364 and IC693CPU374, like any Series 90-30 CPU, should not be placed in an RX3i rack.) Modbus/TCP support Release 3.00 of the PACSystems Ethernet Interface firmware supports the Modbus/TCP Server capability of the Series 90-30 LAN Interface Module (IC693CMM321). However, this release does not support the Modbus.

From the perspective of network structure: Generally speaking, DCS commonly uses a two-layer network structure, with one layer being a process level network. Most DCS uses their own bus protocols, such as Yokogawa’s Modbus, Siemens and ABB’s Profibus, ABB’s CAN bus, etc. These protocols are all based on standard serial transmission protocols RS232 or RS485. The on-site IO module, especially the sampling data of analog quantities (machine code, 213/scan cycle), is very large, and there are many on-site interference factors. Therefore, network standards with high data throughput and strong anti-interference ability should be adopted. The bus structure based on RS485 serial port asynchronous communication mode meets the requirements of on-site communication. The sampling data of IO is converted by the CPU into shaped or real data, which is transmitted on the operation level network (second layer network). Therefore, the operation level network can adopt several.

According to the network standards of moderate throughput, fast transmission speed, and convenient connection, as the operation level network is generally arranged in the control room, the requirements for anti-interference are relatively low. Therefore, using standard Ethernet is the best choice. TCP/IP protocol is a standard Ethernet protocol that typically uses a communication speed of 100Mbit/s. The working task of a PLC system is relatively simple, so the amount of data that needs to be transmitted is generally not too large, so a common PLC system is a one layer network structure. The process level network and operation level network can either be merged together, or the process level network can be simplified into internal connections between modules. PLC does not or rarely uses Ethernet.

In terms of the scale of the application object, PLC is generally used in small automatic control places, such as equipment control or a small amount of analog control and interlocking, while large-scale applications are generally DCS. Of course, this concept is not very accurate, but it is very intuitive. Traditionally, we refer to systems larger than 600 points as DCS, and systems smaller than this scale as PLCs. Our control system for heat pumps, QCS, and horizontal products is generally referred to as PLC.

3HAC025798-001
MKD112C-058-KP0-AN
3HAC029396-001
AS-J890-102
PFSK102 YM322001-EG
WH5-2FF
3HNM11251-1
RCX40
MVI56-MNETC
GNF-56-D
E69F-B12
SCXI-1162
51402455-100 MP-DNCF02-200
DS200ITXSG1ABB
3HAA3003-52
3HAC7363-7
S61400-NA
3HAC020330-001
Saft 121 PAC
4WE6E70/HG24N9K4
DSQC639
3HNM07648-1