UDT Data Type Creation

#1

Hi,

In 7.9 when I imported tags from OPC, I could right click all those tags and select “Create Data Type from tags”.

Now in 8+ thats not possible anymore.

You can now just create a data type, copy the tags you want into the data type, and paste it while the datatype is selected.

However:
When you export the datatype as tags so you can edit it with notepad++ or similar tools, and then import it again, all the opc items paths are considered as strings and not a function. To make them bind correctly you have to edit each tag and then click “commit”.
Only then the path (which are complemented with udt parameters) gets completed.

In 7.9 it worked just fine.

Is there a way to make this easier?
Im dealing with HVAC/AHU units that consists of 500+ tags, and I got like 11 different vendors that I need to complete.

Clicking 500+ tags manually x 11 is abit pita when it worked flawlessly in 7.9

0 Likes

#2

Hi Lasse,

In 8.0, the “Create Type” functionality can now be found in the popup prompt when dragging selected tags from OPC Browser into the Data Types folder:

create%20data%20type
As for editing the OPC item paths in a text editor, any UDT tag props which are to be parameter bindings on import must be modified to include "bindType": "parameter" as part of its object. Otherwise as you’ve seen, they’ll be treated as values when the modified json tag file is imported.

Depending on the complexity of the parameter bindings you’d like to replace, you may find it easier to export the UDTs as xml instead, in which case boundValueType="parameter" would be added to the tag prop like so:

<Property name="opcItemPath" boundValueType="parameter">ns=1;s=[sim]_Meta:Ramp/Ramp{num}</Property>

0 Likes