Mechanical platform
Chassis, suspension, steering, braking, body, mounting standards, and service access with CAD and a real bill of materials.
3DVR Compute · Open mobility
Research direction · build in publicA vehicle you can understand and keep.
Open hardware, open software, open diagnostics, repairable parts, local computing, and documentation that belongs to the owner.
MechanicalChassis, brakes, suspension, body.
EnergyBattery, BMS, charger, motor.
NetworkIsolated buses, diagnostics, logs.
ComputeLinux now, more open hardware over time.
User-ownedYour logs, diagnostics, configuration, and service data.
RepairableStandard parts, replaceable modules, ordinary tools.
Open by defaultPublish interfaces, software, CAD, schematics, and manuals where possible.
Offline-capableCore operation should not depend on a vendor cloud.
Architecture
Open the whole stack, layer by layer.
The vehicle is both a physical machine and a computing system. The project treats both as things an owner should be able to inspect, repair, and improve.
Energy + propulsion
Document battery modules, BMS, charger, inverter, motor, thermal systems, interfaces, and high-voltage boundaries.
Vehicle communication
Isolated CAN or equivalent networks, gateways, open diagnostics, logging, simulation, and replayable test data.
Open cockpit
Linux-based navigation, cameras, media, owner-controlled connectivity, local storage, and a 3DVR HUD without mandatory cloud dependence.
Modular computer
Replaceable compute rather than a disposable dashboard, with a long-term RISC-V path where the hardware is ready for the role.
3DVR
Maintenance knowledge, trip tools, local AI, automation, and personal context controlled by the person using the vehicle.
Roadmap
Retrofit first. Full platform later.
We can learn on ordinary vehicles without pretending we are ready to redesign every safety-critical system. Each stage should produce useful open artifacts for the next.
1 · CockpitLinux, sensors, GPS, cameras, read-only OBD-II/CAN.
2 · LabSimulation, replayable buses, bench rigs, hardware-in-the-loop.
3 · Prototype EVDocumented donor components and modular vehicle management.
4 · Physical platformOpen CAD, BOM, wiring, fabrication, and service documentation.
5 · Open computePush more of the stack toward auditable Linux and open silicon.
First practical milestone
Open Vehicle Dev Kit
Start with something useful, reversible, and testable on an existing car.
Read-only vehicle data
An isolated OBD-II/CAN interface for diagnostics and recording without issuing control commands.
Local computer
Linux or RISC-V compute with GPS, IMU, local storage, and optional cameras.
Open dashboard
A calm owner-controlled display for trips, diagnostics, maintenance, navigation experiments, and the future 3DVR HUD.
Reproducible data
Sanitized recorded bus data and simulation fixtures so most development can happen away from a moving vehicle.
Open ecosystem
Build on work that already exists.
These are references to learn from, not dependencies. Reuse proven open work where it fits and document the closed boundaries honestly.
Open Vehicle Control System
Open vehicle embedded hardware/software and a useful reference architecture for modular vehicle management.
Explore OVCS →Automotive Grade Linux
A Linux Foundation ecosystem developing open software platforms for automotive applications.
Explore AGL →TABBY EVO
Open Motors' modular EV platform provides a physical open-vehicle reference with published design material.
Explore TABBY EVO →RIGOLETTO
European research developing a RISC-V automotive hardware platform for software-defined vehicles.
Explore RIGOLETTO →Open transportation
Make transportation owner-controlled again.
Mechanics, EV builders, Linux developers, embedded engineers, CAD designers, repair technicians, and documentation people all have a place in this project.