# Odrive Pro Configurable Watchdog

**URL:** <https://discourse.odriverobotics.com/t/odrive-pro-configurable-watchdog/14464>\
**Category:** ODrive Pro Support\
**Created:** [August 20, 2026, 11:35pm UTC](https://discourse.odriverobotics.com/t/odrive-pro-configurable-watchdog/14464 "2026-08-20T23:35:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MPeroutek](https://discourse.odriverobotics.com/user_avatar/discourse.odriverobotics.com/mperoutek/32/8118_2.png) [@MPeroutek](https://discourse.odriverobotics.com/u/MPeroutek)\
**Post date:** [August 20, 2026, 11:35pm UTC](https://discourse.odriverobotics.com/t/odrive-pro-configurable-watchdog/14464/1 "2026-08-20T23:35:54Z")

</div>

Hi,

I’m using a few O-Drive Pro’s in a system where, in the case of a disconnection, “Fail to motor pos=0.0, IDLE” is a much safer state for the motors than “Fail to Last Position, IDLE”.

From the documentation and my research, it’s clear that the built-in Odrive Watchdog functionality only supports the latter (I.e. going to IDLE with no position command).

Is there a world where the ODrive team implements a new parameter like “watchdog\_pos” that can optionally be used to attempt a new “input\_pos” command before going to IDLE?

(P.S. Love the product and it’s doing some really cool things for us. Thanks!)

---

<div class="post-metadata">

**Author:** ![solomondg](https://discourse.odriverobotics.com/letter_avatar_proxy/v4/letter/s/bcef8e/32.png) [@solomondg](https://discourse.odriverobotics.com/u/solomondg)\
**Post date:** [August 21, 2026, 6:10pm UTC](https://discourse.odriverobotics.com/t/odrive-pro-configurable-watchdog/14464/2 "2026-08-21T18:10:36Z")

</div>

Hi!

Glad to hear the ODrive is working out for you 🙂

Yes, it only supports going to idle. But some sort of safe-stop-on-nonfatal-error is definitely something we have in our roadmap.

In the near term though, we’re adding support for user code, so you can write scripts and routines to run on the ODrive in parallel with the main ODrive firmware stack. That should let you accomplish this functionality – have some code that checks for watchdog disarm, then re-enables the axis and moves to the desired safe input\_pos.