SIMOTION D4x5‑2 power-up
During power-up of the SIMOTION D4x5‑2, the SIMOTION Kernel is loaded from the CF card
to the "volatile SIMOTION data" area.
When the SIMOTION D4x5‑2 is switched off, the contents of the "volatile SIMOTION data"
area are lost. When the unit is powered up again, the following data is loaded from the CF card:
● Technology packages and user data to the "volatile SIMOTION data" area
● IP and DP parameters to the "non-volatile SIMOTION data" area
Backing up non-volatile SIMOTION data
You have the following options for backing up non-volatile SIMOTION data on the CF card:
● In the user program:
With the _savePersistentMemoryData system function, the user program can back up the
non-volatile SIMOTION data content to the CF card. This ensures that the retain variables
and the absolute encoder position are backed up in the event that a spare part is used. The
contents are saved to the "PMEMORY.XML" backup file in the "USER\SIMOTION"
directory.
● Via switch/button (service selector switch or DIAG button of the SIMOTION D4x5‑2) or
SIMOTION IT web server. See Section Backing up diagnostic data and non-volatile
SIMOTION data (Page 396). The contents are saved to the "PMEMORY.XML" backup file
in the "USER\SIMOTION\HMI\SYSLOG\DIAG" directory.
On the system side, this system function ensures that a consistent overall image of the non-
volatile SIMOTION data is always available the next time the unit is switched on, even if there
is a power failure during backup. An already existing backup file is renamed to
"PMEMORY.BAK" before a new backup file is generated. If the save operation to the new
backup file fails (e.g. because the capacity of the CF card is insufficient), this backup copy of
the backup file is used the next time an attempt is made to restore the non-volatile SIMOTION
data content.
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 values 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
Homing required again 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 is restored.
In this case, homing (absolute encoder adjustment) must be repeated.
Commissioning (hardware)
5.3 User memory concept
SIMOTION D4x5-2
108
Commissioning and Hardware Installation Manual, 03/2018, A5E33441636B