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

• Related Articles

• The OPCUA server does not correctly handle limit texts (conditionname) with unicode characters

  Summary The OPCUA server does not correctly handle limit texts (conditionname) with unicode characters Description The OPCUA server does not correctly handle limit texts (conditionname) with unicode characters Issue Number: 93838 Fixed on Date: ...

• 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] ...

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

• Writing a variable of the OPCUA client driver in the zenon logic via externally visible does not set the value correctly

  Summary With an OPCUA client driver in zenon and a variable that is set to "externally visible" writing this variable in a zenon logic program does not correctly send this value to the OPCUA server. Instead of the correct value, the value "0" may be ...

• BeckhNG Driver stops after set more than 130 characters to a string variable in runtime.

  Summary After set more than 130 charates to a string value via dialogbox the BeckhNG driver stops. Variable is set to can handle 254 characters. Description After set more than 130 charates to a string value via dialogbox the BeckhNG driver stops. ...