Hi, first post here, I have a question about a certain behavior.
When I use the mouseover text expression to debug the problem I got:
Error_Configuration("Bad_NodeIdUnknown: The node id refers to a node that does not exist in the server address space.")
But, in the tag browser the quality appears “Good”. I already re-checked the bindings and nothing.
Its very weird because always the Error_Configuration or Bad Quality property seems to work fine with every tag, but this time the Quality its accusing something different to the “real” quality of the tag…
Did you copy the path from the opc tab? This error usually means there is a typo in the opcPath or it’s set to the wrong opcServer, from what I’ve seen. You might be missing the node info, if your path doesn’t start with “ns = 1; s =” (the integer after “ns =” may differ)
Thank you for the answer! Yes I've already checked, indeed this is an UDT, in the same window are another tag using the same UDT, the item paths follow the same structure. Moreover, the weird thing is that I'm reading the value in the mouseover text expression accesing to that problematic tag via the UDT Property passed to that PopUp (in this case). To give more context (images), the 4th alarm is missing, and I’m using the following expression for visibility (sorry if the spanish makes this a little confusing):
isGood({Root Container.Pump_UDT::Enclavamientos.Enclavamiento 4.Alarma})
missing,
Show your tag binding in your UI. (The evidence suggest the tag is good, and the binding isn't pointing at it.)
Generally not a good practice. Consider passing a tagpath string, and indirect binding within the popup.
1 Like
Thank you for the answer! Sorry, do you mean the visibility binding? I use the following, and I’m getting “false” as result.
isGood({Root Container.Pump_UDT::Enclavamientos.Enclavamiento 4.Alarma})
Also, the template that uses that Alarm UDT is giving also a “Bad Quality” behavior. (I mean the template that is seen in the images that has the “Rec” button to the right (Ack of the alarm).