Sprecon870: ALT_VAL Bit behaves different depending on used Driver Object Type (PLC Marker vs Group)

• 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 accessing user definied structures with a size larger than 65k the LOGIX_ODVA driver behaves unexpectedly.

  Summary When the LOGIX_ODVA driver accesses user defined structures of driver object type PLC Marker, the LOGIX_ODVA behaves unexpectedly. DescriptionWhen the LOGIX_ODVA driver accesses user defined structures of driver object type PLC Marker, ...

• Process Gateway IEC870Slave should map status bit ALT_VAL of variable to flag 'Substituted'

  Summary When zenon variable has ALT_VAL status bit (bit 27) the Process Gateway iec870Slave sends value changes in ASDU with quality descriptor flag IV ('invalid') or NT ('not topical'). It should send, in quality descriptor in ASDU, the flag SB - ...

• Checklist: Communication to TwinCat via BeckhoffNG driver

  Time estimate: 30 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. TwinCAT ADS communication library ...

• When using multidimensional arrays with driver object type special markers of the LOGIX_ODVA driver, the LOGIX_ODVA driver behaves unexpectedly when trying to read the values of those array variables during runtime of zenon.

  Summary When the LOGIX_ODVA driver reads variable values of multidimensional arrays with driver object type special markers during zenon runtime, the LOGIX_ODVA driver behaves unexpectedly when trying to read the values of those array variables. ...