ifm
System Manual
ecomat
mobile
PDM360NG (CR1080, CR1081, CR9042) Target V01
2011-07-28
Limitations and programming notes
Limits of the device
95
6.1.2
Watchdog behaviour
1490
For (nearly) all programable
ecomat
mobile
devices the program runtime is monitored by a watchdog
of CoDeSys.
If the maximum watchdog time is exceeded:
- the device carries out a reset and starts again
BUT:
BasicController: CR040n:
- all processes are stopped (reset)
- all outputs are switched off
- the status LED lights red
- restart necessary via voltage off/on
BasicDisplay: CR0451:
- all processes are stopped (reset)
- all outputs are switched off
- the screen goes black
- the status LED lights red
- restart necessary via voltage off/on
SafetyController: CR7nnn
- all processes are stopped (reset)
- all outputs are switched off
- the screen goes black
- the status LED flashes red at 5 Hz
- restart necessary via voltage off/on
PDM360NG: CR108n, CR9042
- all processes are stopped (reset)
- all outputs are switched off
- the screen goes black
- the status LED flashes red at 5 Hz
- restart necessary via voltage off/on
Depending on the hardware the individual controllers have a different time behaviour:
Controller
Watchdog [ms]
BasicController: CR040n
100
BasicDisplay: CR0451 (application program)
BasicDisplay: CR0451 (visualisation)
100
1 200
CabinetController: CR030n
100...200
ClassicController: CR0020, CR0032, CR0505
100
ExtendedController: CR0200, CR0232
100
PCB controller: CS0015
100...200
SafetyController: CR7nnn
100
SmartController: CR25nn
100...200
PDM360: CR1050, CR1051, CR1060
no watchdog
PDM360compact: CR1052, CR1053, CR1055, CR1056
no watchdog
PDM360NG: CR108n, CR9042
monitored by Linux *)
PDM360smart: CR1070, CR1071
100...200
*) The Linux kernel and critical processes are separately monitored (different times).