# Thruster Movement Software Issue **URL:** \ **Category:** MATE ROV\ **Created:** [March 29, 2026, 7:06pm UTC](https://discuss.bluerobotics.com/t/thruster-movement-software-issue/22715 "2026-03-29T19:06:20Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![kingcoolance](https://avatars.discourse-cdn.com/v4/letter/k/958977/32.png) [@kingcoolance](https://discuss.bluerobotics.com/u/kingcoolance)\ **Post date:** [March 29, 2026, 7:06pm UTC](https://discuss.bluerobotics.com/t/thruster-movement-software-issue/22715/1 "2026-03-29T19:06:20Z")
I am currently working on an underwater ROV for the MateROV competition, using a 6-thruster vectored frame (4 horizontal at 45 degrees, 2 vertical) running ArduSub on a Navigator Flight Controller, interfaced through BlueOS and Cockpit. When testing with an Xbox One S Wireless Controller, the ROV arms and disarms correctly, all button functions work as expected, and the axis inputs are being read properly in both Cockpit and QGroundControl. MAVLink MANUAL\_CONTROL x/y/z/r values change correctly when the sticks are moved, confirming the controller input is reaching the flight controller. Individual motor tests in BlueOS also work perfectly. All 6 motors respond correctly in their expected physical positions, with one vertical motor reversed as needed. FRAME\_CONFIG is set to 0 in ArduSub parameters. However, when actually piloting the ROV with the controller sticks, the movement has no discernible pattern relative to stick input. The problem persists across both Cockpit and QGroundControl, ruling out a software-specific issue. Any guidance on what could cause correct motor test behavior and correct MAVLink input readings, but completely wrong and unpredictable thruster response during actual piloting would be greatly appreciated. We are on a tight timeline with regionals in 3 weeks, so any help is very much appreciated. ---
**Author:** ![tony-white](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/tony-white/32/18385_2.png) [@tony-white](https://discuss.bluerobotics.com/u/tony-white)\ **Post date:** [March 29, 2026, 7:17pm UTC](https://discuss.bluerobotics.com/t/thruster-movement-software-issue/22715/2 "2026-03-29T19:17:29Z")
Hi @kingcoolance - It sounds like you have everything setup correctly. Does the vehicle “go crazy” in stabilize or depth-hold modes? If so, the compass may not be calibrated correctly, or the [AHRS\_ORIENTATION](https://ardupilot.org/sub/docs/parameters-Sub-stable-V4.1.2.html#ahrs-orientation-board-orientation) has not been set to match how the autopilot is mounted. Can you give more detail on what you mean by: > [@kingcoolance](#): > > but completely wrong and unpredictable thruster response during actual piloting In air, if you are in manual mode and push fwd on the left stick (or however you have it mapped) do all 4 horizontal thrusters push air to towards the back of the vehicle? Do you have an equal number of CW and CCW props intalled? ---
**Author:** ![kingcoolance](https://avatars.discourse-cdn.com/v4/letter/k/958977/32.png) [@kingcoolance](https://discuss.bluerobotics.com/u/kingcoolance)\ **Post date:** [March 30, 2026, 3:05am UTC](https://discuss.bluerobotics.com/t/thruster-movement-software-issue/22715/3 "2026-03-30T03:05:26Z")
When I am piloting with the xbox controller, in air or in water, there is no pattern that I can see to which movement of the joystick moves which. Like, if I push fwd, one of the fwd two turn on fully, the other one stays stagnant, and the back ones go slower than the fwd ones. We do have an equal number CW and CCW props installed, just like the tutorial on the Bluerobotics website ---
**Author:** ![tony-white](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/tony-white/32/18385_2.png) [@tony-white](https://discuss.bluerobotics.com/u/tony-white)\ **Post date:** [March 30, 2026, 4:39am UTC](https://discuss.bluerobotics.com/t/thruster-movement-software-issue/22715/4 "2026-03-30T04:39:04Z")
Hi @kingcoolance - We’re still missing some critical troubleshooting information to assist you. What flight mode is the vehicle in when you test? Are the props all possible to turn easily by hand? What is your AHRS\_Orientation set to vs. how is the autopilot mounted in the vehicle? The more context you can share, including pictures and your[autopilot parameters](https://blueos.cloud/docs/latest/usage/advanced/#autopilot-parameters) file, the better chance we have to assist you! The behavior you describe is normal for the 6 thruster standard BROV2 frame - the front propellers work harder than the front to minimize the pitching affect when starting from a stop, I believe… however if all 4 horizontal thrusters don’t respond, something is likely wrong with the one that isn’t!