531X210DMCAMM1 GE Controller module Brand new

No CPU fault logged when Ethernet 

Interface in fatal blink code

The CPU does not log any Controller or I/O Faults when the Ethernet 

Interface has a fatal blink code. The user’s application should monitor the 

LAN interface OK status bit to detect loss of module.

EGD I/O has unexpected variability 

under heavy load

EGD I/O has intermittent unexpected variability under heavy load. For a 

Produced Exchange, EGD samples may occasionally be delayed by as 

much as a production period or more.

Clear of large hardware configurations 

may cause log event 08/20

A Log event 08/20 may occur when very large hardware configurations 

are cleared and transfers are active on other Server connections. This log 

event can be safely ignored.

COMMREQ Status Word of 0x54A0 

occasionally returned for EGD 

commands

Occasional COMMREQ Status Word values of 0x54A0 are returned to 

COMMREQs for EGD commands when the previously transferred 

command has experienced retries in the network. Executing the 

COMMREQ again results in successful transfer of the command.

Modbus/TCP channel aborted during 

power cycle

After powering up an RX7i running Modbus/TCP client channels, the 

establish connection occasionally fails because the server occasionally 

rejects the "open" from the client. The connection will then succeed if the 

application retries the open when it sees a 0x9690, 0xAA90, or B490H 

response to an open request or to the first write request.

RX7i response timeout errors (8/08) in 

Ethernet exception log under extremely 

heavy SRTP traffic

Under extremely heavy SRTP traffic conditions, the Ethernet Interface 

may log an event in the Ethernet exception log (Event 8, Entry 2 = 08H) 

indicating an overload condition. This error terminates the SRTP 

connection. If this event appears, either the traffic load should be 

reduced, or the application should use an alternate communications 

method to verify that critical data transfers were not lost due to the 

overload.

SRTP channel transfers may take up to 

20 seconds after power cycle

When SRTP communications are interrupted by a power cycle, the 

Ethernet interface may require up to 20 seconds to reestablish TCP 

connection used for SRTP communications.