Variable of the DNP3_NG driver not marked INVALID when reading a point explicitly, with an invalid point number

• Related Articles

• The DNP3_NG driver may communicate to the wrong point index after a reload of the runtime under specific circumstances

  Summary When changes are made to the variable administration in the editor and changed runtime files are compiled and the runtime is reloaded, a variable that is advised more than once in the runtime may use the variable ID instead of the DNP point ...

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

• FAQ: How can I monitor and react on the communication status of my devices with zenon?

  Data quality is very important to the integrity of a HMI or SCADA system. As such, zenon has numerous ways to monitor the communication status of different devices within your automation environment. Here are some options that you can use in your ...

• With the DNP3_NG driver, not all significant digits of a double float analog input are mapped to the LREAL variable in the runtime

  Summary When a DNP analog input object, group 30 variation 6 or group 32 variation 6 or variation 8 is received by the DNP3_NG driver, it is correctly considered a double precision float. The value received in the runtime however did not contain all ...

• FAQ: Why are there small RED squares on the dynamic elements in the zenon Service Engine? 

  Small red squares on the dynamic elements in zenon Service Engine indicate that the INVALID Bit (aka I-Bit) is active for the linked variable. The INVALID Bit is set true automatically by the zenon drivers for variables when there is an underlying ...