Hi there, going through my vehicle setup, and I feel like I am missing something.
To preface, I tried going to vehicle setup to load default parameters (Blueboat120.PARAMS) and initially they appear to write, but then I get the error failed to write some parameters. Please restart and try again (which I have attempted) to no luck.
I am following the blueboat software setup guide and am running into some issues. I have paired my base station, and connected to the basestation 2.4Ghz wifi. I am at the stage where I am accessing BlueOS and I have connected to the basestation wifi in BlueOS, I have wifi but no internet but thats normal cause its a local connection?
Following the steps I search for BlueOS updates and I look for autopilot firmware updates (currently I am on 4.2.3 (STABLE) I get no data available and get the error Autopilot Manager (Firmware_fetch_fail error:Request failed with status code 500)
Question 1:
I am wondering do I need an internet connection at this point to get access to firmware updates (if yes then how? With a wifi adapter/dongle?)or am I simply on the latest update? The error message makes me think its the former?
I continued with the software setup and attempt to calibrate the powerSwitch, when I open the extensions tab, there aren’t any present like in the startup guide? And I also get this error?
“Kraken service
Extensions_manifest_fetch_fail
cannot connect to host bluerobotics.github.io:433 ssl:default [Temporary failure in name resolution] [errno-3]Temporary failure in name resolution.”
I should be able to see these extensions present in the setup guide should I not?
All these errors right off the bat makes me thing I’ve done a silly mistake and set something up wrong? I’m hoping someone can set me straight? Im sorry for the wall of requests.
Thanks for all your help!
Cheers
Alex
You do need an internet connection in order to get updates, yes! You can either bridge your computer’s WiFi with internet to the ethernet connection going to the BaseStation, or connect the Raspberry Pi WiFi to a network with internet access - WiFi icon in the upper right.
4.4.0 is the latest version of ArduRover.
You will only see extensions appear if you have an internet connection! Your screenshot shows that BlueOS is connected to WiFi, but it doesn’t have internet access (globe with slash going through it.)
Once connected to internet, please update BlueOS to 1.2 beta8 - enable pirate mode for this option to show up under BlueOS Version menu. If you’re still having issues when loading the default parameters, checkout this thread - if you flashed the BlueOS image yourself you need to add a lights.lua file.
I am having the same issue, but I seem to have my Wifi setup and my BlueOS appears to have internet access (globe does not have a slash through it). Any suggestions on why I cannot reach the extension store?
I have issue accessing the extension page, while I think I do have pretty good internet connection. Please check the screenshots below. I am running on BlueOS 1.2.6, which I think it is the latest stable one.
From your screenshots your vehicle at least thinks it has internet access, but the notifications about the failed internet check could indicate some problem there (or may just be from running the check too soon after startup, before all the BlueOS services are fully initialised).
If the internet is in fact fine then it’s also possible you’re running into issues with rate limiting[1] when fetching the extensions list, which can generally be resolved by waiting for a few hours[2] and/or reducing the number of installed Docker Images (e.g. if you have several unused Extensions or old BlueOS versions it may help to delete them). If you have other systems on your network that are using Docker Hub then that may also cause the same issue.
That is something we’re aiming to resolve / work around with local caching and by hosting the Extensions ourselves, but that’s part of a more significant alternative store development project, which is ongoing.
Docker Hub (where the extensions are currently hosted) has rate limits for how often a single IP address can fetch and/or download Docker Images, and BlueOS currently pulls tags for each installed BlueOS-core and Extension image. ↩︎
The limits reset every 6 hours, so that should be the maximum required waiting time. ↩︎
