BeckhNG driver: RDA archive recording is started at runtimestart without trigger

BeckhNG driver: RDA archive recording is started at runtimestart without trigger

Summary

RDA archive recording is started at runtimestart without trigger. The memory usage of the driver goes up until its maximum and above, ending with unhandled exception.

Description

RDA archive recording is started at runtimestart without trigger. The memory usage of the driver goes up until its maximum and above, ending with unhandled exception.

Solution

RDA is now initialized correctly for all RDA-variables.



Issue Number: 29473
Fixed on Date: 30.4.2013
Versions: 7.00 0 BUILD 9
    • Related Articles

    • 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 ...
    • Driver configuration cannot be opened and also no new driver can be created.

      If a Service Engine is started as a windows service also zenDrvOpsManager is running as a service. Thus zenDrvOpsManager cannot open a user interface for driver configuration and the Engineering Studio seems frozen. Running a Service Engine as a ...
    • BeckhNG unhandled exception when using RDA archiving

      Description When using RDA archiving for the Beckhoff NG driver, an unhandled error message occurs in the Service Engine. The Service Engine is terminated. This error has been fixed. To benefit from this fix: Update your zenon Software Platform to ...
    • Archive Evacuation for RDA Archive not working for *.arx archives.

      Summary Historian RDA Archive doesn't evacuate intern archive format *.arx archives DescriptionHistorian RDA Archive doesn't evacuate intern archive format *.arx archives Solution Evacuation for RDA archive working. Issue Number: 37195 Fixed on Date: ...
    • CNet driver recording incorrect values

      Description The CNetDrv driver recorded incorrect values (e.g. 0 instead of 1) because the receive buffers in the driver were not reset correctly when the connection was terminated. The issue has been addressed and the recording behavior is now as ...