3S_V3 Driver: Unexpected behaviour can occur when writing a WString variable value which exceeds the limitation defined in the PLC

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

• Checklist: Communication to TwinCat via BeckhoffNG driver

  Time estimate: 30 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. TwinCAT ADS communication library ...

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

• Setting values for DINT/UDINT variables of the S7_NT Driver from zenon runtime to PLC leads to value 0 in both zenon runtime and plc.

  Summary Setting values for DINT/UDINT variables of the S7_NT Driver from zenon runtime to PLC leads to value 0 in both zenon runtime and plc. This behaviour occurs when the following prerequisites are given: S7-Project created in Step 7 v. 55 ...

• The value (%v) in the dynamic limit text is not converted into the secondary unit

  Summary A dynamic limit text may be configured to display a variable´s value with the placeholder %v. It may further more be configured to display the variable´s measuring unit with the placeholder %u. If unit switch is enabled and the secondary unit ...