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.
Description
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.
Solution
An issue was addressed in the programming interface. Now, archive entries are written and the correct meta data is added to archive files.
Information
Writing archive entries with future time stamps should only be used in archives which are inactive and not recording live data to avoid inconsistent data.
Issue Number: 34059
Fixed on Date: 7.4.2015
Versions: 7.20 0 BUILD 19742
Related Articles
Checklist: Data Missing in Service Engine
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] ...
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 ...
FAQ: How, where, why and when does zenon Service Engine save data?
zenon Disk Space Handling: The zenon Service Engine, by default, stores process data on the hard disk. This is true for a standalone zenon project, as well as the zenon Service Engine server(s) in the zenon network topology. This data consists of ...
FAQ: When I activate the option "write synchronously" for the Recipegroup manager recipe, and I write the recipe, the recipe does not seem to be written properly and also the Service Engine does not close properly. Why is that?
When the option "write synchronously" is active at a recipe, when writing a recipe (sending values to the PLC) for each recipe variable a writing confirmation is requested to the driver. On a successfull write, the driver sends a writing confirmation ...
FAQ: It seems that sometimes not all variables are correctly written to the PLC by the RGM module, although the system driver variable states that the recipe was written successfully and the option "write synchronously" is active. How can this be?
When reading a RGM recipe immediately after writing a RGM recipe, with a driver that has the option "keep update list in memory" active, and recipe variables that have been read previously, it can happen that a read cycle is currently in progress, ...