Hi @cmarq !
It’s interesting that it used to work, but doesn’t currently. Can you share what version of BlueOS you’re using, and if you’ve upgraded? Does the list of available wifi networks appear correctly, but the connection fails? Maybe you can setup something like this travel hotspot connected to your university wifi if your phone hotspot is the root of the issue.
It’s also worth noting that those instructions you followed are intended for CompanionOS, which is no longer being developed. Everything covered there from a WiFi router setup is correct, but the commands at the start don’t do anything in BlueOS. Are you using companion? Upgrading is easy, and supported for older vehicles that may be using a Pixhawk autopilot- you’ll just need to extract your SD card, flash it, and re-install / setup the system.
@scriffij -
So sorry we’ve not been able to replicate your issues. In the over 200 BlueBoats delivered to customers, we’ve only had 2 similar instances where a user had issues with GPS lock, but the GPS would work fine with other forms of autopilot electronics. With both of these instances, replacing their entire electronics assembly eliminated the issue, so that was the course we chose to follow with you.
I’ve personally used multiple BlueBoat on dozens of deployments, most recently conducting multibeam and sidescan survey of large sections of the Hawaii coastline. The system navigated with LTE and Starlink on board, using the Raspberry Pi 4 WiFi to connect to the on-board Starlink, and using 4G via USB modem. I’m conducting additional WiFi range tests with the default Mikrotik radio and our upcoming directional antenna kit next week. Everything has been conducted with completely stock power systems on the vehicle.
All that is to say, if there is an RF issue, you would think running 3 different forms of high power radio simultaneously, sometimes larger, more powerful motors, and the same Navigator/Pi hardware as the BlueROV2 (of which thousands have shipped with this electronics configuration) we would know about it!
I apologize you’ve spent large sums investigating this, but as you’ve yet to share any concrete findings (or return the hardware you received a replacement for) we’ve been unable to investigate… Please help us help you, rather than raise your issues on unrelated user topics!