I’m trying to control the BlueROV using a standard logitech controller (the one recommended in the documentation) but the controls seem to map very oddly. Checking the UI, the joysticks map correctly to forward/lateral/thrust/yaw axes.
In manual mode:
When I press forward on the forward joystick, the robot yaws counterclockwise/left, and when I press down on the forward joystick, the robot yaws clockwise/right. Lateral left goes clockwise/right, and lateral right goes counterclockwise/left. Thrust forward rolls to the right, and thrust down rolls left. Yaw left goes left/counterclockwise, and yaw right goes right/clockwise.
Could it be that the trims for everything need to be adjusted? All the gains/maximum in the tuning tab of QGroundControl are set to 0 right now. I searched for guidance on trimming to resolve these issues but unfortunately could not find anything. I double checked to make sure the motors were hooked up correctly, and everything (motor positions and polarity) looks correct when I test each motor separately. I’m not sure if there is something I need to configure that I have missed? I recalibrated the compass and accelerometer as well. Do you have any ideas on how to get steering/controls to work as expected?
Thanks for the detailed breakdown of what you’ve done so far, and what you’ve checked/tested
Can you try the Automatic Motor Direction Detection process? This sounds like some of your thrusters may be reversed, which is what that process is made to detect and account for
That’s odd, although not necessarily relevant to your main issue because the tuning parameters are only used in stabilisation modes, not manual mode.
Which version of ArduSub are you running? It should tell you in the Frame section (bottom right) of the QGC Summary page. If you’re not on 4.0.3 then I’d recommend updating to the latest Stable version, which you can do from the System page of the Companion Web Interface (http://192.168.2.2:2770). If there’s an update available for your Companion computer you’ll need to do that first (there was a recent issue that stopped Pixhawk firmware downloads on Companion, which the latest Companion update fixes).
