Siemens SIMOTION D410 Commissioning Manual page 47

data content. If the new file is successfully created, the backup copy of the backup file is
deleted.
NOTICE
Loss of data due to failure to make backup copies
Non-backed-up non-volatile SIMOTION data can be lost on hardware replacement (module
defect), for example, if the current value of the retain variables have not been backed up and
replaced by their initial values again.
Back up the non-volatile SIMOTION data on the CF card.
NOTICE
Repeat referencing necessary after absolute encoder overflow
If an absolute encoder overflow occurs after _savePersistentMemoryData, the actual position
value is no longer correct after the non-volatile SIMOTION data are restored.
In this case, homing (absolute encoder adjustment) must be repeated.
With the SCOUT functions "Save variables" and "Restore variables," you also have the option
of backing up to your PC and restoring data that were changed during operation and only
stored in the runtime system.
Reloading non‑volatile SIMOTION data
SIMOTION data backed up on a CF card with _savePersistentMemoryData are restored in the
following cases:
1. after replacing a module, see Section Replacing modules (spare part scenario)
2. after an memory reset, see Section Resetting the memory of SIMOTION D410 (Page 152).
3. by switch setting, see Section Deleting/restoring non-volatile SIMOTION data (Page 209).
To restore the data backed up via the service selector switch or web server, the existing backup
files PMEMORY.XML and PMEMORY.BAK in the "USER\SIMOTION" directory on the CF
card must be deleted. See also Section Deleting/restoring non-volatile SIMOTION data
(Page 209).
SIMOTION D410
Commissioning Manual, 04/2014
(Page 167).
Commissioning (hardware)
3.5 User memory concept
47