Repository navigation
Havne v0.7.0
Havne 0.7.0 is for the drive and for reading it back: a Dashboard you build by hand from eight kinds of gauge, themes for a cabin after dark, and an analysis log that records only the signals you pick, at their own pace, into a wide CSV ready for a spreadsheet. Read DISCLAIMER.md before connecting it to a vehicle.
Downloads
| For | Download |
|---|---|
| Windows (x64) | havne-0.7.0-windows-x64.zip |
| Linux (x86_64), the app | havne-0.7.0-linux-x86_64.AppImage |
| Linux (64-bit ARM: a Raspberry Pi 3 or later), the app | havne-0.7.0-linux-aarch64.AppImage |
| Android 12 or later (64-bit ARM) | havne-0.7.0-android-arm64-v8a.apk |
Linux (x86_64): havne-cli and core alone, for your own programs |
havne-core_0.7.0_amd64.deb (Debian, Ubuntu) or havne-core-0.7.0-linux-x86_64.tar.gz |
Linux (64-bit ARM): havne-cli and core alone |
havne-core_0.7.0_arm64.deb (Raspberry Pi OS, Debian, Ubuntu) or havne-core-0.7.0-linux-aarch64.tar.gz |
| Python wheel (Windows x64, Linux x86_64 and arm64, macOS arm64 13+) | pip install havne-0.7.0-py3-none-<platform>.whl; Python 3.11 or later |
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). The AppImage runtime's sources, fuse-3.15.0.tar.xz and type2-runtime-20251108.tar.gz, are there as LGPL-2.1 asks: the runtime links libfuse statically (the AppImage's notice says more). GitHub adds the source code archives.
Try it
Windows
- Download
havne-0.7.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 Advanced, then press the
mock://demopreset on Connection 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.7.0-linux-x86_64.AppImage, or on 64-bit ARM (a Raspberry Pi 3 or later on a 64-bit system)havne-0.7.0-linux-aarch64.AppImage. chmod +xit, then run it.- In Settings, tick Developer mode under Advanced, then press the
mock://demopreset on Connection 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.7.0_amd64.deb (./havne-core_0.7.0_arm64.deb on ARM), or unpack havne-core-0.7.0-linux-x86_64.tar.gz (havne-core-0.7.0-linux-aarch64.tar.gz) anywhere.
Android 12 or later (64-bit ARM)
- On the phone, download
havne-0.7.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 Advanced, then press the
mock://demopreset on Connection 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.6.0
Breaking for scripts
- The CSV export's default is the wide layout:
Time (ms), then a column a signal, a row each sweep or on a grid. The long form as before ishavne-cli export --layout long(C:layout = ECUIO_CSV_LONG). A C caller that zeroes the export options' reserved words gets the wide layout (ADR-0056). - Python's
Recording(folder, profile=..., signals=...)raisesValueErrorwhen given both.
A Dashboard of your own
- Edit (or, on a phone, a long press on a gauge) adds dials, rings, bars, cells, digits, numbers, sparklines and shift lights for any numeric signal of the profile, connected or not, and sets each one's label, range, warning zones, decimals, size and place. Pages can be added, renamed, moved and removed, and Reset brings back the built-in layout. Layouts are kept separately for the phone and the desktop (ADR-0057).
- Low glare and Night themes, amber and red on near black, under Settings, Display. A gauge past its danger value shows a mark beside its reading, so danger doesn't rest on color alone.
- The shift lights flash at 3 Hz at most.
An analysis log
- Start log in the header records the signals ticked on Live from that moment, asking the ECU for those alone, with the log's time and size beside it. Stop log opens it on Recordings. The Dashboard's header says when a log wasn't started or ended on its own, and why (ADR-0056).
havne-cli log <uri> <folder> --signal <name>...is the same log from a script.havne-cli exporttakes--rows,--unitsand--signal.- For programs:
ecuio_session_set_focusnarrows a running session's requests,ecuio_session_recordattaches a recorder to a running session (Python:set_focus,record), andecuio_export_estimategives a wide export's rows and exact size before it's written.
Recordings and imports
- The Recordings page imports a CSV or candump log, on every platform. A CSV needs no column map: the panel shows what it guessed from the header, each column can be changed or left out, and Save as map keeps the result.
havne-cli import csvand Python guess the same way. - The viewer shows a recording's frames: a Values | Frames switch opens the Log page's table, filter and By ID list over the part in view.
havne-cli framesand Python'sread_framesread frames between two times. - The health report names the vehicle's baseline recording;
havne-cli healthtakes--baseline.
Settings and the Log page
- Settings is a list of pages: Connection, Vehicle, Signals, Recording, Display and Advanced.
- The Log page filters by an ID mask, a length and a time, and By ID marks the bytes that changed.
Fixes
- A session kept connected while answers paused for 36 minutes or more and then resumed hung for good (since v0.3.5).
havne-cli stream --recordcrashed when its output went away (since v0.4.0). - A phone's tab bar has touch-sized tabs clear of the system's bars, and Android asks for Nearby devices again after a refusal.
- The Linux AppImage and the Android APK carry Qt's notice and the license texts of what they bundle; the AppImage's runtime is pinned and checked; the Windows download no longer includes Microsoft's shader compiler DLLs; the APK no longer carries Qt's QML debugger. 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, clang-tidy, CodeQL and the load test; a GCC or Clang warning fails it. On Windows the suite is 1814 cases, all passing but six that need the cross-arch step, the car's raw recordings, Linux or Wireshark's
tshark, and the cross-arch cases pass through the x86 helper too. - On a car, at this release's code:
havne-cli logon native Ubuntu 26.04 over the OBDLink MX+ (Bluetooth) and the OBDX Pro VX in ELM mode (USB and WiFi), at 1, 4 and 8 signals, with the Innomaker USB2CAN listening. Only the picked signals were asked for, each recording closed whole, and the wide CSV held exactly the picked columns. At 8 signals over the VX's WiFi the run stalled for about 18 s of 71 s, cause unknown (the session sheet). - On a phone: a development build on the test phone under
mock://: the Dashboard, the themes and Settings. - Not yet run: the app's Start log and Stop log, and a hand-built Dashboard, on a real car; the analysis log over J2534 or requesting through SocketCAN; the iPhone app on a device. The published downloads themselves haven'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.7.0.intoto.jsonl. Check them with the GitHub CLI:
sha256sum -c --ignore-missing SHA256SUMS.txt
gh attestation verify havne-0.7.0-windows-x64.zip -R erickramer42/havne
gh attestation verify havne-0.7.0-android-arm64-v8a.apk -R erickramer42/havne
gh attestation verify havne-0.7.0-linux-x86_64.AppImage -R erickramer42/havne
gh attestation verify havne-core_0.7.0_amd64.deb -R erickramer42/havne
gh attestation verify havne-0.7.0-py3-none-win_amd64.whl -R erickramer42/havne
Those read GitHub's attestation store; add --bundle havne-0.7.0.intoto.jsonl to check against the attached file instead.
The SBOM, havne-0.7.0.spdx.json, is attested to the zip, the APK, the AppImages, the debs, the tarballs and the wheels: 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.7.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 core's packages ship and every download's notice repeats, 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.