# Thrusters firing incorrectly et al

**URL:** <https://discuss.bluerobotics.com/t/thrusters-firing-incorrectly-et-al/12736>\
**Category:** Blue Robotics Software\
**Tags:** ardusub, thruster\
**Created:** [August 13, 2022, 1:33pm UTC](https://discuss.bluerobotics.com/t/thrusters-firing-incorrectly-et-al/12736 "2022-08-13T13:33:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![TheoBenn](https://avatars.discourse-cdn.com/v4/letter/t/9e8a1a/32.png) [@TheoBenn](https://discuss.bluerobotics.com/u/TheoBenn)\
**Post date:** [August 13, 2022, 1:33pm UTC](https://discuss.bluerobotics.com/t/thrusters-firing-incorrectly-et-al/12736/1 "2022-08-13T13:33:38Z")

</div>

Hi folks.

Non-robotic person here (no shade on the robots though). We followed the instructions to build the BlueROV2 (v3) to the letter. All thrusters were labelled and triple-checked for correct routing.

A couple of issues

1. Logitech F310 left analogue stick does not respond in the calibration. The switch is to X, the setting is on 3 for RC. Right analogue stick and D-pad are working but not associated with any number. This was the “default” setting and isn’t that which was supplied on the website.

2. When moving forwards, thruster 5 fires and the unit spins to starboard. When descending, thruster 6 fires, thruster 5 at far less power which results in a pitch to port.

3. Batteries have been charged to 100% but both immediately show as around 50% charged when connected to QGC.

We are going to try and calibrate all the sensors again. We will check the cable routing and connections again. Is there anything else this could be? Also if you know how to completely remap this nightmare controller I’d love a step by step.

Thanks all.  
Theo

---

<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:** [August 16, 2022, 1:40pm UTC](https://discuss.bluerobotics.com/t/thrusters-firing-incorrectly-et-al/12736/2 "2022-08-16T13:40:10Z")

</div>

Hi @TheoBenn,

> [@TheoBenn](#):
>
> 1. Logitech F310 left analogue stick does not respond in the calibration. The switch is to X, the setting is on 3 for RC. Right analogue stick and D-pad are working but not associated with any number. This was the “default” setting and isn’t that which was supplied on the website.

Are you able to confirm whether that stick responds as expected in another application, e.g. the [Windows Game Controllers test page](https://support.logi.com/hc/en-us/articles/360023179034-Access-the-Windows-Game-Controllers-test-page)? If that doesn’t work then your controller may be damaged / malfunctioning.

> [@TheoBenn](#):
>
> 1. When moving forwards, thruster 5 fires and the unit spins to starboard. When descending, thruster 6 fires, thruster 5 at far less power which results in a pitch to port.

This seems odd. Perhaps double-check that the motors are configured correctly for your frame, via QGroundControl’s [Motors Setup page](https://www.ardusub.com/reference/ardusub/motors-setup-page.html)?

> [@TheoBenn](#):
>
> 1. Batteries have been charged to 100% but both immediately show as around 50% charged when connected to QGC.

How is your [Power Setup](https://www.ardusub.com/reference/ardusub/power-setup-page.html) configured? Perhaps there’s an error with the setup there.

---

<div class="post-metadata">

**Author:** ![TheoBenn](https://avatars.discourse-cdn.com/v4/letter/t/9e8a1a/32.png) [@TheoBenn](https://discuss.bluerobotics.com/u/TheoBenn)\
**Post date:** [August 24, 2022, 3:56pm UTC](https://discuss.bluerobotics.com/t/thrusters-firing-incorrectly-et-al/12736/3 "2022-08-24T15:56:55Z")

</div>

Hey Eliot,

> [@EliotBR](#):
>
> Are you able to confirm whether that stick responds as expected in another application, e.g. the [Windows Game Controllers test page](https://support.logi.com/hc/en-us/articles/360023179034-Access-the-Windows-Game-Controllers-test-page)? If that doesn’t work then your controller may be damaged / malfunctioning.

We rolled back the QGC software and it solved this issue

With regards to everything else, all seems fine, and we have narrowed it down to a shorting ESC… Potentially.

Thanks for the help 🙂