Hi, just put together our Blueboat that has arrived. Got all hardware together and talking with software on a laptop. When testing the motors following Blueboat instruction in QGroundControl I had no response/movement from them?
Has anyone got any advice on why this might not be working?
Short of getting the Blueboat on the water to try her maiden voyage I cannot work out why there is no response.
Thanks in advance.
Hi @JoeChapman -
Welcome to the forums!
Do the motors beep when you connect the battery, and again 1-2 minutes later after the Raspberry Pi finishes starting up?
If no beeps at all, the ESCs that power the motors are not connected to power, or the ESCs have not been connected to the motor cable (yellow 3 pin connector)….
If the initial beep happens, but no beep after startup, than the black/white signal cables from Navigator to ESC have not been connected, or were connected backwards- this happens at the back of each hatch, alongside the other motor power and battery power connections.
Hi @tony-white
Thanks for the quick reply!
Yes so certain I can hear both beeps on startup. But still no response when trying motor test in QGroundControl.
I get a message displaying - EKF Variance - is this of help?
I was thinking of trying a wet test to see if the Blueboat will sail.
Hi @JoeChapman -
Getting the motors wet isn’t going to make them start spinning - I never launch until the motors spin, in manual mode, with the use of the gamepad and ground control station software!
You hear beeps on connection of the battery, do you hear additional beeps a minute or two later?
Have you reached BlueOS in your web browser and configured the vehicle as a BlueBoat? You could try the motor test there, under Vehicle Setup / PWM outputs (with QGC closed.)
The EKF Variance message means your compass or accelerometer calibration has an issue, you may want to perform it again away from potential sources of interference (large metal objects.)