Messaging
The CIP Messaging counters provide global information, and are not related to a specific driver. These counters are not available via RSWho. They are only available from
Communications > CIP Diagnostics
. The following is the list of diagnostic counters shown and the definition of each.PCCC requests received | Total number of PCCC requests received by RSLinx Classic encapsulated in a CIP message, either unconnected or via a CIP Messaging connection made with the RSLinx Classic CIP Message Router. These PCCC requests are extracted and forwarded to their intended destination (for example, the DDE Server or a client application registered on the RSLinx Classic virtual link). |
PCCC replies canceled | Total number of PCCC requests received by RSLinx Classic encapsulated in a CIP message, but that were canceled before RSLinx Classic returned a response. |
PCCC replies returned | Total number of PCCC replies that were encapsulated and returned by RSLinx Classic in a CIP message in response to PCCC requests received by RSLinx Classic encapsulated in a CIP message. |
CIP requests received | Total number of CIP messages handled by RSLinx Classic, either for internal processing, for forwarding to another device, or for forwarding to another application. |
CIP replies canceled | Total number of CIP messages handled by RSLinx Classic, but that were canceled before RSLinx Classic returned a response. |
CIP replies returned | Total number of CIP replies returned by RSLinx Classic in response to CIP messages received by RSLinx Classic. |
MR connections open | Total number of CIP Messaging connections currently open to the RSLinx Classic CIP Message Router. A network device (such as a 1756-DHRIO) establishes these connections to send CIP messages to RSLinx Classic. |
MR connections requested | Total number of CIP Messaging connections that devices attempted to open with the RSLinx Classic CIP Message Router. |
MR connections accepted | Total number of CIP Messaging connections that devices attempted to open with the RSLinx Classic CIP Message Router, and that RSLinx Classic accepted. |
MR connections closed | Total number of CIP Messaging connections that devices established with the RSLinx Classic CIP Message Router, but that were closed by the connection originator. |
MR connections timed out | Total number of CIP Messaging connections that devices established with the RSLinx Classic CIP Message Router, but that timed out due to inactivity. This is normal behavior. |
MR connection receipts | Total number of CIP requests received on CIP Messaging connections established with the RSLinx Classic CIP Message Router. |
MR connection sends | Total number of CIP responses returned on CIP Messaging Connections established with the RSLinx Classic CIP Message Router. |
Unconnected requests outstanding | Total number of CIP unconnected requests RSLinx Classic sent, but for which no response has been received. |
Unconnected requests sent | Total number of CIP unconnected requests RSLinx Classic sent. |
Unconnected requests failed | Total number of CIP unconnected requests RSLinx Classic was unable to send because of failure to obtain some resource. If an unconnected send fails in this manner, RSLinx Classic returns a response with a CIP general status of 1 and an extended status of 0204 (hex). This number should be zero. |
Unconnected requests canceled | Total number of CIP unconnected requests RSLinx Classic sent, but that were canceled, due for example to the sending application being closed. Once a request is canceled, RSLinx Classic will not return any response. |
Unconnected requests completed | Total number of CIP unconnected requests RSLinx Classic sent, and for which a response was received and returned to the sender of the request. |
Unconnected requests timed out | Total number of CIP unconnected requests RSLinx Classic sent, but that timed out before a response was received. If a request times out, RSLinx Classic returns a response with a CIP general status of 1 and an extended status of 0204 (hex). Timeouts may indicate that the timeout interval supplied with the request is too short, that the network load is too heavy, that a target (or bridge) device is not there (or is not communicating), or that buffers are being overrun in the target (or bridge) device. |
Fragmentation NAKs received | Total number of fragmentation NAKs received in response to CIP unconnected requests RSLinx Classic encapsulated in PCCC messages and sent over a network using the PCCC fragmentation protocol. |
Provide Feedback