Hello, got a new float tag they are wanting recorded. It seemed like business as usual. However, the tag they are using in the PLC is "r_gasConsuptionTotal_m³". We access this tag through Kepware so it sees the same. I used UA Expert to confirm this. However, when I drive to the tag in Ignition, it sees "r_gasConsuptionTotal_m³". So it adds a weird 'Â' to it. It also comes back as a status of "BAD". If I remove the extra 'Â', it comes back with a status of "Error_Configuration" and its complaining the node ID does not exist in the space. I've never ran into a tag trying to use that cubic symbol before. Is this why Ignition is not happy with it?
Are you talking about the name of this tag or its OPC Item Path?
Can you share more information / screenshots?
nsu=KEPServerEX;s=SPR_FIN_CAVFRN_USXX0037.ESMI.DB_ESMI_GROUP06_ConditionMonitoring.ConditionParams.0.r_gasConsuptionTotal_m³
I don't see a document supporting the use of symbols in OPC Item Path for v8.1 Ignition. I'm thinking its an illegal character. I'm asking the Kepserver team to change that to just a standard '3'.
Hmm, that field should support any UTF-8 string.
This might be some kind of bug in Ignition, I'll have to see if I can replicate it.
Okay, it actually works fine in my testing. Maybe Kepware is encoding the NodeId strangely.
A Wireshark capture where you browse and then subscribe would be useful. You'll have to turn off security for the connection.
Yes, I agree, its looking like a kepware issue. Its crunching it up or it was not put in right to start with. Thanks for letting me know its UTF-8 compliant. That does help a lot in fighting the kepware guys for a resolution.
If you can get a Wireshark capture I'd really like to see it. Any String in OPC UA comms should be UTF-8, and I'm not able to explain why/how this is happening, especially since you said it works in UaExpert.