String commands containing non-standard ASCII characters may not be written correctly to the PLC.

• Related Articles

• Checklist: Process closes unexpectedly (***Non-reproducible***)

  Time estimate: 45 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

• The OPCUA32 client driver does not handle correctly string variable values that contain non-latin or non-ansi characters

  Summary String variables of the OPCUA32 client driver do not correctly display the string value if the string contains non-ansi characters or non-latin characters. DescriptionString variables of the OPCUA32 client driver do not correctly display the ...

• When writing a value to a STRING variable of MODBUS_ENERGY Driver with more than 64 characters, only 64 characters including null termination are written.

  Summary When writing more than 64 characters to a STRING variable of MODBUS_ENERGY Driver, only 64 characters including null Termination are written. DescriptionWhen writing more than 64 characters to a STRING variable of MODBUS_ENERGY Driver, only ...

• Service Engine under Linux supported only ASCII characters

  Description Service Engine zenon 11 supports only ASCII characters under Linux. Strings which are not included in the ASCII table are not supported. Thus also LOG entries are not written. This has been fixed. To take advantage of this fix: Update to ...

• Mitsubishi FX32 driver does not correctly write strings with an odd number of characters

  Summary The mitsubishi FX32 driver does not correctly write string values which have an odd number of characters DescriptionThe mitsubishi FX32 driver does not correctly write string values which have an odd number of characters Solution An issue has ...