Historian on open alpha files should not write the end-timestamp into the archive header.  

• Related Articles

• FAQ: Historian configuration general recommendations

  1. Recommendation on hardware: Storage Memory CPU - SSD (Solid-State Drive). - Disk space capacity as detailed in the attached Excel sheet outputs. - RAM required to load the archive data is about 4 times greater the size of the respective ARX files. ...

• FAQ: How to prevent corrupted files after power outage?

  Read the attached PDF files (English/German) for more information on how to set up your system to avoid corrupted files in case of an power outage.

• Archive configuration for best SQL evacuation performance

  The time required to evacuate data to a database increases linearly with the number of insert SQL statements. In earlier zenon versions, recorded values were evacuated to the target database sequentially using single-insert statements. From zenon 11 ...

• Historian: At reload an old value is written again / received values with old external timestamp not discarded

  Description In the Service Engine, data from already closed archives is written to the current, open archive capsule in the Historian. This problem can occur: By project reload. If the PLC sends variable values with an external timestamp from the ...

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