°C when instantiating an UDT with °C as measurement unit

I’m having an issue when instantiating an UDT where a parameter has °C for engineering unit.
°C gets changed to °C, which I suppose is caused by the fact °C is not interpreted as a UTF-8 character. Any hints?
I’m using Ignition 8.1.16.

What does ‘instantiating’ mean? I made a simple test UDT with °C as the parameter value, and it went through fine:

Overriding also works:

Are you creating instances/overrides through a script?

Hello @PGriffith.
Yep, by “instantiating” (I supposed this was the correct verb, but English is not my first language, sorry for that) I meant creating a new tag starting from an UDT.
When I make an override through a script I get °C in the engineering unit, while I get a null value when I simply create a new tag based on my UDT.
I’m attaching a video to show you my issue (and also my UDT export).

{ Not watching a video… }
Paul’s question was clearly driven by the fact that regular string constants in jython will mangle unicode. You need the use unicode strings instead.

# This will yield a mangled degree symbol
engUnit = '°C'
# This will preserve the degree symbol
engUnit = u'°C'

Hello @pturmel, thanks for your reply.
And what about having the correct engUnit in the UDT without overriding it using a script? u’°C’ doesn’t seem to work. The video was just 40 seconds long, though. :slight_smile:

EDIT: I’ve tried your solution in a Tag Event Script, but it still mangles unicode the way I described in my first post. I get: u’°C’.

Ok, I see it. That’s a bug.

1 Like

I have been attempting to replicate this via the video and the supplied export and have been unsuccessful. This issue could have something to do with the UDT definition that the ActualTemperature UDT member is using (CM/General/Parameters_Double) but unfortunately that wasn’t provided in the tag export provided. I did construct my own version based on the definition provided and was still unable to replicate this issue in 8.1.16.

I would like to try and rule out some other issues.

  1. What version of the Designer Launcher are you using? This is the application that is used to launch the designer, not the Designer itself.

  2. What is the locale and language of the OS your Ignition Gateway and your Client running the Designer set to?

  3. Can you provide me with a full export of all of your UDT definitions and not just the AX_r00 one? You can direct message me them if you don’t want to post them directly to this post.


1 Like

Hello @ggross!

  1. The Designer Launcher version is the last one: when I updated to the last version of Ignition, I was prompted to update the Designer Launcher as well. Is there a way to find out the version number?

  2. The language and locale of the OS the Gateway is running on is EN-us, while the one where I’m running my Designer is set to IT-it.

  3. I’ve sent you an export file with all my UDTs.

Thank you for your help!

Thanks for the additional information. Was able to duplicate it. Looks like it has something to do with the parent having a Parameter binding and it being overridden by a string. I have created a bug regarding the issue.


1 Like