This article covers loggers related to TCP/UDP device connections that were introduced in Ignition version 7.8.X.
Loggers in this article:
drivers.TCPDriver[{DeviceConnectionName}]
A series of loggers monitoring connection status and tag subscriptions using the TCP driver. {DeviceConnectionName} is denoted as the name of the specific TCP device connection in the Ignition config.
drivers.TCPDriver[{DeviceConnectionName}]
- Will notify us when the existing tags under the device are being read
- DEBUG log stating a count of tags under the TCP device that are being read:
Scheduled 3 tags to be read at 50ms.
- DEBUG log stating a count of tags under the TCP device that are being read:
drivers.TCPDriver[{DeviceConnectionName}].TCPConnection[{PortNumber}]
- Provides information about the device connection and the received message. {PortNumber} is denoted as the port number defined for the specific TCP device connection in the Ignition config.
- DEBUG log providing the output of the initialized connection and the received message. The latter will be reported each time new messages arrive and contain the full message in the log:
Connecting to 10.10.60.75:5000...
...
Data arrived: 21/09/2109:44:44 0200:15:39 2065657
...
- DEBUG log providing the output of the initialized connection and the received message. The latter will be reported each time new messages arrive and contain the full message in the log:
drivers.UDPDriver[{DeviceConnectionName}]
A series of loggers monitoring connection status and tag subscriptions using the UDP driver. {DeviceConnectionName} is denoted as the name of the specific UDP device connection in the Ignition config.
drivers.UDPDriver[{DeviceConnectionName}]
- Will show the output of the connection when it is first established.
- DEBUG log showing a successful device connection when it is first created, then disabled in the Ignition config:
Acquired connect permit, calling connect().
Releasing connect permit.
Disconnected -> Connected
…
Connected -> Terminated
- DEBUG log showing a successful device connection when it is first created, then disabled in the Ignition config:
drivers.UDPDriver[{DeviceConnectionName}].BasicTransactionProcessor
- Provides information about created subscriptions for a specific UDP device connection.
- DEBUG log for created / restarted tag subscriptions where {count} is denoted as the number of tags being created / restarted:
Processing transaction with sequence {...}
Adding {count} items.
…
Notifying callback of new subscription state: SubscriptionItem[{count}]
- DEBUG log for created / restarted tag subscriptions where {count} is denoted as the number of tags being created / restarted:
-
- TRACE log for an individual tag subscription that was created / restarted. {...} is the specific CompactLogix address for an existing tag’s opcItemPath:
Adding {...}
Creating AggregateSubscriptionItem for {...}
- TRACE log for an individual tag subscription that was created / restarted. {...} is the specific CompactLogix address for an existing tag’s opcItemPath:
UDPDriver[UDP].PayloadHandlerImpl
- Provides information about the received message.
- DEBUG log showing the contents of the received message. Will also mention missing fields that are not defined in the Ignition config for the device connection:
Handling payload: 21/09/2110:03:41 0200:05:29 5302056
No fields configured, setting message payload only.
- DEBUG log showing the contents of the received message. Will also mention missing fields that are not defined in the Ignition config for the device connection:
Comments
0 comments
Article is closed for comments.