When you import Variable Tags from an OPCUA Server the tag names are truncated to 79 characters, this is sometime not enough. Duplicate tagnames are not allowed. You have to manually adjust all the names. For instance when you connect to a Plant SCADA OPCUA Server and import the variable tags the first part is always:
Objects\BrowseProvider\Cluster1\
Would be better to skip the Objects\BrowseProvider\ part and put Cluster1 into the cluster field, but this is maybe rather specific for the Plant SCADA OPC UA Server.
Guest
|
Idea business value
Would make it a lot easier to import variable tags from an OPC UA Server |
|
| Idea priority | 4 – Important to my company |
I am experiencing the same issue with OPC UA variable tag imports. The 79-character tag name limitation causes tag names to be truncated, resulting in duplicate names and requiring manual renaming of variables.
I also tried increasing the character limit directly in the variable.dbf file as a workaround. Although this seemed like a logical approach, it caused Citect SCADA to generate errors and the database could no longer be used reliably.
The current workaround is not practical for large projects because manually renamed variables lose the ability to be automatically updated from the OPC UA server database.
A proper solution that preserves unique OPC UA tag names during import (for example by allowing longer names or handling the namespace/path information separately) would significantly improve usability and reduce engineering effort.
Same problem detected when connecting to a codesys OPC UA server. Variable names are truncated resulting in the inability to obtain unique names. The only solution is to manually rename the variables, however losing the possibility of automatically updating the database. This update should have top priority.