Protocol diagnostics counters
Diagnostics are available for the following protocols:
- PCCC Dispatchers
- CIP Unconnected Dispatchers
- CIP Connected Dispatchers
- Connection ID
Each Dispatcher entry is created the first time an Engine Socket of that type is opened by a client (for example a data provider or a browser). Once created, these entries persist until the
FactoryTalk Linx
process is shut down.There will be zero or more entries under the Dispatchers that specify paths to target devices. These entries come and go with the Dispatcher objects themselves, which are created and maintained as needed as Engine Sockets are opened and closed by the clients.
The CIP Connected Dispatchers is a little different in that multiple Dispatcher objects can be created for a given path, each managing a separate CIP connection. For each of these Dispatchers/Connections created, a separate entry is provided that is labeled according to the connection ID used internally by the
FactoryTalk Linx
engine (that is, the CIP protocol).Common to PCCC Dispatchers, CIP Unconnected Dispatchers, CIP Connected Dispatchers
- Limit for outstanding requests
- Peak size of request queue
- Requests canceled
- Requests currently in queue
- Requests currently outstanding
- Requests failed on send
- Requests queued
- Requests sent
- Requests timed out after send
- Requests timed out in queue
- Responses received
Specific to CIP Connected Dispatchers
Provide Feedback