# Set\_target\_depth does not work

**URL:** <https://discuss.bluerobotics.com/t/set-target-depth-does-not-work/20125>\
**Category:** ArduSub\
**Tags:** ardusub, pymavlink\
**Created:** [April 18, 2025, 4:28am UTC](https://discuss.bluerobotics.com/t/set-target-depth-does-not-work/20125 "2025-04-18T04:28:09Z")\
**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:** [April 18, 2025, 12:17pm UTC](https://discuss.bluerobotics.com/t/set-target-depth-does-not-work/20125/2 "2025-04-18T12:17:13Z")

</div>

Hi @chang-M,

> [@chang-M](#):
>
> is it possible that there are other reasons?

> [@Moving a BlueROV with pymavlink](https://discuss.bluerobotics.com/t/moving-a-bluerov-with-pymavlink/19981/9):
>
> The [current ArduSub implementation](https://github.com/ArduPilot/ardupilot/blob/Sub-4.5/ArduSub/GCS_Mavlink.cpp#L660-L738) requires setting all three (x,y,z) [position] targets together, because [if you ignore one it will ignore all of them](https://github.com/ArduPilot/ardupilot/blob/Sub-4.5/ArduSub/defines.h#L152).

---

_[View the full topic](https://discuss.bluerobotics.com/t/set-target-depth-does-not-work/20125)._