Download Adept Cobra PLC600 User's Guide - pulsar.com.tr

Diagnostic and Error Messages
DF1 Protocol — Remote STS Error Codes
The remote STS error code, (2-digit) byte value, reports errors found by the PLC that
received the <strong>com</strong>mand from the PLC Server. Error codes (in hex) that might be reported as
the remote error code are listed in Table 11-2.
Table 11-2. Remote STS Error Codes
Code Explanation
00 Success -- no error
10 Illegal <strong>com</strong>mand or format
20 Host has a problem and will not <strong>com</strong>municate
30
40
Remote node host is missing, disconnected, or shut
down
Host could not <strong>com</strong>plete function due to hardware
fault
50 Addressing problem or memory protect rungs
60
Function not allowed due to <strong>com</strong>mand protection
selection
70 Processor is in Program mode
80
Compatibility mode file missing or <strong>com</strong>munication
zone problem
90 Remote node cannot buffer <strong>com</strong>mand
A0
B0
C0
D0
E0
F0
Wait ACK (1775_KA buffer full)
Remote node problem due to download
Wait ACK (1775_KA buffer full)
Not used
Not used
Error code in the EXT STS byte (see the section DF1
Protocol — EXT STS Error Codes)
DF1 Protocol — EXT STS Error Codes
When the PLC reports the STS code F0 (hex), that indicates that the status is contained in
an EXT STS byte. The interpretation of this byte varies, depending on the <strong>com</strong>mand code
(or type of <strong>com</strong>mand) that was sent to the PLC. Table 11-3 lists EXT STS codes for CMD
code 0F (hex). That is the only <strong>com</strong>mand code used by the PLC Server that can result in an
EXT STS byte in the response from the PLC.
154 <strong>Adept</strong> <strong>Cobra</strong> <strong>PLC600</strong>/PLC800 Robot User’s <strong>Guide</strong>, Rev B