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.

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

• When using a Driver in mode Simulation - programmed variables of type UDINT are not supporting values where the highest bit is set.

  Summary When using a Driver in mode Simulation - programmed and setting a value bigger than 2147483647 (7FFFFFFFh) on a variable of type UDINT in the zenon runtime the value will always be 2147483648 (80000000h). DescriptionWhen using a Driver in ...

• Service Engine: S7TIA Driver - crashes on reconnect PLC

  Description The Service Engine has a connection to a S7TIA PLC. If the Service Engine loses the connection and the variables get the status "invalid", the S7TIA Driver is terminated unexpectedly after reconnecting. This error has been fixed. To ...

• 3S_ARTI_NG Driver : It is not possible to write STRING variables in zenon runtime Version 7.50, to a Codesys PLC (V2.3)

  Summary It should be possible to write to STRING variables in the zenon runtime Version 7.50 to a Codesys (V2.3) PLC. In the Diagviewer, a "Poke" is sent to the PLC with the value "null". STRING variables which are written by the PLC are however ...

• The OPCUA client driver should be able to represent special values in the runtime

  Summary The special values NaN, NULL, +infinity and -infinity that variables in an OPCUA server can have, currently cannot be represented in the runtime. Description The special values NaN, NULL, +infinity and -infinity that variables in an OPCUA ...