Machine Stop Code Descriptions
|
Stop Bit
Code (hex)
|
Description
|
|
0x7FFF
|
PLC unhealthy
|
|
0x8000
|
PLC stopped
|
|
0x8400
|
CPU has stopped because the firmware of the CRP module is not compatible with the application program in which the "Online Modification in RUN" check box has been selected
|
|
0x4000
|
Bad I/O traffic cop
|
|
0x2000
|
PLC in Dim awareness
|
|
0x1000
|
Bad port intervention
|
|
0x0100
|
Software error, PLC in HALT
|
|
0x0400
|
CRP firmware not compatible with CCOTF function
|
|
0x0080
|
Watchdog timer has expired
|
|
0x0010
|
RIO option error
|
|
0x0001
|
Bad configuration
|
-
PLC unhealthy: This condition indicates that the CPU has not successfully completed one or more of its health diagnostics. Usually this means that the CPU needs to be replaced.
-
PLC stopped: By itself, an 8000 hex is not an error but a CPU state. If, for example, a user issues a CPU stop command, the status register indicates 8000 hex. An error condition exists when 8000 is added with one or more of the previously defined errors (bits 0-14).
Example:
-
2 stop codes are added,
the 8100 stop code suggests that a PLC has stopped because of a software error detection. The controller is in halt and the application is stopped.
-
3 stop codes are added,
the 8180 stop code suggests that a PLC has stopped because of a software error detection and that the watchdog timer has expired.
-
Bad I/O map: This error occurs if the user declares more than one I/O drop in his configuration but does not have an RIO Head installed. This error may also occur if a drop configuration exceeds the maximum number of inputs/outputs allowable per drop.
-
PLC unconfigured: Expect this condition if you are trying to log into the CPU for the first time. This error indicates that the CPU has not been configured. Write a configuration offline and transfer it to the CPU prior to logging into the CPU. If this error appears while you are seeking to communicate with a previously running CPU, this could indicate corrupted state memory in the CPU. You need to clear memory and attempt to reload the user logic program.
-
Bad modbus port intervention: This error sometimes appears in conjunction with another error. The CPU is usually stopped when this error occurs. The error may also appear if you attempt to clear the system stop state. Try to clear user logic and reload.
-
Software error, PLC in HALT: This error is usually caused by an incomplete or unsuccessful program load. Try to reload.
-
Watchdog timer has expired: The error indicates that the CPU has taken too much time to complete its current scan. You may increase the Watchdog timer value. This error may indicate that the CPU is inoperable..
-
RIO option error: The RIO option board (140 CRP 93• 00) is unhealthy. Replace the board. An error 8010 means that the CPU has stopped because RIO option board has to be replaced (unhealthy).
-
Bad configuration: The most probable cause is that the memory has been modified through the MODBUS/MODBUS PLUS ports. If this error occurs during a program download, check your configuration data for values greater than the CPU's specified addressable range. This error can also appear if the CPU's memory is corrupt.
NOTE: The user can access the Stop codes and the sub Stop codes with the LCD keypad, available only with High-End processors, by selecting System info -> Stop codes.
If the sub Stop code is included between:
-
50 and 98, the machine stopped because of a Traffic Cop error..
-
101 and 137, the machine stopped because of an error of Peer cop.
You can see, in the words %SW124 and %SW125, information if it is a system error and the last default detected.
The causes of the HALT state are saved in the system words: %SW125, %SW126 and %SW127. When the PLC is in HALT mode, the application is no longer executed, the IO are no longer applied.
To quit the HALT state, the user must either initialize or reload the application into the PLC.
