Hardware reference guide
Error Stpd. Codes
866
35013379 02 October 2007
Definitions for
Error Stopped
Codes
The following are definitions for Error Stopped Codes.
z PLC unhealthy: This condition indicates that the CPU has failed one or more of
its health diagnostics. In all probability the CPU will have to be replaced.
z 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 would indicate
"8000" hex. An error condition exists when "8000" is anded with one or more of
the previously defined errors (bits 0-14). An example would be an error code of
"8100"; this suggests a PLC stopped with No End of Logic Node detected.
z Bad I/O map: This error will occur 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 has been configured in such a way so as to exceed the maximum
number of inputs/outputs allowable per drop.
z PLC unconfigured: The user should expect this condition if he is trying to log into
the CPU for the first time. This error indicates that the CPU has not been
configured. The user should write a configuration offline and transfer it to the CPU
prior to attempting to login to the CPU. If this error appears while seeking to
coomunicate to a previously running CPU, this would suggest a corrupted state
memory in the CPU. The usr should clear memory and attempt to reload the user
logic program.
z Bad modbus port intervention: This error will most likely appear in conjunction
with another error. The CPU would in all likelihood be stopped when this error
occurs. This error may also appear upon the user’s attempt to clear the system
stop state. The user should try to clear user logic and reload.
z Bad segment scheduler: This error indicates improper programming of the
segment scheduler.
z Start-of-network (SON) did not start a segment: This error is most often
caused by improper programming. It can also be caused by a corrupted program
and can be detected by issuing a start command to the CPU.
z Bad power-down checksum: This error indicates that continuous run time ram
diagnostic has failed. Reload the user logic program. If this error persists, replace
the CPU.
z No end of logic detected: This error is usually caused by an incomplete or
unsuccessful load of the program. Try another reload.
z Watchdog timer has expired: This error indicates that the CPU has taken too
much time to complete its current scan. This error will sometimes occur with
ambitious DX programming techniques. The user may want to increase the
Watchdog Timer value. This error may also point to a failure of the CPU.
z Real time clock has failed: Replace the CPU.
This document provided by Barr-Thorp Electric Co., Inc. 800-473-9123 www.barr-thorp.com