BlueOS not connecting to Internet through phone hotspot

I am trying to connect my blueROV2 to the internet to be able to update software.

My current setup is consistent with this guide

https://www.ardusub.com/developers/wireless-topside.html

Ever since setting this up, I cannot figure out how to give my vehicle access to the internet. I used to be able to connect to my phone hotspot through blueOS and access the internet, but this doesn’t work anymore

I can connect directly to WiFi at my home, but my main area to work in this robot has university regulated WiFi so I cannot connect directly to it

Any help on this issue would be greatly appreciated

1 Like

sometimes blueos does not work when you connect it to different wifi. You should try perhps with zero tier extension

The Blue Boat electronics is killing the Rpi 4 wifi. I have been diagnosing the Blue Boat now since November 2023. The electronics implimentation creates the most noisy (EMI and RF) interference I have ever seen in a drone build. I will be posting my findings overy the next few days. We gutted the entire elctronics bay and built our own over two days that works perfectly to 2km on wifi and unlimited on 4G (where 4G exists) with ZeroTier - no BlueOS though.

People at Blue Robotics are greate but tired of getting sorry you are having GPS problems when I constantly say the GPS works perfectly on 3 other Ardupilot platforms with the same settings. I dont have a GPS problem, I have a Blue Robotics electronics implimentationm problem.

I’ll post in General Descussion for Blue Boat my findings (includiding those from the Professor in electronics I had to pay to test my theroies). Lost a lot of money on this project!!!

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!

So, I am not sure why this is required, but I was able to fix my issue by setting additional dns nameservers of 8.8.8.8 and 8.8.4.4. Upon doing that, I can immediately access the internet now

Intersting @cmarq -
Where/ how did you configure that dns server? Within BlueOS?

Yes, in BlueOS