I’m trying to import tags into Ignition using a JSON file. These tags are structured as UDTs, and some of the IEDs use IEC 61850. As an example, here is one of the tags used inside a UDT:
After importing the JSON, all of the tag parameters look correct except for the “OPC Item Path”, which shows the following error:
If I click at the end of the OPC Item Path field and simply press Space, the error disappears and the tag starts working normally.
Has anyone seen this bizarre behavior before?
Why would the OPC Item Path be invalid until I manually add a space at the end, even though the JSON value is identical?
Your OPC Item Path has an embedded parameter. In imports, you cannot just stick those into the string value of the tag property--there must be a nested JSON binding object. Interpreting the string value to create the binding is a feature of the designer tag editor, not the import machinery.
Export and examine the JSON of a UDT member tag that has a working binding to see the structure your import needs.
I have added the “ns=1;s=[ACB]{IED}LD0/MMXU1.TotW.mag.f” manually, and it is working with no issue, when I use exactly the same address using importing the JSON file, the error comes up.
ACB: is driver name
IED: the parameters used as STRING.
Error("CreateMonitoredItems failed: Bad_NodeIdUnknown: The node id refers to a node that does not exist in the server address space.")
The confusing part is that addresses are identical but one is working (Manual insert) , JSON is not working.
Shall I consider any thing that seems to be missed?
Phil gave you the answer, you're not building your json correctly. You can find this if you import your tag, do the space trick to fix it, re-export it and then edit it in a text editor and look for the difference.
You'll find you're missing bindType line in your original
