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

• Related Articles

• FAQ: What are the different zenon drivers modes?

  All Service Engine process-driven drivers can run in four different modes, mainly allowing you to switch between active hardware connection and values simulation. While "Hardware" allows establishing a connection to the target device(s) and its the ...

• When using a driver in mode Simulation - programmed, in the zenon runtime an empty string of a variable of type string can`t be read when setting an empty string via the zenon logic workbench.

  Summary An empty string can`t be read in the zenon runtime when using a driver in mode Simulation - programmed and setting an empty string via the zenon logic workbench. Therefore in the zenon runtime the string variable still shows the prior string ...

• When using the Opc2Cli32 Driver in the zenon runtime and using first the Driver command "switch to Simulation mode" (with Opc2Cli32 Driver set to "Hardware" mode in the Editor) and then using the Driver command "switch to Hardware mode" the variables will become invalid and have the Status "switched off" instead of SPONT.

  Summary When using the Opc2Cli32 Driver in the zenon runtime and using first the Driver command "switch to Simulation mode" (with Opc2Cli32 Driver set to "Hardware" mode in the Editor) and then using the Driver command "switch to Hardware mode" the ...

• When using a Driver in mode "Simulation - static" and in the zenon runtime the Driver command "Switch to Hardware mode" is executed, variables of the corresponding Driver get INVALID (correct) but when then executing the Driver command "Switch to Simulation mode" the variable stays INVALID but gets also SPONT.

  Summary When performing the Driver command "Switch to Hardware mode" in the zenon runtime variables of a Driver which is running in mode "Simulation - static" get INVALID (correct). When then performing the Driver command "Switch to Simulation mode" ...

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