Historian values created via the programming interface with a timestamp of 00:00:00 for the first day of the month can no longer be deleted

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

• In the web client the archives in the historian of sub projecs cannot be accessed via the programming interface.

  Summary When using the programming interface in the webclient, the archives in the historian from sub projects cannot be accessed DescriptionWhen using the programming interface in the webclient, the archives in the historian from sub projects cannot ...

• FAQ: What is the time zone and time format used in zenon Software Platform products and what needs to be considered?

  When you ask someone what the time is, they'll usually be able to tell you. But when you ask them what date and time sunrise was yesterday in a different country on a different continent, in a different hemisphere it gets less easy. Terms like GMT ...

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

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

  Summary Via Programming Interface or Archedit should not write the end-timestamp into the archive header of open XX.ARX files as sometimes the end-timestamp in the header is getting invalid when creating archive entries. DescriptionVia Programming ...