Legacy double bit binary input variables of the DNP3_TG driver with an offset > 255 are invalid in the runtime

• Related Articles

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

• BuRPVI driver: all Driver variables have invalid (I-Bit) status

  Summary All variables from object type Driver variable of the BuRPVI driver get an invalid status. No error in the diagnosis viewer logged. Description All variables from object type Driver variable of the BuRPVI driver get an invalid status. No ...

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

• Some statistics variables of the DNP3_TG master driver are not updated when objects groups are received from the outstation

  Summary The statistics variables "unsolicited response objects received" (offset 907) and "solicited response objects received" (offset 906) of the DNP3_TG DNP3 master driver are not updated when the master receives object groups from the outstation. ...

• Incorrect negative values in the runtime under specific circumstances for variables of the the DNP3_TG driver

  Summary Negative values for analog inputs and analog outputs with specific variations that are received from the outstation by the DNP3_TG driver, are not displayed correctly in the zenon runtime. When using variations reprsenting single precision ...