Differences

This shows you the differences between two versions of the page.

--- tools:wdt [2024/06/10 15:01] – created ursgraf
+++ tools:wdt [2024/06/10 17:24] (current) – [Using an Watchdog through the HAL] ursgraf
@@ Line 1: / Line 1: @@
 ====== Using a Watchdog ======
+A watchdog device can greatly improve the overall safety of a system. We recommend to periodically reset such a watchdog from within the main time domain of the control system, e.g. the time domain which runs your actuators. Set the watchdog time to a reasonable multiple of the period of the time domain. Now, if your system gets stuck and your time domain does not run within its desired limit, the watchdog will timeout and switch off your drives.
+===== Using an Watchdog =====
+An external watchdog can be implemented with an external timer or with a simple retriggerable one shot timer. Implement a block in your control system which uses a digital peripheral output. Make sure to toggle the output state every time the block runs. This toggling output periodically reloads the timer. If your time domain blocks for a certain period the timer will run out. \\
+Define a digital peripheral input which is connected to your watchdog timer output. Add this peripheral input to the critical inputs of your safety system, see [[eeros_architecture:safety_system:properties#Critical_Inputs_and_Outputs|Critical Inputs and Outputs]]. Depending on your safety level check the state of the watchdog timer, e.g.
+<code cpp>
+slMoving.setInputActions({check(wdt, true, abort)});
+</code>
+===== Using an Watchdog through the HAL =====
+Some HAL libraries implement a watchdog device, e.g. [[getting_started:install_wrapper#flink|flink]]. When going through the HAL, you can use the [[eeros_architecture:control_system:available_blocks:watchdog|]] block. Such a block runs within the time domain of your control system and periodically resets the timer. The timer must be configured within the configuration file (see [[eeros_architecture:hal:configuration_file|]]. This could be done for example as follows
+<code>
+"subdevice5": {
+  "type": "Watchdog",
+  "channel0": {
+    "signalId": "Wdt",
+    "additionalArguments": "0.05"
+   }
+}
+</code>
+Here, the watchdog timeout is set to 50ms. You have to start the timer, which is called ''arming'' as soon as your time domain starts running.
+<code>
+wdt.arm();
+</code>
+The watchdog block in your control system defines a peripheral input. Check for the state of this input with a critical input in your safety system, see [[getting_started:tutorials:hal2|]].