6 |
Table 6-10. Exception Log Event Codes - Continued
Log Event
Code
Eventª8º PLCDriver events
Possible Cause and Resolution
This event is logged by the PLC Backplane Driver when an unexpected event occurs. Entries1 and 6 of the event log will be zero. For some events, Entries 3, 4 and 5 will give more information on the event.
Entry 2 of the event log is an exception code which indicates what error oc- curred. In general, Entry 2 codes 1 - 1F are PLC backplane communication faults, codes 20 - 2F are resource errors, and codes 30 and up are miscellaneous errors. Entry 2 may have the following values.
1
Could not open VME mailbox. Entry 4 contains the status returned from the MBU_OPEN routine. Entry 5 contains the number of open attempts we made.
2
Could not enable interrupt capability for incoming mail. Entry 4 contains the returned status from the MBU_ENAB_INT routine.
3
Mailpackets from PLC for a read response are out of order. Entry 4 contains the received packet sequence number. Entry 5 contains the expectedpacket sequence number.
4
PLC completed a response earlier than expected. Entry 4 contains the current transfer state.
5
Message from PLC for unknown Ethernet Interface task. Entry 4 contains the task ID received from the PLC.
6
Received PLC response for unknown request. Entry 4 contains the mailbox sequence number of the stray response.
7
Bad message type from PLC. Entry 4 contains the message type code received.
8
Timed out waiting for PLC response. Entry 4 contains the mailbox sequence number for this transaction. Entry 5 contains the transfer state when the timeout occurred. This problem may occur due to the Ethernet Interface being asked to perform beyond its capacity. Try transferringless data per message or establishing fewer simultaneous connections.
9
CPU completed program download before Ethernet Interface was ready.
A
CPU still wants program upload data when Ethernet Interfacefinished.
20
21
Chapter 6 Troubleshooting |
