Skip to content

Project

A purpose-built vehicle and field computing platform.

A complete head unit system for vehicles and mobile field work: navigation, media playback, phone integration, cameras, and system monitoring in one touch-friendly interface optimised for driving. It currently runs in the Transit, and is being designed as a broader mobile computing architecture rather than as something specific to one vehicle.

Current Running in the vehicle today.

Ubuntu 22.04+

Target platform, with a touchscreen

Node.js 18+

Runtime, managed with pnpm

4

Camera roles in the live wall

-30°C

Cold-start design target

Core Functionality

Everything a driver needs, without the phone in their hand.

Maps & Navigation

GPS-powered navigation with waypoint management, so a route can be set up before leaving rather than while driving.

Media Player

A local music library with an MPV backend, so playback does not depend on a data connection.

Phone Integration

Bluetooth audio and pairing over the phone connection. Hands-free calling needs a telephony backend this unit does not have, and the dialer says so plainly rather than failing silently.

Settings Management

Persistent configuration on a SQLite backend, so the setup survives a power cycle.

Cameras & Monitoring

Four camera roles across two wired cameras: a live wall, clip playback, downloads, and trimmed exports.

System Monitoring

System status and hardware health surfaced in the same interface, not in a separate admin tool.

System Features

Built to be left running.

A head unit in a vehicle is not a laptop that gets closed. It stays on, keeps the data current, and remains useful when the network does not.

Fullscreen camera focus

Any camera can be taken full-screen, one tap from the wall — rather than being crowded into a grid.

Real-time monitoring

System status and hardware health shown in the interface rather than hidden in logs.

WebSocket updates

Live data synchronisation, so the screen does not depend on polling to stay accurate.

Prometheus metrics

A machine-readable monitoring endpoint for anything that needs to scrape the box.

Interface

Designed around the driver's hands, not the developer's desk.

The interface is built for a fixed touchscreen in a moving vehicle, which is a much narrower constraint than a general-purpose application.

  • Large buttons and gestures sized for driving rather than for a mouse
  • Responsive layout tested against a 17-inch touchscreen
  • Dark theme, to stay usable at night without glare
  • Offline-first behaviour, degrading gracefully without a connection

Electron + React

The dashboard is an Electron application with a React interface.

Express services

A Node.js/Express API server exposes status, settings, media, GPS, Bluetooth, and camera routes.

SQLite + Prisma

Configuration and application state live in SQLite, accessed through the Prisma ORM.

HAL abstraction

A hardware abstraction layer keeps GPS, Bluetooth, and media behind one interface.

The CapnCoil mobile platform parked in low light during winter testing.
The camera system is exercised where it matters: in winter, in the dark, and on a vehicle that is being used rather than demonstrated.

Camera Workflow

Cameras treated as a working part of the system, not a novelty.

The camera stack covers the parts that make video useful after the fact: seeing what each feed is doing now, getting a clip off the device, and trimming an export without leaving the vehicle.

Being straight about the hardware: the live wall is built for four camera roles — front, rear, left, and right — and the machine currently has a single physical camera, which the remaining roles read from. Continuous background recording is not implemented; captured events are held in a bounded in-memory buffer and are gone when the process restarts. Clip retrieval works on recordings that already exist on disk.

  • Four camera roles — front, rear, left, and right — with per-camera enable toggles
  • Fullscreen focus on any single feed, taken from the live wall
  • Clip playback, downloads, and trimmed MP4 exports from the interface
  • Monitor enablement separated from camera access, as groundwork for a fuller recording stack

Requirements

What the head unit needs to run.

Requires Ubuntu 22.04 or newer with a touchscreen, Node.js 18 or newer, pnpm, a Bluetooth adapter for phone integration, and a USB or Bluetooth GPS device.

The head unit is developed and maintained in house, and access is arranged as part of an evaluation or field validation programme rather than distributed as a download. Recent development work is logged on the homepage What's new log.

Want this evaluated in real conditions?

The head unit is one of the things the mobile platform exists to test. Product evaluation and field validation programmes are arranged through the contact form.