ALLENDF1 driver: datablock 0, offset 3 cannot be read in specific circumstances

• Related Articles

• MELSECA driver cannot read/write file regster variables above offset 65535

  Summary MELSECA driver cannot read/write variables of object type file regster above offset 65535 If higher offsets are used it seem to work, but does not write on the correct address. Or the variable gets an invalid status. Description MELSECA ...

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

• AllenDF1 driver: FLOAT and STRING variables show wrong values when the offset considers data type flag is active on driver configuration

  Summary In specific project configuration/offset constellation invalid Bit is set when a FLOAT variable is seen in a screen even if all offset configuration is correct. The problem occurs when in the driver configuration it is enabled the "Offset ...

• DNP3_TG: Driver does not / cannot switch to redundant connection under specific circumstances

  Summary DNP3_TG driver does not switch to redundant connection under certain circumstances. This has been fixed. Description DNP3_TG driver does not switch to the redundant connection if the TCP connection to a Terminal Server is established but the ...

• OPCUA32: driver crashes on driver start command under specific circumstances

  Summary The OPCUA32 driver closes unexpectedly under specific timing conditions when the driver is stopped and started using driver command functions. Description The OPCUA32 driver closes unexpectedly under specific timing conditions when the driver ...