I'm actually able to work with STRINGs in C-POUs, but run into issues when I try to use WSTRINGs which would support characters that are outside of the base ASCII set.

Using STRING to try to print the degree symbol gives me the following warning and will compile but won't print correctly once it's installed and running on the display.
   - illegal character encoding in string literal In: wDiagSignals Line: 282 Column: 38 Category: Lexical or Preprocessor Issue

Using WSTRING and running the output of the POU directly to the Screen Definition gives me the following compile-time error.
   [CHPARGU1] Unsupported POU Call: {POU: wDiagSignals cannot be called directly from GUIDE code because it is using unsupported interface item(s): wstring, }.


Can WSTRINGs be used this way with ST-POUs?  It seems like it's specifically a limitation of the graphical portion of the environment rather than a C-POU vs ST-POU thing.  I will do some testing with ST-POUs today.

I'm attempting to generate some strings from within a POU that include unicode symbols like the Degree symbol and the Greater-Than-Equal symbol.

I've tried a few different things so far, but nothing has worked.

Basically, I want to take the output of a POU and than insert that into a Screen Definition as a STRING.  Is this possible?

Tor, THANK YOU! That was driving me nuts.  I could not manually add the files and the update center was not doing anything.

So if anyone else has the same issue, deleting the BookCase.xml file worked for me.

Thank you again,
Brian F.

Looks like I'll need to contact tech support.  I uninstalled the Service Tool, rebooted the computer and then reinstalled and nothing changed.

One could also make the update software an install-free executable. That would make the perception of a "long procedure" shorter