Your topside computer’s network configuration should be the same as for the previous Companion software. To configure it, you can follow our network setup instructions.
BlueOS is designed as a modular collection of services, which are accessed and configured via a combined web interface.
The web interface monitors the autopilot and other main software components. It also listens for and displays connections from other HTTP servers (on TCP ports), which allows extensions and custom integrations to provide an interface through BlueOS while remaining independent from the main BlueOS release/update cycle.
- By default you can access BlueOS via blueos.local
- When BlueOS is connected to the same wifi network as your device you can also connect with it using blueos-wifi.local
- By default if BlueOS does not have a wifi connection configured within 5 minutes of booting, it will start its own wifi hotspot which, when connected to, allows accessing the BlueOS interface via blueos-hotspot.local
- The hotspot SSID is
BlueOS (******), with password
- The hotspot SSID is
When BlueOS is newly installed the interface provides a configuration wizard to help get things set up.
The Welcome section allows skipping the wizard if BlueOS and your vehicle have already been configured as desired:
To support BlueOS and autopilot firmware updates, it is recommended for BlueOS to be connected to the internet:
BlueOS supports multiple vehicle types, and allows selecting a quick-setup option for the most common ones:
Vehicle quick-setup involves setting appropriate parameters for the selected vehicle type and frame, as well as choosing a name for your vehicle, and changing the mDNS hostname if you would prefer to connect with something other than http://blueos.local:
Progress is displayed for any selected configuration changes, and an up to date autopilot firmware is downloaded and installed (if using a standard vehicle type):
A completion window is shown once all configuration is done:
When you first open the web interface, you'll see a page that looks like this:
As a brief overview,
- the header contains system health indicators and notifications, and some network and display configuration options
- the sidebar allows navigating between pages, and allows restarting, freeing up space, and reporting issues
- most pages show their content within the BlueOS interface sections, but some extensions open as full pages in a separate tab
For more details see the Advanced Usage Interface Overview section.
Updating / Releases
When starting out, it's important to connect to wifi so you can update to the latest suitable release.
First, click the wifi indicator to scan for available wifi networks
Select the desired network, type in the password, and click connect
Once connected, the wifi icon will change to show the signal strength, and the connected wifi network will be selected on the menu
Now that your BlueOS has an internet connection, you can perform the update to the latest available version.
Click on the hamburger menu (if the sidebar is not already open)
Under Settings, select BlueOS Version
If you're already on the latest version, the right side of your Local Version will be blank. If not, you should see a blue Update button.
Once the update button is clicked the update process will run. Please wait until it finishes - it will automatically reload the webpage for you.
BlueOS is capable of configuring and streaming multiple cameras simultaneously. The first time it boots, it will automatically detect any connected H264-capable cameras and start streaming them. If not, make sure your camera is properly connected, and that BlueOS is on the latest available version. Reset settings and restart BlueOS if necessary.
Additional information is available in the Advanced Usage Video Streams section.
A Raspberry Pi draws more power than many computer USB ports can provide, so a USB-C connection should generally only be used for data transfer, with a separate power supply (or through a powered USB hub).
usb0 network interface is configured to use a DHCP server at
192.168.3.1 by default, which does not provide access via the 192.168.2.2 static IP address.
If you are using MacOS, make sure to allow the RNDIS/ethernet gadget:
MacOS will consider a USB-OTG connection as a valid source of internet, which can be avoided by reordering your network interfaces, making sure that wifi and your actual wired internet connection interface are used with higher priority.