DocumentationReference

Community and talks

Conference videos, slides, the forum thread, the GitHub organisation, and how to contribute.

#Where it comes from

OVCS was started in early 2024 by Marc Lainez, Loïc Vigneron and Thibault Poncelet at Spin42, to make vehicle embedded computing accessible with off-the-shelf components and high-level languages. The team built the framework and, on it, the reference vehicles that prove it works:

  • OVCS1: a 2007 Volkswagen Polo converted to electric with a Nissan Leaf AZE0 drivetrain, a Bosch iBooster Gen2, an Orion BMS2 and custom Arduino controllers, orchestrated by Elixir on Raspberry Pis running Nerves.
  • OVCS Mini: a Traxxas RC car, so remote-control and ROS 2 work can be developed safely before it reaches the full-size car.
  • OBD2: a scan tool for any car with a diagnostic port.

The talks mostly show OVCS1 and OVCS Mini; what they demonstrate is the framework underneath. See Framework and vehicles.

#Talks and videos

EventDateWatch and read
ElixirConf EU 2024April 2024Retrofitting a Car and Running it with Elixir (video) · slides
MakilabNovember 2024slides
FOSDEM 2025February 2025Converting an '07 car to an RC EV using open source software (video) · Building a robot from a Traxxas RC car (video) · slides
OVCS teaser2025Open Vehicle Control System teaser (video)

Build logs and demos: the Spin42 Engineering YouTube channel.

#Ask and discuss

#Repositories

Everything lives under the open-vehicle-control-system GitHub organisation.

RepositoryWhat it is
ovcsThe monorepo: the framework, the three reference vehicles under vehicles/, and these docs
cantasticYAML-driven CAN library: SocketCAN, frame encoding and decoding, ISO-TP, OBD2
express_lrsMAVLink v2 receive-only decoder for ExpressLRS handsets
msp_osdMSP / DisplayPort OSD stack for HDZero, Walksnail and DJI video transmitters
ovcs_controlPID controller, input filters, and an interactive tuning simulator
presentationsSlide decks from the talks
ovcs_base_can_system_rpi4Nerves system: Raspberry Pi 4 with CAN, for the VMS and bridge firmwares
ovcs_base_can_system_rpi5Nerves system: Raspberry Pi 5 with CAN and display, for the infotainment
ovcs_base_can_system_rpi3aNerves system: Raspberry Pi 3A with CAN, for bridge firmwares such as radio control
ovcs_bridges_system_rpi5Nerves system: Raspberry Pi 5 for bridge firmwares with stereo cameras and a Hailo-8 (perception)

mise run libraries sideloads the four libraries into libraries/, because they are useful outside OVCS. The framework-internal contracts (ovcs_bridge, ovcs_bus, ovcs_can, ovcs_vehicle, ovcs_drivers) live in the monorepo. See Repository layout.

#Contributing

Set up as any user would (Getting started), then check:

sh
git clone https://github.com/open-vehicle-control-system/ovcs.git
cd ovcs
mise trust
mise install
mise run cli
./ovcs doctor

Before opening a pull request:

  • Style. CODE_STYLING.md documents the conventions. Credo covers the Elixir apps, Ruff the Python tooling, cspell the spelling. Guides follow the documentation rules in CLAUDE.md and pass elixir scripts/check_docs.exs.
  • The guides are the website. Every guide linked from docs/README.md is published as-is on ovcs.be/docs; add a new guide there to put it in the navigation. The website pins this repository as a submodule and bumps it to main daily, so a merged guide change goes live with the next bump, after the website's own checks. To preview an unmerged change, run the website with OVCS_DIR pointing at your checkout (its README has the commands).
  • CI runs on pull requests. .github/workflows/ holds ci.yml (the Elixir tree, every PR), firmware.yml (every firmware build, on PRs touching vms/, infotainment/, bridges/, vehicles/, libraries/ or mise.toml; the only thing that catches a host-versus-target OTP mismatch) and ros2.yml (the container stacks and the Zenoh pin check, on PRs touching compose/ or ruff.toml).
  • Sideloaded libraries have their own repositories. A change to Cantastic, ExpressLRS, MSP OSD or ovcs_control is a pull request there, not against libraries/ here.
  • Vehicles live in vehicles/. A new vehicle is a new package scaffolded with ./ovcs new, not a framework change. The cores, firmware shells and libraries stay free of vehicle-specific code; if your vehicle needs something the framework cannot express, open a separate framework pull request. See Your vehicle package.
  • The reference vehicles are examples, not requirements. Fixes to them are welcome; nothing in a new vehicle should depend on them.
  • Nerves systems are forks pinned to upstream tags; Toolchain and OTP has the migration recipe.

#Disclaimer and licence

OVCS is released under the MIT License, copyright Spin42 SRL. No neural-network weights are committed: the YOLOv8 weights the perception pipeline can use are AGPL-licensed and don't compose with MIT. mise run fetch-models downloads them and prints each licence first. The default Hailo model is the Apache-2.0 NanoDet-RepVGG.

This page is docs/community.md in the ovcs repository; edit it there.