Loggers - OPC-UA

This article covers loggers related to OPC-UA that were introduced in Ignition version 7.8.X.

Loggers in this article:

• DriverVariableNode[{DeviceConnectionName}]

• xopc2.client.OpcUaConnection

• xopc2.client.OpcUaConnection$UaSubscriptionChangeListener

• xopc2.client.OpcUaConnection$DataValueConsumer

• org.eclipse.milo.opcua.stack.client.handlers.UaTcpClientAcknowledgeHandler

• OPC-UA Server.ActivateSessionService

DriverVariableNode[{DeviceConnectionName}]

• Monitors the current state of all Tag subscriptions for a specific device connection. Will update at the rate of the defined Tag Group/Scan Class for each tag. {DeviceConnectionName} is denoted as the name of the specific device connection in the Ignition config.
  • TRACE log providing the current qualified value of a specific Tag subscribed to a device. nodeId will provide the OPC Item Path of existing Tags:
    

    Driver setting value value=11644, status=StatusCode[Severity=Good, Subcode=NotSpecified], source=Tue Sep 14 15:10:14 PDT 2021, server=null on DriverVariableNode@6d528c74[nodeId=[{DeviceConnectionName}]C5:0.ACC,nodeClass=Variable,dataTypeId=ns=0:i=4]

Back to top

xopc2.client.OpcUaConnection

A series of loggers that will monitor the creation and value change of tag subscriptions for an OPC-UA client.

xopc2.client.OpcUaConnection$UaSubscriptionChangeListener

• Monitors the creation of Tag subscriptions when an OPC-UA server is started/restarted.
  • DEBUG log of a successful subscription of 11 Tags for an existing Scanclass:
    

    Synchronizing subscriptions... Creating subscription 'Scanclass 'Default[default]'' @ 1000ms... Creating/deleting items on subscription 'Scanclass 'Default[default]''... nodesToAdd.size()=11 nodesToRemove.size()=0 Creating 11 items on subscription 'Scanclass 'Default[default]''... Setting MonitoringMode to Reporting for 11 of 11 items on subscription 'Scanclass 'Default[default]''... synchronizing subscriptions finished in 5ms. Re-synchronization scheduled=false

• • TRACE log showing an example of a failed attempt to subscribe to a specific tag. id provides the OPC Item Path of an existing Tag:
    

    Failed to create item 'NodeId{ns=1, id=[Micrologix]B3:6}': StatusCode{name=Bad_NodeIdUnknown, value=0x80340000, quality=bad}

Back to top

xopc2.client.OpcUaConnection$DataValueConsumer

• Monitors all value changes occurring on existing tag subscriptions in the OPC-UA server.
  • TRACE log showing an example of a Tag subscription that recently received a value change:
    

    nodeId=NodeId{ns=1, id=[Micrologix]B3:0}, clientHandle=8, value=15

Back to top

org.eclipse.milo.opcua.stack.client.handlers.UaTcpClientAcknowledgeHandler

• Monitors the request and acknowledgment of an initial connection to an OPC-UA server.
  • DEBUG log showing a successful connection to the Ignition OPC-UA server. Provides the IP and ports being used.
    

    Sent Hello message on channel=[id: 0xeceae68b, L:/127.0.0.1:58681 - R:localhost/127.0.0.1:4096]. Received Acknowledge message on channel=[id: 0xeceae68b, L:/127.0.0.1:58681 - R:localhost/127.0.0.1:4096].

Back to top

OPC-UA Server.ActivateSessionService

• By default (logger set to INFO), provides details on the user credentials being applied to an initialized OPC-UA server connection.
  • INFO log showing a successful authentication to an OPC-UA server:
    

    User "{schedule=Always, firstname=, notes=, language=null, username=opcuauser, lastname=}" connected.

Back to top