User Manual

Programming and commissioning
Programming tool: SAPRO
5
A6V1127616_en--_a 23 | 38
Lifecycle of flash for ApplicationSave
After ApplicationSave is triggered, all object parameters are written into the flash.
Consider the flash’s lifecycle
*)
when triggering ApplicationSave.
*）An entire flash chip typically has 100,000 erase/program cycles.
As a consequence the times for ApplicationSave and the chip’s lifecycle must be
balanced. The graph below shows a typical lifecycle with different ApplicationSave
scenarios.
Note: A timer or object change of value can trigger the ApplicationSave. The
ApplicationSave strategies are defined as follows:
ApplicationSave strategies
● Strategy 1: ApplicationSave once after application configuration procedure is
completed or after downloading a parameter file to the controller. Use Scope
tools or application in Access DB blocks to directly trigger the ApplicationSave
member of object aoDiagnostic.
● Strategy 2: With HMI (example DM or TM), the member EXT:CurPWLevel in
the object HMI is used to detect when someone is logging in and logging out of
the HMI. The setpoint change is not saved if logged in as a normal user. Only
service or factory level log in / log out can trigger ApplcationSave.