# How does symbols work for Ignition Tags?

**URL:** <https://forum.inductiveautomation.com/t/how-does-symbols-work-for-ignition-tags/78238>\
**Category:** Ignition\
**Created:** [August 22, 2023, 3:05pm UTC](https://forum.inductiveautomation.com/t/how-does-symbols-work-for-ignition-tags/78238 "2023-08-22T15:05:22Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![darren.sisco](https://avatars.discourse-cdn.com/v4/letter/d/ec9cab/32.png) [@darren.sisco](https://forum.inductiveautomation.com/u/darren.sisco)\
**Post date:** [August 22, 2023, 3:05pm UTC](https://forum.inductiveautomation.com/t/how-does-symbols-work-for-ignition-tags/78238/1 "2023-08-22T15:05:22Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 22, 2023, 3:29pm UTC](https://forum.inductiveautomation.com/t/how-does-symbols-work-for-ignition-tags/78238/2 "2023-08-22T15:29:58Z")

</div>

Are you talking about the name of this tag or its OPC Item Path?

Can you share more information / screenshots?

---

<div class="post-metadata">

**Author:** ![darren.sisco](https://avatars.discourse-cdn.com/v4/letter/d/ec9cab/32.png) [@darren.sisco](https://forum.inductiveautomation.com/u/darren.sisco)\
**Post date:** [August 22, 2023, 3:31pm UTC](https://forum.inductiveautomation.com/t/how-does-symbols-work-for-ignition-tags/78238/3 "2023-08-22T15:31:13Z")

</div>

nsu=KEPServerEX;s=SPR\_FIN\_CAVFRN\_USXX0037.ESMI.DB\_ESMI\_GROUP06\_ConditionMonitoring.ConditionParams.0.r\_gasConsuptionTotal\_mÂ³

---

<div class="post-metadata">

**Author:** ![darren.sisco](https://avatars.discourse-cdn.com/v4/letter/d/ec9cab/32.png) [@darren.sisco](https://forum.inductiveautomation.com/u/darren.sisco)\
**Post date:** [August 22, 2023, 4:02pm UTC](https://forum.inductiveautomation.com/t/how-does-symbols-work-for-ignition-tags/78238/4 "2023-08-22T16:02:40Z")

</div>

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'.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 22, 2023, 4:07pm UTC](https://forum.inductiveautomation.com/t/how-does-symbols-work-for-ignition-tags/78238/5 "2023-08-22T16:07:18Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 22, 2023, 4:11pm UTC](https://forum.inductiveautomation.com/t/how-does-symbols-work-for-ignition-tags/78238/6 "2023-08-22T16:11:40Z")

</div>

Okay, it actually works fine in my testing. Maybe Kepware is encoding the NodeId strangely.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/9/d98413bf72b5e4280eb384a4ce6b014c8f43ca41.jpeg)

A Wireshark capture where you browse and then subscribe would be useful. You'll have to turn off security for the connection.

---

<div class="post-metadata">

**Author:** ![darren.sisco](https://avatars.discourse-cdn.com/v4/letter/d/ec9cab/32.png) [@darren.sisco](https://forum.inductiveautomation.com/u/darren.sisco)\
**Post date:** [August 22, 2023, 4:20pm UTC](https://forum.inductiveautomation.com/t/how-does-symbols-work-for-ignition-tags/78238/7 "2023-08-22T16:20:12Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 22, 2023, 4:21pm UTC](https://forum.inductiveautomation.com/t/how-does-symbols-work-for-ignition-tags/78238/8 "2023-08-22T16:21:43Z")

</div>

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.
