Archive with event-triggered recording saves wrong values after runtime was restarted

• Related Articles

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

• When the API is used to write archive values with future timestamps, the data cannot be shown with timefilters other than "No timefilter"

  Summary When the API is used to write archive values with future timestamps, the data cannot be shown with timefilters other than "No timefilter". If a specific time filter is set, no data is shown in a trend/report/archive revision screen. ...

• MetadataSynchronizer API-Event 'SynchronizationCompleted' sporadically does not trigger

  Summary The event is now always triggered correctly. Description The event is now always triggered correctly. Information Crude: Program-which-waits-for-the-event needs a timeout; after the timeout it has to check independently in ...

• Historian On change archive in start image stores wrong time

  Summary 'On change' archive in start image stores variables having internal time stamp with wrong time. Description'On change' archive in start image stores variables having internal time stamp with wrong time. Solution Time for a record is now taken ...

• Sometimes archive entries are lost when changing archive values via the API

  Summary When changing archive values in a current open capsule/file via the API sometimes archive entries are lost/deleted entirely. Description When changing archive values in a current open capsule/file via the API sometimes archive entries are ...