Tag references through the FactoryTalk Linx OPC UA Connector fail to communicate after an OPC UA Server changes its namespace index

Possible cause and solution
  • When the FactoryTalk Linx OPC UA Connector detects tags that have duplicate names, the namespace index and node ID are added into the tag reference used by FactoryTalk Clients. Example: [UAServerName]\Demo.@UA_NodeId:ns=2;s=Demo. If the OPC UA Server changes its namespace index after these tags have been browsed, these references will not connect properly because the node ID and namespace index are incorrect.
    To solve this issue, use these steps to refresh the tag names.
    1. In
      FactoryTalk Administration Console
      Explorer
      , right-click the FactoryTalk Linx OPC UA Connector, then select
      Properties
      .
    2. In
      FactoryTalk Linx OPC UA Connector
      , select
      OPC UA Servers
      .
    3. Highlight an
      OPC UA Server
      , then select
      Refresh Tag Names
      .
    4. In
      Refresh Tag Names
      , select the
      Continue with reset option
       to restart the FactoryTalk Linx OPC UA Connector service.
    5. For each tag that included the OPC UA Server’s node ID, use the client software that requested the data (Example:
      FactoryTalk View Studio
       or
      FactoryTalk Historian
      ) and re-browse the desired tag to capture the updated reference with the new namespace index.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal