5 Commissioning (hardware)
5.4 User memory concept
5.4.3 Operations and their effect on the user memory
The operations marked with arrows in the figures entitled "SIMOTION D4x5 memory model"
and "Configuration data and system variables in the volatile memory" and their effects on the user memory will be described below.
SIMOTION SCOUT Download
The Download menu command transfers the following data from the engineering system to the "volatile data" area:
● User data (units, configuration data, parameter settings, task configuration)
● Technology packages (TPs)
In addition, the IP and DP parameters are saved to the "non-volatile data" area. The retain variables are set to their initial values, but this depends on the settings in SIMOTION SCOUT. If the SIMOTION D4x5 is switched off following the download, the volatile data are lost.
Copy RAM to ROM
The Copy RAM to ROM menu command saves the following data via the engineering system to the CF card:
● Technology packages and user data (units, configuration data, parameter settings, task configuration) from the "volatile data" area
● Current values can also be copied to the "volatile data" area, depending on the settings in SIMOTION SCOUT. Select the option "Transfer current values to RAM for RAM to ROM"
under "Options" > "Settings" > "CPU download". The current values of the system are then first transferred to the RAM and then copied to the ROM from there with this setting.
Note
The "Copy RAM to ROM" menu command does not save the current values of the retain variables to the CF card. Use the system function "_savePersistentMemoryData" for this.
5.4 User memory concept
SIMOTION D4x5 power-up
During power-up of the SIMOTION D4x5, the SIMOTION Kernel is loaded from the CF card to the "volatile data" area.
When the SIMOTION D4x5 is switched off, the contents of the "volatile data" area are lost.
When the SIMOTION D4x5 is powered up again, the following data are loaded from the CF card:
● Technology packages and user data to the "volatile data" area
● IP and DP parameters the "non-volatile data" area
Backing up non-volatile data
With the _savePersistentMemoryData system function, the user program can back up the contents of the non-volatile data 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. On the system side, this system function ensures that a consistent overall image of the non-volatile data is always available the next time the unit is powered on, even if there is a power failure during backup. To this end, before a new backup file is created, any existing backup file is renamed as "PMEMORY.BAK". 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 contents of the non-volatile data.
If the new file is successfully created, the backup copy of the backup file is deleted.
NOTICE
If you do not save the data to the CF card, they will be lost if a spare part must be used (in the event of a module defect).
If an absolute encoder overflow occurs after "_savePersistentMemoryData", the actual position value will no longer be correct after the non-volatile data have been restored. In this case, homing (absolute encoder adjustment) must be repeated.
Network failure
In the event of a power failure, the data in the SRAM of the Control Unit is backed up by an internal SuperCap and a fan/battery module (where applicable).
The non-volatile data are available again the next time the unit is powered up. Thus, the control unit is immediately operational without data loss.
Note
After the unit is powered off and then on again, the SIMOTION part runs in coordination with SINAMICS Integrated, whereby SINAMICS Integrated ends the power-up at a later point.
The "Incoming station" alarm is triggered, and the PeripheralFaultTask is called.
5.4 User memory concept
Power-up and non-volatile data
The table below lists the cases that can arise during power-up in connection with the volatile data and explains how they are handled.
Table 5- 3 Cases: power-up with non-volatile data
Case Initial condition Result
1 The non-volatile data are valid. SIMOTION D4x5 powers up with the non-volatile data, meaning, for example, that the PROFIBUS address in the non-volatile data is valid.
2 The non-volatile data are invalid, and there is no backup file (PMEMORY.XML) and no backup copy of the backup file (PMEMORY.BAK).
SIMOTION D4x5 copies the default settings to the non-volatile data and powers up with these data. In this case, for example, the default PROFIBUS address is used.
3 The non-volatile data are invalid. A valid backup file
(PMEMORY.XML) exists. SIMOTION D4x5 copies the backup file contents to the non-volatile data and powers up with these data.
4 The non-volatile data are invalid, the backup file is invalid, and there is no backup copy of the backup file
(PMEMORY.BAK).
SIMOTION D4x5 copies the default settings to the non-volatile data and powers up with these data, in which case, for example, the default PROFIBUS address is used.
5 The non-volatile data are invalid; a backup file exists, but it is invalid; a backup copy of the backup file exists, and it is valid.
SIMOTION D4x5 copies the backup file contents to the non-volatile data and powers up with these data.
Non-volatile data diagnostics
The user can determine the status of the non-volatile data and the battery using the diagnostic buffer, system variables, and PeripheralFaultTask.
5.4 User memory concept
Evaluating via the diagnostic buffer
When they are issued, the following messages are entered once in the diagnostics buffer:
Table 5- 4 Messages of the diagnostics buffer
Entry Meaning Remedy
Level 1 battery voltage warning 1) Battery voltage below prewarning level Replace battery in the fan/battery module Level 2 battery voltage warning 1) The battery voltage is below the warning
level, backing up of non-volatile data/clock can no longer be guaranteed.
Replace battery in the fan/battery module Battery voltage for data backup in
permissible range
Non-volatile data memory voltage error The buffer voltage of the SuperCap or the battery was too low after Power On.
Possible data loss in the non-volatile data/clock.
Replace battery in the fan/battery module or charge SuperCap by energizing it for a longer period.
Non-volatile data loaded from a file (Persistent Data File Loading done)
Non-volatile data have been
successfully restored from the backup file on the CF card.
-
Non-volatile data loaded from the backup file (Persistent Data Backup File Loading done)
Non-volatile data have been
successfully restored from the backup copy of the backup file on the CF card.
-
Error while loading non-volatile data from a file
(Persistent Data File Loading Failure)
Backup file or backup copy of backup file could not be loaded.
Possible causes:
• Backup file or backup copy of backup file does not exist
• Data in backup file are invalid
Use the
"_savePersistentMemoryData"
system function to generate a valid backup file.
Device with battery module Fan/battery module is present. -
Device without battery module Fan/battery module is not present. Connect fan/battery module if necessary.
1) These warnings are only signaled when the fan/battery module has been inserted.
Refer to the SIMOTION SCOUT Configuration Manual for information about how to read out the contents of the diagnostic buffer.
5.4 User memory concept
Evaluating via PeripheralFaultTask
Battery status changes in RUN are reported to the user program by calling PeripheralFaultTask. Changes can be evaluated here using Taskstartinfo:
● TSI#InterruptId = _SC_PC_INTERNAL_FAILURE (= 205)
● TSI#details = Detailed information on battery status, see SIMOTION SCOUT Basic Functions Function Manual.
If there is no fan/battery module present or no battery inserted when the power is on, or in STOP mode, no PeripheralFaultTask will be triggered when powering up or in RUN (application case: D4x5 should generally be operated without a fan/battery module or battery).
References
Detailed information on setting up Taskstartinfo(#TSI) can be found in the SIMOTION Basic Functions Function Manual.
Evaluating via system variables
The system variables in the "device.persistentDataPowerMonitoring" structure indicate the status of the non-volatile data and the battery.
Table 5- 5 Status of non-volatile data and battery
system variables Designation Status Updating
powerFailure Buffer voltage (SuperCap or battery) too low, possible loss of data
NO (91)
YES (173) "YES" was set at too low a buffer voltage when powering up;
status needs to be reset to "NO" via the application.
persistentDataState Reading the persistent
data See Table 5.6, "Status of non-volatile data after powering up"
During power-up
warningBatteryVoltage
Level1 1) Battery voltage below
the prewarning level NO (91)
YES (173) During a status change, remains set if Level 2 is reached
warningBatteryVoltage
Level2 1) Battery voltage below
the warning level NO (91)
YES (173) During a status change
1) Both battery warning levels are set under the following conditions:
- Fan/battery module is present and battery inserted, battery voltage is below the warning level
- Fan/battery module is present, no battery is inserted (V4.1 SP2 and higher)