Repository navigation
Releases
Havne v0.8.0
Havne 0.8.0 lets a log or a warning start from the car's own state: conditions judged in a session, alerts in the app (a banner, colored values and, on Android, a tone), armed recording that writes a window when a condition fires, one plugin store for every import, and computed signals with functions, comparisons and chains. Read DISCLAIMER.md before connecting it to a vehicle.
Downloads
| For | Download |
|---|---|
| Windows (x64) | havne-0.8.0-windows-x64.zip |
| Linux (x86_64), the app | havne-0.8.0-linux-x86_64.AppImage |
| Linux (64-bit ARM: a Raspberry Pi 3 or later), the app | havne-0.8.0-linux-aarch64.AppImage |
| Android 12 or later (64-bit ARM) | havne-0.8.0-android-arm64-v8a.apk |
Linux (x86_64): havne-cli and core alone, for your own programs |
havne-core_0.8.0_amd64.deb (Debian, Ubuntu) or havne-core-0.8.0-linux-x86_64.tar.gz |
Linux (64-bit ARM): havne-cli and core alone |
havne-core_0.8.0_arm64.deb (Raspberry Pi OS, Debian, Ubuntu) or havne-core-0.8.0-linux-aarch64.tar.gz |
| Python wheel (Windows x64, Linux x86_64 and arm64, macOS arm64 13+) | pip install havne-0.8.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.8.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. - Press Demo data on Home, then 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.8.0-linux-x86_64.AppImage, or on 64-bit ARM (a Raspberry Pi 3 or later on a 64-bit system)havne-0.8.0-linux-aarch64.AppImage. chmod +xit, then run it.- Press Demo data on Home, then 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.8.0_amd64.deb (./havne-core_0.8.0_arm64.deb on ARM), or unpack havne-core-0.8.0-linux-x86_64.tar.gz (havne-core-0.8.0-linux-aarch64.tar.gz) anywhere.
Android 12 or later (64-bit ARM)
- On the phone, download
havne-0.8.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. On Dash, press the Demo data row, then 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.7.4
Conditions and alerts
- A condition file is a set of named tests of a session: a signal above or below a level (with hysteresis and a hold), the link's state, or one of the frames check's findings, joined by
allorany, each marked for an alert, a recording or a marker. Conditions are judged on the frames' own time, so the same recording replayed gives the same events at any speed, and one whose input has gone stale says so (docs/condition-files.md, ADR-0063). - Settings, Alerts adds, edits, switches off and removes alerts on the session's signals and its link, with levels typed in your units, and imports and exports a condition file. A gauge's panel makes an alert from its own danger or warning levels.
- A banner under the header on every page, and over the gauges in the drive view, shows the highest alert with the value it fired at; a gauge or Live value an alert reads takes the alert's color. On Android an alert can play a short tone (one beep for a warning, two for a danger) at the alarm volume, so it sounds with the phone on silent.
- Armed recording: the Armed button beside Start log (and in the drive view) records nothing until a condition set to record fires, then writes a folder for each window, from the condition's
beforeto itsafter.havne-cli log --conditions <file> --armedand Python'sRecorder(armed=True)do the same. - A recording keeps its session's conditions, and the viewer draws each time one was ON as a bar along the chart's foot, with a Conditions... list beside Stretches... that moves the view to one.
havne-cli conditions checksays what a condition file holds and why it is refused,havne-cli stream --conditionswrites a line at each change, and Python hasConditionSet,Session.set_conditions()andRecordedConditions.schema/condition-file.schema.jsonis the format's JSON Schema.
One plugin store
- Settings, Signals is one list of plugins: every signal set on the device is a plugin there, each variant a row a press picks for the vehicle, and the vehicle's own plugins come first under "For this car:". One Import... takes a plugin package, a signal file (as a new plugin or into one of your own) or an OBDb set (ADR-0064).
- At the first start after the update, the vehicles' signal files move into the store, each as a plugin of your own picked for the vehicles that had it; one that could not move is listed with why. Add a signal saves into the vehicle's own plugin, and renaming a signal keeps the Dashboard gauges and layouts that show it.
- More on a row saves a variant as a signal file, exports a plugin, copies it to your own, or marks an imported one as yours so a newer export updates it in place.
havne-cli plugins wrap,putanddropand Python'sPlugin.wrapmake and change packed plugins.
Signals and requests
- Signal files in format 2 compute with functions, comparisons and a conditional, give a stale input as no value, and read other computed signals up to 8 deep, as
examples/boost-ratio.jsondoes (ADR-0062). - A set may derive up to 1024 requests, so an OBDb import of a whole car's set keeps its signals. The app asks a session's ranked signals, the Dashboard's gauges and the rows ticked on Live, not every signal of a large set; the rest read "Not asked" until a tick asks them (ADR-0051, ADR-0056).
- A connected car is recognized as soon as it answers its VIN. The minimum time between sweeps paces Live and the Dashboard too, and J2534 sessions pace their requests by the replies.
- The Log page is now Activity, so "log" names only a recording.
Fixes
- On Android, a save that fails or is refused leaves nothing behind and never removes a document you chose to replace; a CSV save can replace a CSV file.
- Opening a recording with a long events log can be canceled at once, and a rare crash in Qt 6.12's step-by-step script memory cleanup is avoided.
havne-cliexits 1 when it can't write a refusal. 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. Dev's CI run 43783701411 passed on this release's tree, and the release pull request's run on this release's commit gates the tag.
- Locally the full verify at dev's tip passed 2711 of 2711 tests; the skipped cases are the ones gated on what a Windows machine lacks (Linux, Wireshark's
tshark, the car's raw recordings) or that the cross-arch step runs, and the cross-arch (x86) step passed 111 of 111. - Conditions have run against the simulated car (
mock://) and recordings only; the ...
Havne v0.7.4
Havne 0.7.4 follows up the Dashboard and the viewer: a layout saved to a file and loaded back, more gauge colors, steady trends on the Dashboard and Live's chart, every plugin variant offered for a vehicle, Compare's difference trace, the demo car under obd2, and Android's own document picker. Read DISCLAIMER.md before connecting it to a vehicle.
Downloads
| For | Download |
|---|---|
| Windows (x64) | havne-0.7.4-windows-x64.zip |
| Linux (x86_64), the app | havne-0.7.4-linux-x86_64.AppImage |
| Linux (64-bit ARM: a Raspberry Pi 3 or later), the app | havne-0.7.4-linux-aarch64.AppImage |
| Android 12 or later (64-bit ARM) | havne-0.7.4-android-arm64-v8a.apk |
Linux (x86_64): havne-cli and core alone, for your own programs |
havne-core_0.7.4_amd64.deb (Debian, Ubuntu) or havne-core-0.7.4-linux-x86_64.tar.gz |
Linux (64-bit ARM): havne-cli and core alone |
havne-core_0.7.4_arm64.deb (Raspberry Pi OS, Debian, Ubuntu) or havne-core-0.7.4-linux-aarch64.tar.gz |
| Python wheel (Windows x64, Linux x86_64 and arm64, macOS arm64 13+) | pip install havne-0.7.4-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.4-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. - Press Demo data on Home, then 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.4-linux-x86_64.AppImage, or on 64-bit ARM (a Raspberry Pi 3 or later on a 64-bit system)havne-0.7.4-linux-aarch64.AppImage. chmod +xit, then run it.- Press Demo data on Home, then 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.4_amd64.deb (./havne-core_0.7.4_arm64.deb on ARM), or unpack havne-core-0.7.4-linux-x86_64.tar.gz (havne-core-0.7.4-linux-aarch64.tar.gz) anywhere.
Android 12 or later (64-bit ARM)
- On the phone, download
havne-0.7.4-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. On Dash, press the Demo data row, then 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.7.3
Live and the Dashboard
- A layout in a file: Export layout and Load layout on Dash's Page row save a page's gauges to a file and load them back. The phone's and the desktop's layouts stay apart, never scaled into each other, and a load says which of the signal files the layout reads this vehicle lacks.
havne-cli layout check <file>checks a layout file with no app (ADR-0057). - Five more gauge colors (red, blue, yellow, green and light blue; the green before them is Light green), or one of your own from red, green and blue under Custom... in the panel's Color row.
- Steady trends: the Dashboard's sparkline and Number tile keep their trace while you visit another page, Settings or Live, and a short spike (lambda through a fuel cut) keeps its height and its place as the trace scrolls. Live's chart holds still as it scrolls: a signal that swings keeps its shape from frame to frame, a trace's scale widens at once and narrows only when the trace has shrunk well inside it, and the plot keeps its width when a value gains a digit or a minus sign.
- On a phone, a gauge's panel gives its size as Columns and Height, both in columns.
The viewer
- Compare's Difference switch draws, for each plotted signal both recordings hold under one name and unit, the compared recording's value less this one's in a pane of its own (ADR-0056).
- The chart keeps its detail further out: it reads samples or per-second summaries by the signals plotted, so two short logs lined up on a pull draw sharp from the start.
- Closing a recording stops its pull and cruise search where it is and doesn't wait for a span's statistics. On a phone, the pane seams and the chart's splitter take a touch anywhere within a finger's width.
Vehicles, plugins and the demo
- Every imported plugin's variants are offered on Settings' Signals page for the picked vehicle, its VIN known or not. The variants a VIN covers come first and stay marked with the vehicle after the session ends; nothing asks for a VIN, and nothing is picked for you (ADR-0052).
- The demo car answers OBD-II under the
obd2profile from its drive cycle, so theobd2Dashboard, Boost included, shows values with no car;havne-cli sim's simulated car answers the same PIDs (ADR-0039). - A car whose supported-PID list ends early shows the signals past its end as not sent, and
mock://gives each ECU a signal file or plugin reads a channel of its own.
Android
- Android's own document picker opens Load layout, Import a log, a column map, a signal file, an OBDb set and a plugin, and reads the file picked, a name with parentheses ("name (1).json") included. An export to a name already taken writes the "(1)" document, a folder export through the picker works, and a save that is refused or fails removes only the empty document the picker made.
- Paired headsets, watches and health devices sit under Other paired devices, not among the adapters. In developer mode the display line gives the phone's form and orientation alone, never its size.
Accessibility, Python and the C API
- With a screen reader on, Live's rows and the Log's By ID list read as one item each.
- Python's
Recording.stretches,find_thresholdandfind_markerstop at Ctrl+C and takecancel=; the C API addsecuio_recording_stretches_withandecuio_recording_find_with.havne-cli viewends at Ctrl+C with the interrupted end line.
Fixes: SocketCAN's close waits for a read under way before it returns each module to the default session (ADR-0060), a drag after pressing Live, the Stretches panel's levels across a change of units and under a comma locale, a frame table's place, an import's words over the next recording, a recording row's signal count, a short CSV's column map, havne-cli export --rows saying when an interval thins nothing, a relay that can't start, and keepalive_ms across a change of address kind. CHANGELOG.md lists each.
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. Dev's CI run 43620355468 passed on this release's tree, and the release pull request's run on this release's commit gates the tag.
- Locally the full verify at dev's tip passed 2232 of 2232 tests; the skipped cases are the ones gated on what a Windows machine lacks (Linux, Wireshark's
tshark, the car's raw recordings) or that the cross-arch step runs, and the cross-arch (x86) step passed 108 of 108. - On a phone: the release APK of v0.7.4-rc1 on the test phone (Android 16) under
mock://demo: Live's chart through the demo's rev-limiter pulls, its bands holding their edges as they scroll; the Dashboard's trends across page switches; two layout exports under one name, the second "(1)", and each loaded back, a cancel changing nothing; the signal file, OBDb and plugin imports refusing a layo...
Havne v0.7.3
Havne 0.7.3 is for reading your recordings: the viewer's chart in panes with two cursors and a span's statistics, a Jump row between a recording's pulls and cruises, Live's pause, and first-run words that find the way without the guide. Read DISCLAIMER.md before connecting it to a vehicle.
Downloads
| For | Download |
|---|---|
| Windows (x64) | havne-0.7.3-windows-x64.zip |
| Linux (x86_64), the app | havne-0.7.3-linux-x86_64.AppImage |
| Linux (64-bit ARM: a Raspberry Pi 3 or later), the app | havne-0.7.3-linux-aarch64.AppImage |
| Android 12 or later (64-bit ARM) | havne-0.7.3-android-arm64-v8a.apk |
Linux (x86_64): havne-cli and core alone, for your own programs |
havne-core_0.7.3_amd64.deb (Debian, Ubuntu) or havne-core-0.7.3-linux-x86_64.tar.gz |
Linux (64-bit ARM): havne-cli and core alone |
havne-core_0.7.3_arm64.deb (Raspberry Pi OS, Debian, Ubuntu) or havne-core-0.7.3-linux-aarch64.tar.gz |
| Python wheel (Windows x64, Linux x86_64 and arm64, macOS arm64 13+) | pip install havne-0.7.3-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.3-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. - Press Demo data on Home, then 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.3-linux-x86_64.AppImage, or on 64-bit ARM (a Raspberry Pi 3 or later on a 64-bit system)havne-0.7.3-linux-aarch64.AppImage. chmod +xit, then run it.- Press Demo data on Home, then 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.3_amd64.deb (./havne-core_0.7.3_arm64.deb on ARM), or unpack havne-core-0.7.3-linux-x86_64.tar.gz (havne-core-0.7.3-linux-aarch64.tar.gz) anywhere.
Android 12 or later (64-bit ARM)
- On the phone, download
havne-0.7.3-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. On Dash, press the Demo data row, then 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.7.2
The viewer
- The chart is in panes, one for each unit, stacked on one time axis, each with its own axis. A pane's range zooms with Ctrl and the wheel or a vertical pinch, and a drag on its axis pans it; dragging the line between two panes sets their heights (ADR-0061).
- A second cursor (Shift+click, or a long press) shows the span between the two: its length, and each signal's change, lowest, highest, mean and rate. On a phone the title row and the chart stay put while one list scrolls under them.
- A Jump row steps between a recording's pulls and cruises, with each drawn as a band on the chart. Stretches... sets the levels that make one; the app and
havne-clifind pulls as road logs drive them (ADR-0056). - Compare lines two recordings up on a pull you choose in each. It is a button beside Export.
- A recording opens with at most four signals plotted, and a trace keeps its own color.
Live and the Dashboard
- Live's pause: drag the chart to look back through the last two minutes while the values keep updating; Live (or Space) follows now again.
- Change a gauge's kind and pick its color in its panel; gauges warn below a level as well as above one, and a new gauge on a common signal starts with zones for a gasoline engine. The panel shows the gauge it edits.
- The demo vehicle is turbocharged, with boost that builds and vents, and says which signals it never sends.
Finding your way
- The Demo data row and the Log's raw frames are there for everyone, no Developer mode. Mark stands beside Stop log, and Live says what a log records.
- Settings says why a page is dim while a session runs, what Record sessions keeps and what a vehicle is for; Connection has an Extended session box.
- On a phone the status reads Connected, a connect from Other address... returns to the page that sent it, and Profile is three segments.
Recordings and import
- A recording's row says how long it is, whether it is a log or a whole session, and its marks. Import takes a label, opens its recording, and can be canceled; on Android its picker offers every file.
- A CSV with padded cells, a bare numeric time or rows with no time imports as the file means it, and a wide export no longer lets a sparse column set the pace (ADR-0054).
Signals, the extended session and the C API
- A signal file may replace one of OBD-II's signals by name, and OBD-II reads Boost. A signal set that repeats a name is refused, and a computed signal's input a file turns into text is named.
- The extended session's close waits for the module, so it is returned to the default session (ADR-0060).
havne-cli viewtakes--spanand--stretchesand aligns on a chosen pull with each column's mean and delta; Python'sRecordinghasstats,step,role_signalandstretches, and looks up a VIN and a trouble code offline. The C API addsecuio_recording_stats,_step,_stretchesand_role_signal.
Fixes: the Dashboard after Reset, a connect list's two recents on one adapter, Live's Space key, the viewer's keys and cursor handle, an aligned view's columns and the axis's end, a second Ctrl+C after a finished export, and more. CHANGELOG.md lists each.
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. The release pull request's run on this release's commit gates the tag.
- Locally the full verify at dev's tip passed 2147 of 2147 tests; the skipped cases are the ones gated on what a Windows machine lacks (Linux, Wireshark's
tshark, the car's raw recordings) or that the cross-arch step runs, and the cross-arch (x86) step passed 108 of 108. - On a phone: development builds on the test phone (Android 16) under
mock://: Live's pause, the viewer's panes, cursors and statistics, and the Dashboard at phone width in four looks, then a build from dev's tip with CI's APK: the import picker offered a CSV, its format and column map were guessed, "Imported 25 values" and the recording opened in the viewer, and the viewer's Jump row and Stretches panel fit the phone's width. An import canceled on the phone left no recording, though its note wasn't caught on screen. The first-run words and the other Recordings changes have not been looked at on a phone, and the release APK itself has not been run. - On a car: the extended session ran parked on the test car through two adapters (2026-11-11-ext-session-car): entered, read in and held by tester present. The closes were changed afterward and are tested against the fakes only; a car run of them is planned. The pull rules were tuned against five road logs of one car read through a logger, not a live session.
- Not yet run: the published downloads haven't connected to an adapter or a car, and the iPhone app has not run on a device.
Verifying the downloads
SHA256SUMS.txt holds every download's SHA-256, the debug file...
Havne v0.7.2
Havne 0.7.2 is for building your own Dashboard and scripting your recordings: the desktop's gauges on one panel with undo, a Light look for sun, a signal file's dial range and warning levels, Python's exports and health report, and a user guide. Read DISCLAIMER.md before connecting it to a vehicle.
Downloads
| For | Download |
|---|---|
| Windows (x64) | havne-0.7.2-windows-x64.zip |
| Linux (x86_64), the app | havne-0.7.2-linux-x86_64.AppImage |
| Linux (64-bit ARM: a Raspberry Pi 3 or later), the app | havne-0.7.2-linux-aarch64.AppImage |
| Android 12 or later (64-bit ARM) | havne-0.7.2-android-arm64-v8a.apk |
Linux (x86_64): havne-cli and core alone, for your own programs |
havne-core_0.7.2_amd64.deb (Debian, Ubuntu) or havne-core-0.7.2-linux-x86_64.tar.gz |
Linux (64-bit ARM): havne-cli and core alone |
havne-core_0.7.2_arm64.deb (Raspberry Pi OS, Debian, Ubuntu) or havne-core-0.7.2-linux-aarch64.tar.gz |
| Python wheel (Windows x64, Linux x86_64 and arm64, macOS arm64 13+) | pip install havne-0.7.2-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.2-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.2-linux-x86_64.AppImage, or on 64-bit ARM (a Raspberry Pi 3 or later on a 64-bit system)havne-0.7.2-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.2_amd64.deb (./havne-core_0.7.2_arm64.deb on ARM), or unpack havne-core-0.7.2-linux-x86_64.tar.gz (havne-core-0.7.2-linux-aarch64.tar.gz) anywhere.
Android 12 or later (64-bit ARM)
- On the phone, download
havne-0.7.2-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.7.1
The Dashboard
- The desktop's gauges sit on one panel, with hairlines between them as on the phone, and a short gauge fills the empty space under it. The pages are tabs on the panel's upper edge, with a "+" tab in edit mode, and a long row of tabs scrolls sideways, by the wheel too (ADR-0057).
- Undo and Redo in edit mode, at the start of the bar, back to the first change since Edit (at most 50 steps). On the desktop Ctrl+Z undoes and Ctrl+Shift+Z or Ctrl+Y redoes, in edit mode or out of it. A change made from a gauge's panel outside edit mode shows a line for 5 seconds with Undo. A run of steps on one control, a stepper held or a switch flipped, is one Undo.
- A gauge's panel (a long press, or a tap in edit mode) has Remove, and Undo brings the gauge back. Edit mode's remove box draws as a button and stays inside a short cell such as the shift lights.
- A gauge whose value has stopped updating says "no new data" beside its dimmed value. The Number gauge has no status dot; it dims and says so, as every other kind does.
- The built-in layouts show Boost, Lambda and Battery in place of Throttle and Engine load. Boost reads on the demo (
mock://); OBD-II gives no boost value of its own, so on a car the Boost gauge waits for a signal file or a later release that computes it. A layout you've edited keeps its gauges. - Paste is in the "+" cell, beside the "+" while a gauge is copied, and no longer on the bar. Done is at the bar's end, and on a narrow screen Add gauge reads "Add". Edit mode's "Pages" button reads "Page".
- The demo connection reads a battery voltage: about 12.45 V with the key on, a dip while the engine cranks, and the alternator's 14.1-14.6 V once it runs. A Dashboard gauge added for Battery Voltage on the demo or on an OBD-II connection reads on the other too. A battery gauge added before 0.7.2 reads only on the connection it was added on, until its signal is chosen again.
- Holding a gauge opens its menu even when the finger drifts a little while it's held, as a thumb or a finger on a phone in a holder does.
The look
- A Light look, dark text on white for reading the screen in sun, chosen on Settings' Display page. Night still shows over it when it's on, and on Android the status and navigation bar icons turn dark to match (ADR-0058).
- A button that can't be pressed yet, such as Connect while it connects, draws as a dimmed ordinary button in every look, not as a gray block. At night, the red Clear codes buttons on Diagnostics keep their words readable.
On the phone, and the desktop's first screen
- The drive view's gauges fill the screen, and a tap brings the controls up from the bottom with the tab bar, leaving the top row and the status line in view. Start log, Stop log, Mark and Disconnect are there too (ADR-0059).
- Dash's connect list on a phone, and the desktop's Home, which is the same list, show your paired and plugged-in adapters beside the recent addresses, so a first connect takes a tap or two. On a phone, Bluetooth's permission is asked only when you tap Allow there.
- Home on the desktop shows the session once connected, with Dashboard and Disconnect. Its tachometer sweeps once when Home first shows, and stops while Home is hidden or the app is in the background.
- A Log row at the end of Settings' list shows the newest activity line and opens the Log. A connect that fails, on Dash's list or in Settings, offers Show log beside its words. The Log page has a back arrow, and in developer mode its Activity | Frames switch sits under the title so the row fits a narrow screen.
- On Recordings, the signal list stops at five rows, so a swipe above or below it scrolls the page.
Recordings
- The viewer opens onto a recording's chart and signals; what applies to the whole recording (its info, Replay and Save report, the decode choice, the baseline, Compare and the frames check) follows under an "About this recording" heading. Maximized, its side view follows the Values | Frames switch: Frames gives the frames table the page, Values the chart.
- The Export panel has a Cancel button while an export runs: it stops at once and leaves nothing half written.
- Quitting during an import, or while the log viewer writes a health report, no longer waits for it to finish: it stops, and nothing half made is left.
havne-cli import, andhavne-cli healthover a recording, stop cleanly on Ctrl+C, andhavne-cli export,importandhealthover a recording end at once on a second Ctrl+C, with the interrupted end line and exit 1. - A Save report or an export on a phone that fails, is stopped or can't start no longer leaves an empty document where you picked it, and a temporary folder an import or a report left behind is removed at the next start, as an export's was.
havne-cli logno longer ends a short replay with a values count of 0 (or short) in its end line; the recording itself was always whole.
Signal files, Python and the C API
- A signal file can give a signal a gauge: its range and its low and high warning levels, in the signal's own unit.
havne-cliand the Python package report it; the app's dials don't read it yet. A...
Havne v0.7.1
Havne 0.7.1 is for the phone in the car: a drive view that shows your gauges to the screen's edges with every bar hidden, Night as a one-tap switch in amber or red, a flatter look in Barlow type, and the Recordings viewer's Export, which saves a whole recording scrubbed through the system's pickers. Read DISCLAIMER.md before connecting it to a vehicle.
Downloads
| For | Download |
|---|---|
| Windows (x64) | havne-0.7.1-windows-x64.zip |
| Linux (x86_64), the app | havne-0.7.1-linux-x86_64.AppImage |
| Linux (64-bit ARM: a Raspberry Pi 3 or later), the app | havne-0.7.1-linux-aarch64.AppImage |
| Android 12 or later (64-bit ARM) | havne-0.7.1-android-arm64-v8a.apk |
Linux (x86_64): havne-cli and core alone, for your own programs |
havne-core_0.7.1_amd64.deb (Debian, Ubuntu) or havne-core-0.7.1-linux-x86_64.tar.gz |
Linux (64-bit ARM): havne-cli and core alone |
havne-core_0.7.1_arm64.deb (Raspberry Pi OS, Debian, Ubuntu) or havne-core-0.7.1-linux-aarch64.tar.gz |
| Python wheel (Windows x64, Linux x86_64 and arm64, macOS arm64 13+) | pip install havne-0.7.1-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.1-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.1-linux-x86_64.AppImage, or on 64-bit ARM (a Raspberry Pi 3 or later on a 64-bit system)havne-0.7.1-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.1_amd64.deb (./havne-core_0.7.1_arm64.deb on ARM), or unpack havne-core-0.7.1-linux-x86_64.tar.gz (havne-core-0.7.1-linux-aarch64.tar.gz) anywhere.
Android 12 or later (64-bit ARM)
- On the phone, download
havne-0.7.1-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. It opens on Dash: with no session, Dash lists the addresses that connected before, or Connect... opens Settings. In Settings, tick Developer mode under Advanced, then press the
mock://demopreset on Connection and Connect. Back on Dash, Drive shows the gauges full screen; a tap brings the controls back.
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.7.0
On the phone
- A drive view. Drive on the Dash page shows the gauges to the screen's edges, with the system's bars hidden and a one-line status. A tap brings the controls back for 2, 4 or 8 s, or until tapped away, as set under Settings, Display, where Android also sets which way the view holds the screen. It keeps the screen on, and comes back by itself the next time a session connects on Dash (ADR-0059).
- The tab bar has five labeled tabs: Dash, Live, Codes, Recs and Settings. Tap the status in the top bar for the Log. With no session, Dash lists the last five addresses that connected, replays and the demo left out, ready to connect.
- The Dashboard is laid out on 6 columns upright and 12 on its side, its gauges one flat panel with thin lines between the cells, and a gauge shorter than its neighbor fills the empty space under it. A layout you have already edited keeps its shape. Its tools share one row (Drive, Reset peaks, Edit and the Night switch), and the tab bar and top bar take the place of the page's title and link line.
- Android's Back reaches the app: it closes a Settings page, closes an open recording to the list, closes a Dashboard gauge's panel and then edit mode, and returns from the Log, or from Connection opened through Other address... or by a refused Replay, to where it came from. The screen stays on while connected, on external power or with Dash showing.
- Settings' title row stays while a page scrolls, with a back arrow at its left.
- With an accessibility service on, such as a screen reader or a password manager, Havne could stop answering for minutes after you left the Dashboard and came back during a session. Each gauge now reads as one line, its name, value and unit.
Night, and the look
- Night (Off, On or Scheduled) and a Night style (Amber or Red), under Settings, Display, in place of the Low glare and Night themes; a stored theme carries over. The Dashboard has a one-tap Night switch that, under a schedule, holds the opposite until the schedule's next boundary (ADR-0058).
- Neutral graphite with a light accent, squarer corners, flat gauge cards and Barlow type, with fixed-width digits for readings. Dials have no bezel and draw larger; needles, bars and traces are one flat color. Buttons have four ranks, and text fields and check boxes share one look; on a phone they and the Recordings page's controls are a touch's size. Blue appears only where it means cold, and one vocabulary runs through the app: "address", "Disconnect" and "No session".
Dashboard editing
- Press and hold a gauge, in or out of edit mode: let go for its menu (signal, size, Copy, Paste after), or move to drag it to a new place. Gauges copy and paste across pages, and a blank cell in Add holds a spot open (ADR-0057).
- A tall Digits gauge puts its unit under larger, centered digits, and takes its digit count from its range unless one is set.
Recordings and the analysis log
- Export in the Recordings viewer saves the whole recording as a CSV (wide or long), pcapng or a folder copy, scrubbed, with the file's size shown beside each row interval before anything is written, through the system's file and folder pickers (ADR-0056).
havne-cli export --format csv --estimateprints the rows and bytes without writing a file. - Replay connects in one tap and lands on Live, or on Settings with the reason when core refuses the recording. It reads "Disconnect to replay" while connected and "Stop the relay to replay" while the relay runs.
- The analysis log takes a minimum time between sweeps, for a slow adapter or a busy ECU: Settings' Advanced page,
havne-cli log --min-sweep <ms>and Python'sset_focus(signals, min_sweep_ms=...). - Quitting the app during a long export, or Android closing it, stops the export and leaves nothing half written;
havne-cli exportstops cleanly on Ctrl+C.
The extended session, for uds-generic
- Add
?session=03to the address and Havne asks each module to enter the extended diagnostic session before reading, keeps it there while it reads, and returns it to the default session at the end. A module that refuses is read in the default session, and the Log page,havne-cli'ssessionline and Python say which session each module was read in. Nothing but reads and the session's own requests is sent in it (ADR-0060).
For programs
- Append-only additions to the C ABI:
ecuio_session_set_focus_with,ECUIO_SESSION_INFO_REQUESTS,ecuio_export_withandecuio_export_estimate_with(an export and its sizing that a cancel can stop), and the session fields ofecuio_channel_support_t. A CMake consumer that uses them asks forfind_package(ecuio 0.7.1). - Python's
havne.Pluginloads a packed plugin file; it...
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-wind...
Havne v0.6.0
Havne 0.6.0 is for people who script and share: everything it reads reaches havne-cli and Python as well as the app, a recording goes out as a scrubbed pcapng, CSV or folder copy with the car's identity left out and checked, a car's health is one file to hand to a shop or a buyer, and a simulated car answers as an ELM327 adapter so other tools read it with no car. Read DISCLAIMER.md before connecting it to a vehicle.
Downloads
| For | Download |
|---|---|
| Windows (x64) | havne-0.6.0-windows-x64.zip |
| Linux (x86_64), the app | havne-0.6.0-linux-x86_64.AppImage |
| Linux (64-bit ARM: a Raspberry Pi 3 or later), the app | havne-0.6.0-linux-aarch64.AppImage |
| Android 12 or later (64-bit ARM) | havne-0.6.0-android-arm64-v8a.apk |
Linux (x86_64): havne-cli and core alone, for your own programs |
havne-core_0.6.0_amd64.deb (Debian, Ubuntu) or havne-core-0.6.0-linux-x86_64.tar.gz |
Linux (64-bit ARM): havne-cli and core alone |
havne-core_0.6.0_arm64.deb (Raspberry Pi OS, Debian, Ubuntu) or havne-core-0.6.0-linux-aarch64.tar.gz |
| Python wheel (Windows x64, Linux x86_64 and arm64, macOS arm64 13+) | pip install havne-0.6.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). GitHub adds the source code archives.
Try it
Windows
- Download
havne-0.6.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.6.0-linux-x86_64.AppImage, or on 64-bit ARM (a Raspberry Pi 3 or later on a 64-bit system)havne-0.6.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.6.0_amd64.deb (./havne-core_0.6.0_arm64.deb on ARM), or unpack havne-core-0.6.0-linux-x86_64.tar.gz (havne-core-0.6.0-linux-aarch64.tar.gz) anywhere.
Android 12 or later (64-bit ARM)
- On the phone, download
havne-0.6.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.5.1
Python
- The
havnepackage: sessions on every transport, their frames and decoded values read as iterators, recordings, the simulated ECU, a script's own signals and a plugin's variants, over core's shared library through ctypes, with no compiler at install time (ADR-0053). - A wheel for each platform: Windows x64, Linux x86_64 and 64-bit ARM, and macOS on Apple silicon (13 or later), with core's library inside (and on Windows the J2534 helpers), for Python 3.11 or later:
pip install havne-0.6.0-py3-none-<platform>.whl. - Examples you can run with no car (
python/examples/):read_pids.pyon any session,did_scan.pylisting the identifiers an ECU answers,isotp_fuzz.pysending malformed ISO-TP exchanges to the simulated ECU on a Linux virtual CAN bus (and refusing any real interface), and a notebook predicting fuel cut from a synthetic recording.
Sharing a recording, scrubbed
havne-cli exportwrites a recording as pcapng for Wireshark (its ISO-TP reassembled by Wireshark's own dissector), as CSV of its values for a spreadsheet, pandas or R, or as a copy of its folder that Havne opens, views and replays like the original.- Scrubbed unless
--raw: identification replies (Service 09, the F180-F1FF DIDs) on any CAN ID and in either addressing layout, and text signals, are left out and counted; then every message, segments joined on any ID, and the file itself are searched for the car's identity values and anything shaped like a VIN, and a match writes nothing. A failed export leaves nothing behind (ADR-0054). - The Log page's frame table (developer mode) filters by ID, bytes, direction and flag, lists one row per ID with its rate, and Export CSV writes what it shows through the same scrub.
A car's health in one file
havne-cli health, and Save report on Diagnostics and in the log viewer, write the vehicle from its VIN (never the VIN itself), the emissions inspection's verdict, each ECU's readiness, trouble codes with titles, freeze frame, the values since the codes were cleared and the key values, as JSON or text, from a live session (reads only) or a recording, checked for the car's identity before it's written.
Imports and a baseline
havne-cli import candumpreads acandump -Llog into a recording;havne-cli import csvreads another logger's CSV by a column map. Both open in the viewer and throughreplay://, and Python has both.- A vehicle's baseline recording: kept from the Recordings page, it overlays a new run lined up on their engine starts, and
havne-cli view --align-on engine-startdoes the same.
The simulated car, as an adapter
havne-cli sim <uri> --elm327 tcp:<port>serves the simulated car as an ELM327 adapter on a TCP port: Havne's ownelm327://127.0.0.1:<port>, python-OBD and ELM327 apps that take a WiFi adapter's address read it (ADR-0055).
More
havne-cli clear <uri> --yesclears trouble codes from a script through the app's own gate (engine stopped unless you say otherwise), reporting what each ECU did.- The viewer and
havne-cli view --framesdecode a recording's frames through a profile, so a raw recording has values to plot. Settings imports an OBDb signal set for a vehicle. JSON Schemas for signal files and plugins let an editor check a file as you write it.
For programs that use core
- Core builds as a shared library (
ecuio.dll,libecuio.so,libecuio.dylib) exporting the C API and nothing else, withecuio_version; the pull queue (ecuio/queue.h) reads a session's frames or values from a thread of your own. The C ABI grows append-only (a minor release, ADR-0048).
Fixes
havne-cliexits with a failure when its output can't be written; a value that isn't a number is recorded readably on every platform; a packed Service 01 reply gives each text-decoded PID its value;signals import obdbwrites through a file of its own. 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 exports and the health report among the harnesses), clang-tidy, CodeQL and the load test; a GCC or Clang warning fails it. On Windows the suite is 1607 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. The Python package's tests run in each CI job against that job's own core, and each wheel is installed into a fresh environment and runsread_pids.pybefore the release publishes it. - The scrub against real recordings: scrubbed pcapng, CSV and folder exports of every archived real-car, bench and phone recording (159) hold none of their cars' identity values, searched whole and in pieces, as bytes and as hex; over the 245 recordings on hand, the scrub refuses none.
- Other tools: Wireshark's
tsharkreads an export and reassemb...
Havne v0.5.1
Havne 0.5.1 is a patch: a recording replays with the signal file it was recorded with, a signal its module refuses says so, and a vehicle's signal file can be saved out of the app, after a run of 0.5.0's own signals on the test car. Read DISCLAIMER.md before connecting it to a vehicle.
Downloads
| For | Download |
|---|---|
| Windows (x64) | havne-0.5.1-windows-x64.zip |
| Linux (x86_64), the app | havne-0.5.1-linux-x86_64.AppImage |
| Linux (64-bit ARM: a Raspberry Pi 3 or later), the app | havne-0.5.1-linux-aarch64.AppImage |
| Android 12 or later (64-bit ARM) | havne-0.5.1-android-arm64-v8a.apk |
Linux (x86_64): havne-cli and core alone, for your own programs |
havne-core_0.5.1_amd64.deb (Debian, Ubuntu) or havne-core-0.5.1-linux-x86_64.tar.gz |
Linux (64-bit ARM): havne-cli and core alone |
havne-core_0.5.1_arm64.deb (Raspberry Pi OS, Debian, Ubuntu) or havne-core-0.5.1-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.1-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.1-linux-x86_64.AppImage, or on 64-bit ARM (a Raspberry Pi 3 or later on a 64-bit system)havne-0.5.1-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.1_amd64.deb (./havne-core_0.5.1_arm64.deb on ARM), or unpack havne-core-0.5.1-linux-x86_64.tar.gz (havne-core-0.5.1-linux-aarch64.tar.gz) anywhere.
Android 12 or later (64-bit ARM)
- On the phone, download
havne-0.5.1-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.5.0
Your own signals, as they were recorded
- A replay decodes with its recording's own signal file: a recording holds the file it decoded with, and its replay uses that copy, in the app and in
havne-cli stream replay://, so a recording replays as it was recorded after the vehicle's file has changed or been removed, or on another machine. A copy that no longer matches its hash isn't used, and the replay says why (docs/signal-files.md). - A refused signal shows as refused, not blank: Live's row reads "Refused: requestOutOfRange (7F 22 31)", the negative reply's code by name, and
havne-cli stream --valueswrites arefusedline naming each such signal with its request, the reply and the code's name. A module that leaves PIDs out of its supported-PID bitmaps still has its refusals named, and past the eight a module's report lists, Live's status line and therefusedline say how many more it refused. A refused signal gives its place among the chart's default signals to the next. On a phone, a row too narrow for the words reads "Refused (7F 22 31)" and the name keeps its room. A replay shows no refusal: the recording keeps it only as an activity line. - Save a copy: Settings' Vehicle section saves each of a vehicle's signal files out of the app, through the desktop's save dialog or Android's document picker, byte for byte, so a file made in the form can be shared or given to
havne-cli --signals. docs/signal-files.md walks through a DID scan, Read once, the file, a recording holding it and sharing it. - The form and the vehicles: each box in the form for a vehicle's own signals has its name above it; a Request ID left empty keeps the module's, and a typed one that differs moves the module's other signals too, the note naming them. When the connected car's VIN picks another saved vehicle than the one picked, the Vehicle section says so until you pick one yourself. Picking another vehicle, or New, or the end of a session in which the VIN picked another, puts What to read back to Default when it named the last vehicle's file, and a vehicle the VIN adds keeps no other vehicle's file in its connection.
- The viewer's Replay view is Replay in Settings: it fills Settings' field with the part in view for Connect, and it's off while a session runs.
Speed
- On Windows, a session that asks waits out the request engine's 20 ms floor on a high-resolution timer instead of Windows' 15.6 ms step: against an adapter whose empty reads return at once, each module is asked about every 21 ms, from 31, however many modules. Through the OBDX Pro VX the pace stays the adapter's own, about 27 ms.
- The charts draw their traces on the GPU: on the test phone, a tap on the Recordings page's chart with every signal plotted holds the app about 50 ms instead of 150, and a drag moves the chart as it goes.
Fixes
- A plugin whose data files hold a number in its shortest 17-digit form, as Python and most tools write one, loads; it was refused. Every number a signal file, a plugin, an OBDb import or a recording holds reads as the double nearest it.
- On Windows,
havne-clitakes a path with a character outside the system's code page, so a replay, a recording,view,info, a signal file, an OBDb import and a plugin under a folder named with an accent or in Greek work. - Importing a newer version of a plugin that couldn't be kept left neither version loaded; the loaded version stays until the new one has loaded in its place.
- The full list is in the CHANGELOG.
For programs that use core
- No ABI change. A channel's support report (
ecuio_channel_support_t) lists indropped_listthe requests a negative reply refused before those the bitmaps left out, each in set order; before, all were in set order.
Known issue
- Through the OBDX Pro VX, with requests out to two modules, the second module's reply can be lost while the first's longer reply is in flight: 22% of one module's requests on the test car, 1.1% with
?pack=0on the URI, the workaround for a two-module session through the VX (STATUS.md's Known Issue #42). The OBDLink MX+ lost none.
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, and a check of the C ABI against 0.5.0's; 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 1271 cases, all passing but three that need a local build tree, the car's raw recordings or Linux, and the 102 cases of the 32-bit driver path pass through the x86 helper too.
- Against the fakes: a two-module session through the fake J2534 driver and the fake ELM327 asks each module at the engine's floor, a median of 20.6 and 20.5 ms, by the fakes' own stamps; a refused DID reads Refused on Live and in
havne-cli, through the fake on Windows and the simulated ECU on Linux. - On the test car (a development build from before this release's review fixes): a signal written in Settings' form and checked with Read once, a signal file's DIDs on two modules, a DID the module refuses shown as refused, an enumeration and boost, read through the VX over J2534 in the app and
havne-cli, and through the OBD...
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:...
Havne v0.4.1
Havne 0.4.1 is a patch: its pages fit a phone, upright or on its side, with the chart able to take the whole page, and replies through a J2534 adapter reach the session as they arrive. Read DISCLAIMER.md before connecting it to a vehicle.
Downloads
| For | Download |
|---|---|
| Windows (x64) | havne-0.4.1-windows-x64.zip |
| Linux (x86_64), the app | havne-0.4.1-linux-x86_64.AppImage |
| Android 12 or later (64-bit ARM) | havne-0.4.1-android-arm64-v8a.apk |
Linux: havne-cli and core alone, for your own programs |
havne-core_0.4.1_amd64.deb (Debian, Ubuntu) or havne-core-0.4.1-linux-x86_64.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.4.1-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, glibc 2.39 or later: Ubuntu 24.04 and newer, Debian 13, Fedora 40 and newer, Arch)
- Download
havne-0.4.1-linux-x86_64.AppImage. chmod +x havne-0.4.1-linux-x86_64.AppImage, 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.4.1_amd64.deb, or unpack havne-core-0.4.1-linux-x86_64.tar.gz anywhere.
On ARM Linux (a Raspberry Pi, aarch64) there is no download yet (0.5.0 brings them): the core and havne-cli build from source (docs/development.md), as they did on the Raspberry Pi 3 under "What's verified".
Android 12 or later (64-bit ARM)
- On the phone, download
havne-0.4.1-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.0
The pages on a phone
- Denser pages: on a phone, upright or on its side, and in a window as small, margins, spacing, buttons, the toolbar and the sidebar shrink and Live's rows are shorter, so more of each page fits at 100 %. Upright, the Dashboard's tachometer and speedometer sit side by side.
- The chart takes the page: Live's chart and the Recordings viewer's fill the page at a press of Chart, a double-click or
F, and give it back the same way; on a phone on its side they start that way. The viewer then shows the values at the cursor once you tap one, beside its chart, or below it on a page taller than wide (a phone upright), and a button folds them away and opens them again, kept between runs. A handle below Live's list, and one below the viewer's chart, sets each part's share, kept between runs. - A pinch on Live's chart, or the mouse wheel over it, steps its window: fingers spreading show less time, closing show more.
- Charts that hold still: a noisy trace's peaks stay where they are as Live scrolls and as the viewer pans, instead of shifting at every update.
- Log rows copied: the Log page's frame table copies the rows you pick, a tap or a shift-click, with Copy or
Ctrl+C(Cmd+Con a Mac), as tab-separated lines with a header. Paused, it says where new frames still go. - In developer mode, a corner badge counts the frames the window draws each second.
Listening beside another tester
- An ELM327 session that only listens (
?profile=raw) turns the adapter's flow control off, so it never answers another tester's first frame with one of its own. Through an OBDLink MX+ it hears only replies that fit in one frame (STATUS.md's Known Issue #41).
Fixes
- Through a J2534 adapter, replies reach the session as they arrive: on the OBDX Pro VX a reply that took longer than 10 ms came about 50 ms late, and the others waited out the rest of a 10 ms read. A read that fails right after frames were lost reports the failure at once, and messages a driver returns beyond those asked for count as lost.
- A tap on the viewer's chart puts the cursor on the nearest sample of the first signal plotted, with a dot on each trace at the sample its value comes from, so the value read always matches the line.
- The viewer zooms a notch per notch of a high-resolution wheel or a touchpad, a sideways scroll doesn't zoom it out, and on a phone a double-tap on a chart lands when the two taps fall a little apart, and when the viewer's chart has the page and takes a moment to draw. On a phone upright, Live's 120 s button stays on one line.
- For bench and car sessions: with
ECUIO_SUR_LOG_FRAMES=1, the J2534 session log gives each driver read its own line, with how long the driver held it (docs/j2534.md). - 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, the load test on Windows and Linux, and a check of the C ABI and its headers' declarations against 0.4.0's; a GCC or Clang warning fails it. The Android and iOS apps are cross-built there; their tests don't run on a device. On Windows the suite is 1018 cases, all passing but two that need a local build tree or the car's raw recordings, and the 101 cases of the 32-bit driver path pass through the x86 helper too.
- On Linux bare metal: an x86_64 desktop with Ubuntu 26.10 and a Raspberry Pi 3 (aarch64, Kali Linux), each building with no warnings: the whole app's suite (877 cases) on the desktop and the core's (728) on both, passing but for the locale case and the real-car recordings' diff; on
vcan0with the kernel's ISO-TP, the simulated bus's 63 cases but for the one that needs root, andhavne-cliend to end on both: a replay, the mock car played onto the bus and heard, and the simulated ECU answering anobd2session while it recorded, the recording then passinginfoandview(docs/linux.md). - Against the fakes: a J2534 read through the fake as the VX ends at its reply, 6.7 to 7.2 ms after a request answered in 4, and never asks the driver to wait 0 ms.
- One reply on two clocks: two recordings of one virtual bus line up to about 0.3 ms on one machine, and on a desk bus the VX's recording of the simulated ECU's replies against Linux's
candumpto 10.4 ms at the median, the adapter's delivery and the two clocks' offset together (2026-11-04). - On the test car (a development build from before this release's J2534 and listening changes): both of the car's ECUs in one session, through the VX over J2534, each ECU's requests waiting only for their own replies, and through the OBDLink MX+ on the test phone, taking turns; recorded by the laptop's app, the phone's and
havne-cli, each recording's check clean; the MX+ and an Innomaker USB2CAN under SocketCAN listening beside the VX, the run that found what this release changes (2026-11-04). - The VX's latency, on the test car again: through the VX over J2534 on this release's J2534 changes, the latency per request at the median is 16.4 ms with packing and 4.6 ms without, where 0.4.0's car run measured 65.5-73.7 ms packed; each driver read held a median under 1 ms (2026-11-05).
- Listening beside another tester, on the test car again: through the OBDLink MX+ on the test phone, beside the VX asking, a listening session hears Single Frame replies only. The adapter's monitor misses every frame that follow...