4. When Execute changes to TRUE again, Busy changes to TRUE.
5. Execute is ignored if it changes to TRUE during instruction execution (i.e., when Busy is TRUE).
6. If an error occurs, several retries are attempted internally. The error code in ErrorID is not updated
during the retries.
7. When a communications error occurs, Error changes to TRUE and the value of ErrorID is stored.
Also, Busy and Done change to F
ALSE.
8. When Execute changes to FALSE, Error changes to FALSE.
Precautions for Correct Use
If Execute
changes back to FALSE before Done changes to TRUE, Done stays TRUE for only
one task period. (Example 1)
If you want to see if Done is TRUE at any time, make sure to keep Execute TRUE until you
confirm that Done is TRUE.
If Execute is TRUE until Done changes to TRUE, Done stays TRUE until Execute changes to
FALSE. (Example 2)
E
xecute
Done
Execute
Done
Busy
(Executing)
Busy
(Executing)
Changes to
FAL
SE in next
task period.
When Execute
changes to
FALSE, Done
returns to FALSE.
Example 1 Example 2
8-2-10
Response Codes
This section describes the response codes stored in the ErrorIDEx output variable if an error occurs
during execution of a CIP message communications instruction.
General Status Codes
As response codes, general codes are stored in the ErrorIDEx output variable (DWORD data) after
execution of a CIP communications instruction is completed.
If an additional code is added, the additional code is also stored.
General status code (1 byte)
Additional code (1 word)
Error
IDEx
31 23 16 15 024
General
status
code (hex)
Status name Description of status
00 Success Service was successfully performed by the object specified.
01 Connection failure A connection related to service failed along the connection path.
8 CIP Message Communications
8-35
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
8-2 CIP Message Communications Client Function
8
8-2-10 Response Codes
To Next Page
Loading...
Need help?
General
