Hi @JDControlsLLC ,
There are a couple factors that can affect how the string is interpreted. One reason is the option selected under “IEC-61131 STRING type select” when importing the CODESYS tags in EB Pro.
Here is a forum post that goes into more detail on this option: link.
Another possibility is the data type used in CODESYS. If the STRING data type is used instead of WSTRING, the STRING data is represented as two characters per word when mapped to the HMI. If those bytes are then interpreted as UTF-16 Unicode, the two characters can be interpreted together as a single Unicode character, which may result in characters from Japanese or other Unicode character ranges being displayed.