BlueOS

BlueOS is a modular, robust, and efficient platform for managing a vehicle or robot from its onboard computer. It is the evolution of the Companion project, which aimed to route a vehicle's video stream and communications to its control station computer. Recognizing the need for a more sophisticated and scalable system, BlueOS was created from the ground up, embracing modularity to ensure portability, robust updating, and extensibility.

<p align="center"> <a href="doc/dashboard.png"> <img src="doc/dashboard.png" width="75%"> </a> </p>

Quick Links ⚡

• Official documentation
• Installation
• Development documentation
• Contributions
• Code of Conduct
• Registered Extensions
• Custom installation

Principles and Goals 📖

The development of BlueOS is driven by the following core principles:

• An interface that is simple by default but powerful when needed - the user has the power to change anything they desire and customize the full experience
• Designed to focus on what matters, improving user access to information and controls with a human-friendly UI and UX
• Make complex tasks simpler and improve ease of use by reusing design patterns from other applications (based on the material UI guidelines)
• Advanced error handling and detection, making any problems clear to the user and developers, along with how to fix them
• Simplify development, providing full access to our services API and modular development model
• Portable and flexible, you should be able to run on a Raspberry Pi 3/4/5 or any SBC with Linux operating system, contributions are welcomed
• Highly functional with low CPU usage, the entire system is built to run efficiently
• Developed on solid foundations, critical parts or intensive workforce services are designed using the most advanced languages and features available for stability

The design, organization, and future releases of BlueOS are aligned with these principles, striving to provide an optimized and enriched user experience.

Release Types ✨

BlueOS is available in three release types:

• Stable: Officially tested and validated versions with long-term support. Recommended for most users.
• Beta: Lightly tested rolling releases with new features, bug fixes, and improvements.
• Master: Bleeding-edge development releases with almost daily changes. These are the very latest features that may not have been tested yet.

Vehicle Support 🛸

BlueOS has been designed with a focus on vehicle and platform agnosticism. Our aim is to facilitate broad compatibility across a wide spectrum of applications. Currently, BlueOS officially supports the following vehicle types:

Boats (ArduRover)

ArduRover is an open-source, uncrewed boat platform. Whether you are commanding a leisure boat or a research vessel, BlueOS's compatibility with ArduRover ensures that you can navigate the waters smoothly 🌊.

BlueBoat is supported by default.

Submarines (ArduSub)

ArduSub is the go-to control system for remotely operated underwater vehicles (ROVs) 🐟. BlueOS offers seamless integration with ArduSub, enabling efficient management and operation of underwater vehicles.

BlueROV2 is supported out of the box.

Generic (ArduPilot / PX4)

BlueOS provides generic support for a wide variety of terrestrial, aerial, and marine uncrewed vehicles that use ArduPilot and PX4 autopilots. This extends the range of vehicles that can be managed using our system, from drones to autonomous cars and more.

Note: Specific vehicle configuration may be necessary to ensure optimal performance with BlueOS.

Custom installation

Raspberry Pi and hardware preparation

For installations that need hardware configuration and preparation of the operating system, it´s highly recommended to use the installation script and customize it as necessary to perform the necessary changes for your system.

Running BlueOS

It's highly recommended to have debian, debian based (like ubuntu) or any linux distribution with similar services and tools to run BlueOS. This is necessary since BlueOS use specific components on the host computer to do software configuration and take control of the system.

Running via Docker Compose (docker compose)

1. Clone the repository with git
   • git clone --depth=1 --recurse-submodules --shallow-submodules https://github.com/bluerobotics/blueos
2. Modify core/compose/compose.yml example file.
   • BLUEOS_DISABLE_SERVICES: Comment or remove this line if you want BlueOS to have full access of the system, including wifi and ethernet configuration.
   • BLUEOS_DISABLE_MEMORY_LIMIT: Comment or remove this line if running in a system with 4GB of RAM memory or less.
   • BLUEOS_DISABLE_STARTUP_UPDATE: This environment variable is necessary, "startup update" procedure is only required when bootstrap is running to manage the system (not the case when using docker compose).
   • SSH_USER: Uncomment and update the value for the SSH user, required for BlueOS to run commands and access the host computer if necessary.
   • SSH_PASSWORD: Uncomment and update the value for the SSH user password.
3. Run docker compose

   • cd core/compose/ && docker compose pull && cd - # Ensure that docker is up-to-date
     docker compose -f core/compose/compose.yml up
     

In the end, your docker compose file should look like this

version: "3.7"
services:
  blueos-core:
    container_name: blueos-core
    image: bluerobotics/blueos-core:master
    privileged: true
    network_mode: host
    pid: host
    restart: unless-stopped
    environment:
      - BLUEOS_DISABLE_MEMORY_LIMIT=true
      - BLUEOS_DISABLE_STARTUP_UPDATE=true
      - SSH_USER=pi
      - SSH_PASSWORD=raspberry
    volumes:
      - ./workspace/.config:/root/.config
      - ./workspace/etc/blueos:/etc/blueos
      - ./workspace/tmp/wpa_playground:/tmp/wpa_playground
      - ./workspace/usr/blueos/bin:/usr/blueos/bin
      - ./workspace/usr/blueos/extensions:/usr/blueos/extensions
      - ./workspace/usr/blueos/userdata:/usr/blueos/userdata
      - ./workspace/var/logs/blueos:/var/logs/blueos
      - /dev:/dev
      - /etc/dhcpcd.conf:/etc/dhcpcd.conf
      - /etc/machine-id:/etc/machine-id:ro
      - /etc/resolv.conf.host:/etc/resolv.conf.host:ro
      - /run/udev:/run/udev:ro
      - /sys:/sys
      - /var/run/dbus:/var/run/dbus
      - /var/run/docker.sock:/var/run/docker.sock
      - /var/run/wpa_supplicant:/var/run/wpa_supplicant
      - /run/log/journal:/run/log/journal:ro
      - /var/log/journal:/var/log/journal:ro
      - /home/patrick/.ssh:/home/pi/.ssh

The system should be accessible now via 0.0.0.0:80 or via the network using the IP address of the device.

Running via Docker (docker run)

You can update the script to follow your board configuration. Here, we are creating temporary folders for the binds, but it's highly recommended to create a workspace environment where you can set the binds to be persistent.

# Prepare workspace
mkdir -p /tmp/workspace/var/logs/blueos
mkdir -p /tmp/workspace/.config
mkdir -p /tmp/workspace/tmp/wpa_playground
mkdir -p /tmp/workspace/etc/blueos
mkdir -p /tmp/workspace/usr/blueos/{bin,extensions,userdata}

# Docker command
docker run --privileged --network=host --pid=host --name=blueos-core \
  --mount type=bind,source=/dev/,target=/dev/,readonly=false \  # Required for hardware access
  --mount type=bind,source=/sys/,target=/sys/,readonly=false \  # Required for system access
  --mount type=bind,source=/var/run/wpa_supplicant,target=/var/run/wpa_supplicant,readonly=false \ # Required for wifi control
  --mount type=bind,source=/tmp/workspace/tmp/wpa_playground,target=/tmp/wpa_playground,readonly=false \ # Required for wifi control
  --mount type=bind,source=/var/run/docker.sock,target=/var/run/docker.sock,re