Siemens SIMOTION D4 5-2 Series Commissioning And Hardware Installation Manual page 100

Commissioning (hardware)
4.3 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 = 16#00000040
If no battery is used during the transition of the operating state to RUN, no
PeripheralFaultTask will be triggered (application case: D4x5-2 should generally be operated
without a battery).
References
Detailed information on setting up TaskStartInfo(#TSI) can be found in the
SCOUT Basic Functions
Evaluating via system variables
The system variables in the device.persistentDataPowerMonitoring structure indicate the
status of the non-volatile SIMOTION data and the battery.
Table 4- 5
System variable
powerFailure
rtcFailure
(as of V4.3)
retainDataFailure
(as of V4.3)
persistentDataState
100
Function Manual.
Status of the non-volatile SIMOTION data and battery
Designation
Buffer voltage
(SuperCap or battery)
too low, possible data
loss of the real-time
clock
Indicates that the
clock contents (RTC)
are invalid (clock must
be set again)
Indicates a checksum
error of the non-
volatile SIMOTION
data; can be an
indication of defective
HW
Reading the persistent
data
State Updating
NO (91) "YES" was set at too low a
YES (173) buffer voltage when
powering up; status needs
to be reset to "NO" via the
application; the status
remains even after power
off/on.
NO (91) Is updated once during
YES (173) power-up; status must be
reset to "NO" via the
application; the status is
retained even after power
off/on.
NO (91) Is updated once during
YES (173) power-up; status must be
reset to "NO" via the
application; the status is
retained even after power
off/on.
See the table below, During power-up
"State of non-volatile
data following
power-up".
Commissioning and Hardware Installation Manual, 02/2012
SIMOTION
SIMOTION D4x5-2