3S_V3 Driver : The length of WSTRING variables is not considered during variable Import.

• Related Articles

• Checklist: Driver(s) cannot establish a reliable communication

  Time estimate: 60 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] ...

• MELSECA: Writing a variable of type WSTRING overwrites two times the string length

  Description With the MELSECA driver, variables of type WSTRING overwrite twice the length of the string. As a result, neighboring strings may be overwritten. This bug has been fixed. As expected, only the single string length is now written. To ...

• The datatype WSTRING of the MODRTU32 Driver does consider the Byte order for STRING Option in the Settings tab of the MODRTU32 Driver. This Option (Byte order for STRING) should only be considered by variables of type STRING but not by variables of type WSTRING.

  Summary The datatype WSTRING of the MODRTU32 driver gets decoded wrong. The Setting Byte order for STRING in the Settings Tab of the MODRTU32 driver affects the representation of a WSTRING variable. As a result, when having Modbus Standard ...

• The S7TIA driver does not correctly display the value of WSTRING variables in the Runtime. 

  Summary The S7TIA driver does not correctly display the value from the PLC for WSTRING variables in the Runtime. The S7TIA driver does however write the correct value to the PLC for WSTRING variables if they are modified in the Runtime.   ...

• FAQ: How can I browse an OPC UA Server using the zenon OPC UA Client Driver?

  Go to Drivers > New Driver Create a Driver of Type "OPC UA Client Driver" Open the Driver Configuration Go to "Connections" Create a new Connection Enter your Discovery URL Enter your Server URL manually or click the 3 dots to browse the Discovery ...