Download Adept Cobra PLC600 User's Guide - pulsar.com.tr
Download Adept Cobra PLC600 User's Guide - pulsar.com.tr
Download Adept Cobra PLC600 User's Guide - pulsar.com.tr
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
PLC Server Messages<br />
LED Pattern<br />
1 2 3<br />
Error<br />
Description<br />
- R G -3021 *Pallet locations are linear*<br />
- G R -3022 *Invalid pallet index* Position n<br />
R G R<br />
-xxx<br />
Error : <br />
xx<br />
xxx<br />
Message : <br />
Warning : <br />
1. When the PLC Server first starts up, “GGG” is displayed until: (a) the PLC starts <s<strong>tr</strong>ong>com</s<strong>tr</strong>ong>municating<br />
with the Server, or (b) the Server times out (see #3 below).<br />
2. During normal <s<strong>tr</strong>ong>com</s<strong>tr</strong>ong>munication with the PLC, the “GGG” pattern is turned on and off by alternate<br />
<s<strong>tr</strong>ong>com</s<strong>tr</strong>ong>munications. That results in an activity indicator (but with a variable frequency).<br />
3. If there is no <s<strong>tr</strong>ong>com</s<strong>tr</strong>ong>munication with the PLC for the time-out period (currently 5 seconds), the “RRR”<br />
pattern blinks on and off (very slowly -- 2.5 seconds on, 2.5 seconds off).<br />
4. If the PLC Server code is not able to start for some reason, the three status LEDs on the<br />
SmartCon<strong>tr</strong>oller are turned on red. Unlike the behavior for the lost-<s<strong>tr</strong>ong>com</s<strong>tr</strong>ong>munication error, the LEDs<br />
do not blink on and off in this situation.<br />
5. If there is any other error, the corresponding LED pattern is displayed when the error message is<br />
sent to the PLC. Note that this “error” pattern does not blink. The LEDs return to the blinking<br />
“GGG” pattern when the PLC sends a reset-fault <s<strong>tr</strong>ong>com</s<strong>tr</strong>ong>mand (N240:0/5 or <s<strong>tr</strong>ong>Adept</s<strong>tr</strong>ong>_Command_Bits.5).<br />
PLC Server Messages (Alphabetical Listing)<br />
*Cannot mix joint-coordinate location and pallet* (-3009)<br />
A motion relative to a pallet has been requested, and the motion-qualifier bits (N240:4<br />
or <s<strong>tr</strong>ong>Adept</s<strong>tr</strong>ong>_Motion_Qualifier) indicate that the specified location is defined by joint<br />
coordinates.<br />
*Cannot move relative to a pallet* (-3010)<br />
A relative motion has been specified by the motion-qualifier bits (N240:4 or<br />
<s<strong>tr</strong>ong>Adept</s<strong>tr</strong>ong>_Motion_Qualifier), and a pallet has been identified by the <s<strong>tr</strong>ong>com</s<strong>tr</strong>ong>mand register<br />
(N240:8 or <s<strong>tr</strong>ong>Adept</s<strong>tr</strong>ong>_Pallet_Number)<br />
*DF1 <s<strong>tr</strong>ong>com</s<strong>tr</strong>ong>munication error: Invalid data s<strong>tr</strong>ing length* (-3002)<br />
A DF1 message has been received, or one is being sent, and the message has an odd<br />
character count other than 1.<br />
*DF1 <s<strong>tr</strong>ong>com</s<strong>tr</strong>ong>munication error: ENQ count exceeded* (-3004)<br />
After sending a message to the PLC, two ENQ requests have been sent without a<br />
response.<br />
*DF1 <s<strong>tr</strong>ong>com</s<strong>tr</strong>ong>munication error: NAK count exceeded* (-3003)<br />
After sending a message to the PLC, two NAK responses have been received.<br />
<s<strong>tr</strong>ong>Adept</s<strong>tr</strong>ong> <s<strong>tr</strong>ong>Cobra</s<strong>tr</strong>ong> <s<strong>tr</strong>ong>PLC600</s<strong>tr</strong>ong>/PLC800 Robot User’s <s<strong>tr</strong>ong>Guide</s<strong>tr</strong>ong>, Rev B 151