Communication instructions Chapter 9
Rockwell Automation Publication 2080-RM001D-EN-E - February 2015 179
CIPSTATUS status bits
The CIPSTATUS status bits are set based on the status of the message execution,
the communication buffers, and the rung conditions.
- - - - - - - - - - - 4 3 2 1 0
Bit Name Description Behavior
0 EN Enable Set when the rung goes true and remains set until either the DN bit or the ER bit is set and the rung goes false.
1 EW Enable Waiting Set when the communication buffer is allocated for the message request. Cleared when the ST bit is set.
2 ST Start Set when the message has been transmitted and is waiting for a reply. Cleared when the DN bit is set.
3 ER Error Set when message transmission fails. An error code is written to ErrorID. The ER bit and error code values are cleared the next
time the rung goes from false to true.
4 DN Done Set when the message is transmitted successfully. The DN bit is cleared the next time the rung goes from false to true.
When the Done bit is set, all other bits are cleared to indicate the MSG completed successfully. When an error is detected and
the Error bit is set, the other status bits (EN/EW/ST) are not cleared.
CIPSTATUS error codes
The following table describes the error codes that are displayed in the ErrorID and
SubErrorID fields of the CIPSTATUS parameter when the ER bit is set.
ErrorID
code
SubErrorID Error code description
33 Parameter configuration related errors
32 Bad Channel number.
36 Unsupported CIP connection type.
40 Unsupported CIP symbolic data type.
41 Invalid CIP symbol name.
43 Unsupported CIP Class value or MemberID count.
48 The instruction block’s input data array size is not sufficient.
49 Invalid target path.
50 Bad service code.
51 The instruction block’s transmit data array size is too big for CIP communication.
Note: The maximum length for the user data to be transmitted varies for different message configurations. If the total
CIP message payload (including user data and CIP message overload) is beyond 504 bytes, an error 0x21 (subError
0x33) is reported.
55 Timeout related errors
112 Message timed out while waiting in the message wait queue.
113 Message timed out while waiting for the a connection to the link layer to be established.
114 Message timed out while waiting to transmit to the link layer.
To Next Page
Loading...
