Commissioning (hardware)
4.3 User memory concept
SIMOTION D4x5-2
100 Commissioning and Hardware Installation Manual, 02/2012
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
SIMOTION
SCOUT Basic Functions
Function Manual.
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 Status of the non-volatile SIMOTION data and battery
System variable Designation State Updating
powerFailure Buffer voltage
(SuperCap or battery)
too low, possible data
loss of the real-time
clock
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; the status
remains even after power
off/on.
rtcFailure
(as of V4.3)
Indicates that the
clock contents (RTC)
are invalid (clock must
be set again)
NO (91)
YES (173)
Is updated once during
power-up; status must be
reset to "NO" via the
application; the status is
retained even after power
off/on.
retainDataFailure
(as of V4.3)
Indicates a checksum
error of the non-
volatile SIMOTION
data; can be an
indication of defective
HW
NO (91)
YES (173)
Is updated once during
power-up; status must be
reset to "NO" via the
application; the status is
retained even after power
off/on.
persistentDataState Reading the persistent
data
See the table below,
"State of non-volatile
data following
power-up".
During power-up
To Next Page
Loading...
