Reload of the historian module is performed concurrently with the historian recording thread

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

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

• Modifications in the SAP interface module are not recognized by the reload function

  Summary When the SAP Interface module is used in a zenon project, and the configuration in this module is changed in the zenon editor, creating runtime files will cause the file sap.cmp to be updated. When the function "reload project" is then ...

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

• Automatic function execution does not perform a reload.

  Summary If a reload function is executed automatically the reload is not performed until the runtime is restarted. DescriptionIf a reload function is executed automatically the reload is not performed until the runtime is restarted. Solution An issue ...