I'm migrating a server from 8.1.50 to 8.3.2. All the devices connected are Modbus TCP connections (modicons). It's an inherited mess that I'm trying to straighten out a touch.
There are a number of OPC tags that refer to modbus addresses that don't have a mapping in the PLC. Mostly bools.
In 8.1, those tags seem to semi-randomly be set to either T or F.
In 8.3, those same tags are returning an "Error" status, [null, Error("CreateMonitoredItems failed: Bad_NodeIdUnknown: The node id refers to a node that does not exist in the server address space."), Tue Jan 06 10:26:39 CST 2026 (1767716799767)]
Is that an expected difference in how 8.3 is handling such items? Or did I miss a setting somewhere? I prefer the Error, as it's more definitive for me as to which devices ACTUALLY have which tags.
Nothing changed, Bad_NodeIdUnknown with the Modbus driver probably means a bad/invalid address, which means either the address mapping isn't right, or the OPC Item Path isn't right.
If it's the OPC Item Path the likely cause would be something to do with UDT params resolving or not resolving... look at these tags and see what's going on.
Same tags. Looking at the tag diagnostics, there is a slight difference, and I'm guessing it's from the Ignition OPC-UA server. I know the modbus address is not mapped in the PLC, so that "false" that is getting returned on 8.1.50 isn't "real"
8.1.50:
Last Published Value:
[false, Error_Configuration("Bad_NodeIdUnknown: The node id refers to a node that does not exist in the server address space."), Mon Nov 10 09:24:49 CST 2025 (1762788289759)]
8.3.2:
Last Published Value:
[null, Error("CreateMonitoredItems failed: Bad_NodeIdUnknown: The node id refers to a node that does not exist in the server address space."), Tue Jan 06 10:26:39 CST 2026 (1767716799767)]
Those are effectively the same error, so whatever your problem is it's happening in 8.1 and 8.3.
They're the same underlying error, but the tag browser in 8.1.50 shows the tag as being perfectly fine, with a False value. In 8.3.2, it shows as "Error". And bindings react differently.
I think what you might be seeing is that we fixed the fact that checkboxes in the Tag Browser didn't indicate bad quality in any meaningful way. Your tags were never "perfectly fine" when they had bad quality.
Not sure about your bindings problem, maybe talk to support and explain the difference.
Gotcha. I'm glad you made the fix. As it's much easier having that bad quality be visible..
1 Like
Can you provide some screenshots of the difference you're seeing in the Tag Browser?
I'm starting to wonder if the improvement to uncertain/bad quality for booleans was actually implemented or just planned... in which case I don't know what you're seeing.
Definitely appears to be implemented.
8.1:
8.3:
1 Like