Hi @grantdutoit -
Are you using a Raspberry Pi 4? The onboard WiFi is typically used to connect the system to the internet, to install extensions and download updates… otherwise it is not required!
It starts occuring after changing the ip address from 192.168.2.2 to something else like 192.168.2.10, but regardless of changing it back to dynamic 192.168.2.2 it didn’t help.
Couldn’t find a solution in the forum or elsewhere in the setting, probably there is way I am not aware of.
Anyone know how to reset those settings to default factory, preferably without resetting the whole ardusub settings and without access to the microsd card on the raspberry pi?
This network issue may be relevant. As far as I’m aware it is present in all the latest BlueOS versions, which is partly what’s holding up releasing 1.4.3 as stable (we want to fix the network problems first).
If so, you can try resetting the settings via the cog icon at the bottom of the sidebar.
If you’re using a Navigator, you can back up (save) ArduSub’s configuration from the Autopilot Parameters page, then load them back in afterwards.
That process also works for independent flight controller boards, but in those cases the autopilot parameters shouldn’t be affected by BlueOS configuration changes to start with.
I am having constant issues with blueos, doesnt have proper connection in the browser. Receiving dozens of errors in the notification about the wifi fetch fail, or autopilot type fetch fail…and many more.
Which version is considering more stable or the one that shouldnt have such behaviour, I believe its purely the problem with blueos software part as the hardware was working fine, constant ping between laptop and ROV using the 100m tether between 10-20ms, and cosntant ping with internal components like dvl, jetson.
The only problem right now is usage blueos, cockpit (browser version), cockpit (desktop version),
QGC receiving data that Autopilot sending and it seems constant.
Is there a way I can attach a log file so you can look at it?
The latest stable version is 1.4.2. We’re working on 1.4.3 with various stability fixes, but it has some intermittent network issues we’re trying to resolve that are related to some of the changes. You can try 1.4.3-beta.9 if you want to see if it helps, but it may not resolve your problem.
This screenshot is showing that the backend is offline (i.e. you have BlueOS loaded in a browser tab, but it cannot connect to the vehicle). In such cases all the other checks BlueOS does are expected to fail (e.g. checking the vehicle’s wifi and internet status, autopilot type, accessing the file browser all require communication with the vehicle, so cannot work without it).
This sounds like you might be connecting to it at the wrong address. Can you try checking which “global address” Cockpit is using, via Settings / General? If Cockpit is working then you should be able to access BlueOS using that same address (with http:// in front).
The forum allows log file uploads, so if you download a BlueOS system log you should just be able to upload it using the upload button in the editor (the tray with the upward arrow), or just drag the file into a post that you’re editing.
