Chapter 12. Diagnostics
GFK-2224Q January 2017 235
PLC Timeout Errors
PLC timeout errors may occur when the SRTP traffic to the Ethernet Interface exceeds the PLC’s ability to
process the requests, or when the PLC is unable to deliver mail to the Ethernet Interface. PLC Timeout errors will
take down an SRTP Server connection; in this case, the remote SRTP client must reestablish a new SRTP
connection to the Ethernet Interface.
This error is indicated in the Controller Fault Table as:
Backplane communication with controller fault; lost request
with exception Event = 8, Entry 2 = 8
These errors may also be accompanied by any of the following:
Backplane communication with controller fault; lost request
with exception Event = 8, Entry 2 = 6; location = Ethernet Interface
LAN system-software fault; resuming
with exception Event = 8, Entry 2 = 16; location = Ethernet Interface
Non-critical CPU software event
status code (bytes 5-8) = 80 3a 00 12; location = CPU module
The PLC Timeout condition occurs when the CPU cannot process requests within a specified timeout period.
The remedy is to reduce the rate of requests, or increase the processing capacity in the PLC.
Cause Corrective Action
Heavy COMMREQ traffic. Reduce the rate at which the logic application sends COMMREQs to the
Ethernet Interface.
Heavy SRTP traffic. Reduce the size, number, or frequency of SRTP requests at the remote SRTP
client.
Long PLC sweep time. Modify the PLC application to reduce the PLC sweep time.
PLC Communication Window
set to LIMITED mode.
Change to RUN-TO-COMPLETION mode.
Note: The rack-based Ethernet modules use the Backplane Communications Window. The RX7i
embedded Ethernet daughterboard uses the Controller Communications Window.
To Next Page
Loading...
