# Vectored thruster orientation

**URL:** <https://discuss.bluerobotics.com/t/vectored-thruster-orientation/7060>\
**Category:** Thrusters and Motors\
**Tags:** ardusub, vehicle-design\
**Created:** [March 18, 2020, 4:25am UTC](https://discuss.bluerobotics.com/t/vectored-thruster-orientation/7060 "2020-03-18T04:25:46Z")\
**Posts on this page:** 1\
**Showing post:** 30

<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:** [March 22, 2022, 1:31am UTC](https://discuss.bluerobotics.com/t/vectored-thruster-orientation/7060/30 "2022-03-22T01:31:13Z")

</div>

> [@etienne](#):
>
> - Depth sensor is not detected. Tried 2 different pixhawk and depth sensors.

Did you build off `ArduSub-stable`, or `ArduSub-beta` / `master`?

> [@WaterLinked DVL A50 integration not working](https://discuss.bluerobotics.com/t/waterlinked-dvl-a50-integration-not-working/11501/5):
>
> ArduSub beta/devel recently had a couple of updates that apparently messed up a default parameter for the depth sensor. The issue should be fixed if you
> 
> > [@Ongoing DVL-A50 issues](https://discuss.bluerobotics.com/t/ongoing-dvl-a50-issues/11419/10):
> >
> > try setting BARO\_PROBE\_EXT to 768 and then reboot.

> [@etienne](#):
>
> - When I load my custom frame, I get a message that the light parameters are not found and I can’t set the lights to anything else other than disabled.

Hmm, that’s odd, although if you’re using a `beta` or `master` branch firmware build it’s possible the parameters have changed, which may not be reflected in the version of QGC you’re using.

---

_[View the full topic](https://discuss.bluerobotics.com/t/vectored-thruster-orientation/7060)._