# Python script, manual mode: thrusters return to neutral after a few seconds

**URL:** <https://discuss.bluerobotics.com/t/python-script-manual-mode-thrusters-return-to-neutral-after-a-few-seconds/11162>\
**Category:** Blue Robotics Software\
**Tags:** ardusub, simulate, pymavlink, sitl\
**Created:** [December 9, 2021, 5:30pm UTC](https://discuss.bluerobotics.com/t/python-script-manual-mode-thrusters-return-to-neutral-after-a-few-seconds/11162 "2021-12-09T17:30:54Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\
**Post date:** [December 10, 2021, 12:28am UTC](https://discuss.bluerobotics.com/t/python-script-manual-mode-thrusters-return-to-neutral-after-a-few-seconds/11162/2 "2021-12-10T00:28:01Z")

</div>

Hi @TMJ,

> [@TMJ](#):
>
> the motors return to zero thrust after a few seconds unless I repeatedly send the command in a while loop.

This is expected behaviour, ArduSub includes a [Pilot Input failsafe](https://www.ardusub.com/reference/ardusub/safety-setup-page.html#pilot-input) which by default disarms the vehicle if it hasn’t received a new control input within the last 3 seconds. It’s possible to disable the failsafe by setting [`FS_PILOT_INPUT`](https://www.ardusub.com/developers/full-parameter-list.html#fspilotinput-pilot-input-failsafe-action) to 0, but the recommended approach is to send regular control inputs just as you should be sending regular heartbeat messages. There’s an example [here](https://discuss.bluerobotics.com/t/sending-and-recieving-heartbeats-to-bluerov-from-surface-computer-using-pymavlink/10940/6#your-actual-issue-1) of periodic events, which may be useful 🙂

---

_[View the full topic](https://discuss.bluerobotics.com/t/python-script-manual-mode-thrusters-return-to-neutral-after-a-few-seconds/11162)._