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

• Related Articles

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

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

• BuRPVI: Sporadically some datapoints do not receive status (SPONT) or receive INVALID when starting service Engine

  Description Sporadically some variables from the BuR-PVI driver with the driver object type "PLC marker" do not receive a status (SPONT or INVALID) when the Service Engine is started. No PVI events are sent initially for these datapoints. This error ...

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

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

  Summary Legacy double bit binary input variables of the DNP3_TG driver with an offset > 255 are invalid in the runtime. Legacy double bit binary input variables with a lower offset than 255 correctly combine two regular binary input points into a ...