CIP Dispatching
The CIP Dispatching 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."Fast" PCCC requests via Messaging | Total number of "fast" PCCC requests that needed to be encapsulated for transmission over a network (for example, ControlNet) using the CIP Messaging protocol. These requests are queued and then sent either unconnected or connected depending on the RSLinx Classic configuration. Most PCCC commands are "fast" requests, including diagnostic commands and most types of reads and writes. |
"Slow" PCCC requests via Messaging | Total number of "slow" PCCC requests that needed to be encapsulated for transmission over a network (for example, ControlNet) using the CIP Messaging protocol. These requests are queued and then sent either connected or unconnected depending on the RSLinx Classic configuration. Slow PCCC commands include Read Modify Write and many of the programming commands. |
"Fast" PCCC requests via DHRIO | Total number of "fast" PCCC requests that needed to be transmitted over a network (for example, ControlNet) using the CIP protocol to a ControlLogix Gateway and out a DH+ channel of a 1756-DHRIO module. Most PCCC commands are "fast" requests, including diagnostic commands and most types of reads and writes. |
"Slow" PCCC requests via DHRIO | Total number of "fast" PCCC requests that needed to be transmitted over a network (for example, ControlNet) using the CIP protocol to a ControlLogix Gateway and out a DH+ channel of a 1756-DHRIO module. Slow PCCC commands include Read Modify Write and many of the programming commands. |
Requests canceled | Total number of PCCC requests that needed to be transmitted using CIP but that were canceled by the sender of the PCCC request, due for example to the sending application being closed. No PCCC response is returned. Once queued, a PCCC request may be canceled either before or after it is encapsulated and sent. |
Requests not sent | Total number of PCCC requests that needed to be transmitted using CIP but that could not be sent, because the provided route or data were not acceptable or because resources could not be obtained. A PCCC error response with a STS of 20h is returned to the sender of the request. These errors may indicate that the configuration for PCCC encapsulation in CIP is throttling communication too much to handle the application load. |
Requests sent unconnected | Total number of PCCC requests that RSLinx Classic encapsulated and sent via CIP unconnected messaging. |
Requests sent connected | Total number of PCCC requests that RSLinx Classic encapsulated and sent via CIP connections. |
Requests timed out unconnected | Total number of PCCC requests that RSLinx Classic encapsulated and sent via CIP unconnected messaging, but that timed out before a response was received. A PCCC error response with a STS of 05 is returned to the sender of the request. Timeouts may indicate that the timeout interval supplied with the PCCC 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. |
Requests timed out on connection | Total number of PCCC requests that RSLinx Classic encapsulated and sent via CIP connections, but that timed out before a response was received. A PCCC error response with a STS of 05 is returned to the sender of the request. Timeouts may indicate that the timeout interval supplied with the PCCC request is too short, that the network load is too heavy, or that a target (or bridge) device has failed. |
Requests failed with connection | Total number of PCCC requests that RSLinx Classic encapsulated and sent via CIP connections that timed out before a response was received. A PCCC error response with a STS of 20h is returned to the sender of the request. These errors may indicate that the network load is too heavy, or that a target (or bridge) device has failed. |
CIP error responses received | Total number of PCCC requests that RSLinx Classic encapsulated and sent via CIP messaging, connected or unconnected, but that received a CIP error response. A PCCC error response with a STS of 20h is returned to the sender of the request. These errors may indicate that the timeout interval supplied with the PCCC request is too short, that the network load is too heavy, that a target (or bridge) device has failed or is not there (or is not communicating), or that buffers are being overrun in the target (or bridge) device. |
PCCC responses received | Total number of PCCC responses that were received for PCCC requests that needed to be transmitted using CIP. The response is returned to the sender of the request. |
Connections open | Total number of CIP connections currently open for sending encapsulated PCCC requests. |
Connections attempted | Total number of CIP connections RSLinx Classic attempted to open for sending encapsulated PCCC requests. |
Connections established | Total number of CIP connections RSLinx Classic attempted to open for sending encapsulated PCCC requests and that were successfully established. |
Connections rejected | Total number of CIP connections RSLinx Classic attempted to open for sending encapsulated PCCC requests but that were rejected by the target device (or an intervening bridge). Devices support a limited number of connections, and a nonzero count may mean that overall demand for these connections in the system is surpassing these limits. A nonzero count may also indicate that the network load is too heavy, that a target (or bridge) device has failed or is not there (or is not communicating), or that buffers are being overrun in the target (or bridge) device. |
Connections closed | Total number of CIP connections RSLinx Classic established for sending encapsulated PCCC requests but that were closed due to inactivity. RSLinx Classic attempts to open as many connections as necessary to handle the PCCC traffic, up to the configured maximum, but if traffic drops off RSLinx Classic attempts to close the unneeded connections. |
Connections timed out | Total number of CIP connections RSLinx Classic established for sending encapsulated PCCC requests but that were timed out. A nonzero count may indicate that the network load is too heavy, or that a target (or bridge) device has failed. |
Connections dropped | Total number of CIP connections RSLinx Classic established for sending encapsulated PCCC requests that were dropped, generally because an application terminated. |
Provide Feedback