Repository navigation
Havne v0.5.0
Havne 0.5.0 reads the signals you define: your own PIDs and DIDs as signal files, written in the app or converted from an OBDb set, enumerations and computed signals such as boost, and plugins' data tier, a package of signal files that the car's VIN proposes; and it comes for 64-bit ARM Linux, such as a Raspberry Pi. Read DISCLAIMER.md before connecting it to a vehicle.
Downloads
| For | Download |
|---|---|
| Windows (x64) | havne-0.5.0-windows-x64.zip |
| Linux (x86_64), the app | havne-0.5.0-linux-x86_64.AppImage |
| Linux (64-bit ARM: a Raspberry Pi 3 or later), the app | havne-0.5.0-linux-aarch64.AppImage |
| Android 12 or later (64-bit ARM) | havne-0.5.0-android-arm64-v8a.apk |
Linux (x86_64): havne-cli and core alone, for your own programs |
havne-core_0.5.0_amd64.deb (Debian, Ubuntu) or havne-core-0.5.0-linux-x86_64.tar.gz |
Linux (64-bit ARM): havne-cli and core alone |
havne-core_0.5.0_arm64.deb (Raspberry Pi OS, Debian, Ubuntu) or havne-core-0.5.0-linux-aarch64.tar.gz |
The other files under Assets check a download or debug one: SHA256SUMS.txt, the build provenance (.intoto.jsonl) and the SBOM (.spdx.json), described below under Verifying the downloads; the Windows PDBs (-symbols.zip) and havne-cli's Linux debug info (-dbgsym deb, -debug tarball). GitHub adds the source code archives.
Try it
Windows
- Download
havne-0.5.0-windows-x64.zipand unzip the whole folder. - Run
havne.exe. The program isn't code-signed, so SmartScreen may stop it the first time: choose More info, then Run anyway. - In Settings, tick Developer mode under Display, then press the
mock://demopreset under Adapter and Connect.
The zip's README.txt covers adapters and what each file is. havne-cli.exe is beside havne.exe: havne-cli stream mock://demo --values --count 20 prints a simulated car's frames and values.
Linux (x86_64 or 64-bit ARM, glibc 2.39 or later: Ubuntu 24.04 and newer, Debian 13 and Raspberry Pi OS 13, Fedora 40 and newer, Arch)
- Download
havne-0.5.0-linux-x86_64.AppImage, or on 64-bit ARM (a Raspberry Pi 3 or later on a 64-bit system)havne-0.5.0-linux-aarch64.AppImage. chmod +xit, then run it.- In Settings, tick Developer mode under Display, then press the
mock://demopreset under Adapter and Connect.
It takes OpenGL, fonts and FUSE from the system; a minimal install may lack them. docs/linux.md says what to install, how to reach an adapter (serial permissions, Bluetooth, SocketCAN) and where Havne keeps its files.
For havne-cli and the core alone: sudo apt install ./havne-core_0.5.0_amd64.deb (./havne-core_0.5.0_arm64.deb on ARM), or unpack havne-core-0.5.0-linux-x86_64.tar.gz (havne-core-0.5.0-linux-aarch64.tar.gz) anywhere.
Android 12 or later (64-bit ARM)
- On the phone, download
havne-0.5.0-android-arm64-v8a.apkand open it. Android asks to let your browser or file manager install apps the first time; Play Protect may offer to scan an app from outside Google Play. - Open Havne. In Settings, tick Developer mode under Display, then press the
mock://demopreset under Adapter and Connect.
A later release installs over this one and keeps its settings and recordings. A Havne built by CI or from source carries another key, so uninstall it first.
What's new since 0.4.1
Your own signals
- Signal files: a user's own signals as JSON: Service 01 PIDs and Service 22 DIDs on up to four modules, read as numbers, text, enumerations or signals computed from others, the same in the app and
havne-cli. Core reads a file from its bytes and refuses anything wrong when it loads, naming the line and column (docs/signal-files.md, ADR-0051). - In the app, per vehicle: Settings' Vehicle section imports signal files and writes a vehicle's own a signal at a time, and Read once asks the car for one signal with no session connected, showing the reply's bytes beside the value. Each file is a profile under What to read (
user.<name>); one that extendsobd2takes obd2's place on an adapter. - Enumerations and computed signals: Live and the Recordings viewer show an enum's label in place of its number, and a computed signal runs a bounded program over up to four others, each no older than its own age bound. The simulated car now reads its MAP and baro, and Live shows its boost.
- An OBDb set converted:
havne-cli signals import obdb <file> --out <file>turns an OBDb signal set on disk into a signal file, reporting each field that differs from OBDb's reading and each signal left out, with the set's attribution (CC BY-SA 4.0) kept in the file. Havne fetches nothing and ships no OBDb data. - On the command line:
havne-cli signals checksays what a file holds or why it's refused, andstream --signalsandsim --signalsread through one. - In recordings: a session a signal file decodes keeps a copy of the file beside the recording, so a replay decodes the same values, and an enum's labels are recorded too (format 3; formats 1 and 2 still open).
Plugins' data tier
- A plugin is a package of signal files with one manifest naming the cars it's for; each variant, its files merged, is a profile (
plugin.<id>.<variant>). Settings imports a packed plugin, the car's VIN proposes the variants that fit, and the one picked stays with the vehicle (plugins/README.md, ADR-0052). havne-cli plugins list,match --vinandcheck; on Linux,plugins check --on <vcan>runs a plugin's value fixtures through the simulated ECU and decodes them back, and CI checks the repository's example plugin that way.
The simulated car
havne-cli sim "mock://sim?modules=2"adds a second module with DIDs of its own, and the simulated ECU answers the DIDs of any registered profile, a plugin's included, so a set of DIDs is checked with no car. The faultpending:<n>answers a request "response pending" first.
Linux on 64-bit ARM
- The app as an AppImage, and
havne-cliand core as a deb and a tarball, for a Raspberry Pi 3 or later on a 64-bit Raspberry Pi OS 13 or Ubuntu 24.04 and newer, with the same checksums, provenance and SBOM as the x86_64 files (docs/linux.md).
For programs that use core
- C ABI break: the signal set's layout is 4 (
ECUIO_SIGNAL_SET_LAYOUT), with its enum and computed tables; a set built against an earlier layout is refused until it's rebuilt. A set may derive up to 256 requests. - New headers:
plugin.h(plugins) andobdb.h(the OBDb conversion);signals.hloads a signal file.
Fixes
- Before release, a review of the new code tightened its edges: a number with a huge exponent parses at once, a computed signal may read one listed after it, a field past any reply is refused, a name with a line break or two signals of one name no longer spoil a recording, and an OBDb command with ID 000 or a doubled formula sign is skipped rather than failing the whole import. In Settings, a vehicle's own signals save apart from another's, an edit renames its signal, and a variant the VIN proposed can be picked once the session ends.
- The full list is in the CHANGELOG.
What's verified, and where
Havne's claims are tiered (docs/testing.md):
- Every build runs the full test suite on Windows, macOS and Linux in CI, plus sanitizers, fuzzing (the new readers of JSON, signal files, plugins and OBDb sets started from seeds built from the committed fixtures), clang-tidy, CodeQL and the load test; a GCC or Clang warning fails it. The Android and iOS apps are cross-built there, and the 64-bit ARM Linux files are built and smoked on an ARM runner. On Windows the suite is 1238 cases, all passing but three that need a local build tree, the car's raw recordings or Linux, and the 101 cases of the 32-bit driver path pass through the x86 helper too. With GCC on Ubuntu 26.04 (WSL) the whole app's suite, 1103 cases, passes.
- A plugin through the simulated ECU: on a virtual CAN bus, every value fixture of the example plugin is answered by the simulated ECU from its variant's file and decoded back by a SocketCAN session through the variant's profile (CI's Linux job).
- The Linux app on the simulated car (a development build from before this release's review fixes, under WSLg): with the simulated car answering on a virtual bus as two ECUs, a DID defined in Settings' form read once and then on Live from the second module, a synthetic OBDb file converted and imported read its gear from the same module (as its raw number: the build predates Live's enum labels, which the tests check), and Live showed the simulated car's boost below zero at idle and about zero at full load (testing.md).
- On a Raspberry Pi 3 (aarch64, Kali Linux): the ARM runner's AppImage ran 10 s offscreen, and its debs and tarballs passed the release's own checks; the release's files get the same check before this release is final.
- Not yet run: signal files and plugins against a real ECU or adapter (each read so far is the simulated car's); SocketCAN requests through a real controller (no controller on hand offers one-shot mode); the iPhone app on a device. This build itself hasn't connected to an adapter or a car.
Verifying the downloads
SHA256SUMS.txt holds every download's SHA-256, the debug files' and the SBOM's. One signed build provenance from this repository's release workflow covers every download, attached as havne-0.5.0.intoto.jsonl. Check them with the GitHub CLI:
sha256sum -c --ignore-missing SHA256SUMS.txt
gh attestation verify havne-0.5.0-windows-x64.zip -R erickramer42/havne
gh attestation verify havne-0.5.0-android-arm64-v8a.apk -R erickramer42/havne
gh attestation verify havne-0.5.0-linux-x86_64.AppImage -R erickramer42/havne
gh attestation verify havne-core_0.5.0_amd64.deb -R erickramer42/havne
Those read GitHub's attestation store; add --bundle havne-0.5.0.intoto.jsonl to check against the attached file instead.
The SBOM, havne-0.5.0.spdx.json, is attested to the zip, the APK, the AppImages, the debs and the tarballs: add --predicate-type https://spdx.dev/Document/v2.3 to check it.
The APK is signed with Havne's release key, whose certificate SHA-256 is fb4f415a1f6c0dc56ee54dcd454c29d2226bc293c7b4c978a9b9bc8e74c4210f (packaging/android/release-cert.sha256). With the Android SDK's build tools, apksigner verify --print-certs havne-0.5.0-android-arm64-v8a.apk prints it.
Third-party data
Havne's core carries data from others, each under its own terms, listed in core/THIRD_PARTY_NOTICES.txt, which the Windows zip and core's packages ship, and compiled into every binary:
- Trouble-code titles: SAE J2012's generic powertrain and network codes, from Wal33D/dtc-database (MIT).
- Vehicle makes: the manufacturer codes of NHTSA's vPIC, a work of the US government.