Hi @dahlia -
You’ll want to update from that version to the latest stable - 1.4.2. You’ll also want to apply the bootstrap update after doing so - in pirate mode, the yellow button will appear after the update.
In order to update, you will need to connect the Pi running BlueOS to WiFi - you can do this from the WiFi icon in the upper right of the BlueOS web interface. Some WiFi networks that require both username and password are not possible to connect to - a phone hotspot is often a good alternative.
Hi Dahlia -
Were you in pirate mode after the BlueOS update? The button should be present in the BlueOS Version menu, next to the 1.4.2. You can delete the older version.
As for the ArduPilot firmware, you want to use the latest stable for ArduRover (not ArduSub or any other flavor) - this is 4.6.1 currently.
The firmware has been updated to 4.6.1. Yes, we are working in Pirate Mode, the yellow button for updating the bootstrap did not appear. The GPS fix is still unsuccessful, any other suggestions for troubleshooting? Maybe a communication issue?
Hi @dahlia -
Now that you’re on the latest everything, do you see any indication of GPS communications in BlueOS, in the upper right corner? What elevation above sea level are you operating the BlueBoat at? Have you opened the starboard hatch and confirmed the GPS is plugged into Serial 5? You should see some lights flashing from the under-deck plate it is mounted too - if not it may not be getting power?
You may want to try loading the BlueBoat default vehicle parmeters from the Vehicle Setup menu in BlueOS, to make sure things are configured to the default state. If you back up your autopilot parameters first you can restor the motion sensor calibrations and not have to re-do all that work…
Hi @tony-white there is no indication of GPS, the BlueOS dashboard does not display the avatar seen on other dashboards. We are operating at sea level. The GPS is plugged into Serial 5 and is powered. I will attempt to backup and work from default!
Hi @dahlia -
Please verify the other end of the cable from Serial5 is connected to the GPS, and that you see flashing lights coming from it! If these aren’t present, please reach out to support
to discuss a replacement (report a problem with a product), and include your order #.
Hi @tony-white Serial5 works and we are picking up a GPS signal now.
The boat has been calibrated again. Qgroundcontrol allows for the vehicle to be armed however when flying a mission, on AUTO, the boat does not follow the preplanned mission. It goes in the opposite direction. It reads GPS 1 error, is there any way to troubleshoot this?
When on manual mode, the boat follows the commands from the wireless controller.
EDIT: For more context, when on GPS lock the red marker on QGC is in the opposite direction.
Now that the port is in Serial 5, under QGC sensor settings, it reads Compass 1 (secondary, external) Compass 2 (secondary, internal) Compass 3 (secondary, external) . We have done over 10 compass calibrations (in an open field) Yet it would not let us arm bc of “compasses inconsistent”. Until we turned off the 2nd compass, but now it is 180 degrees from where the front of the boat is actually facing.
Hi @dahlia -
It sounds like either your calibrations wasn’t very good, or your parameters for autopilot orientation have been changed! Can you confirm your AHRS_ORIENTATION parameter is set to Roll180 in your Autopilot Parameters menu? If it isn’t, best to load the default BlueBoat parameters from the Vehicle Setup menu in BlueOS…