GE PACSystems RX7i, Руководство пользователя

Страница: 225 / 276

Chapter 12. Diagnostics
212 PACSystems* RX7i & RX3i TCP/IP Ethernet Communications User Manual GFK-2224Q
Blink
Code
Description Blink Code Description
0x39 Instruction cache TLB miss exception 0x78
Boot: Unexpected Restart pushbutton
interrupt
0x41 BSP startup error
12.5
Controller Fault Table
Most error conditions involving the Ethernet interface generate faults in the Controller Fault table. The table on
the next two pages lists Ethernet interface faults and corrective actions.
To access the details of a Controller Fault Table entry, double-click the Fault Table entry and the details are
displayed as “fault extra data”. Refer to Online Help in the PLC programming software for more information.
An example of the fault extra data is shown below:
Figure 89: Fault Extra Data Example
For Ethernet Interfaces the leftmost 14 digits of fault extra data (underlined in the example above) show the
corresponding log Events (2 digits) and Entries 2, 3, and 4 (in that order, 4 digits each).
The example above is reporting
▪ an Event 16,
▪ Entry 2=6,
▪
Entry 3=3, and
▪ Entry 4=5.
This information can be used to refer directly to detailed fault descriptions included in the Exception Log Event
tables in GFK-2225,
TCP/IP Ethernet Communications for PACSystems Station Manager Manual.
(In that
document, refer to Appendix B, Exception Log Events.)
Controller Fault Table Descriptions
Controller Fault User Action
Backplane communications with
controller fault; lost request
Check to make sure that the logic application is not sending COMMREQs
faster than the Ethernet Interface can process them. Reduce the rate at
which the application is sending COMMREQs to the Ethernet interface. If
problem persists, contact Technical Support.
Mailbox queue full – COMMREQ
aborted
Check to make sure that the logic application is not sending COMMREQs
faster than the Ethernet Interface can process them. Reduce the rate at
which the application is sending COMMREQs to the Ethernet interface. If
problem persists, contact Technical Support.
Bad local application request;
discarded request
Check for valid COMMREQ command code. If problem persists, contact
Technical Support.
Bad remote application request;
discarded request
Try to validate the operation of the remote node. If problem persists,
contact Technical Support.
Can’t locate remote node;
discarded request
Error reported when message received where IP/MAC address cannot be
resolved. Error may indicate that remote host is not operational on the
network. Check that remote host is operational on network and its
addresses are correct.