Skip to content

Beta v0.4.1

Choose a tag to compare

@PabloSoage PabloSoage released this 16 Oct 16:28
· 8 commits to main since this release

opendash 0.4.1 — the ELM327 bridge that a real scan tool can use

Context: one commit in opendash on top of 0.4.0, and three new profiles in
opendash-plugins. Found and fixed on 16 October 2026 against an emulated engine module
of an Opel Astra J 1.7 CDTI (A17DTJ, Denso ECU), with ScanMyOpel CAN on a phone talking
to a desk copy of the bridge that logged every byte.

Theme: the bridge passed its own self-test and every command a generic OBD app sends
first, and still ScanMyOpel CAN could not connect. It speaks a part of ELM327 the bridge
did not.

Deliverable: android-arm64-v8a-release.apk, versionCode 5, versionName 0.4.1,
minSdk 26, three languages (en/es/de). Signed with the same key as 0.4.0, so it installs
over it and keeps its data, and 0.4.0 offers it as an update.


1. The headline

ScanMyOpel CAN against the bridge 0.4.0 0.4.1
Connecting hangs up on ATBI, 46 times in a row connects
Engine module not found identified, identification read
Stored codes — listed

2. What the scan tool was asking for

With every byte logged, the session reads like this:

  • ATBI, bypass the protocol search. The bridge answered ?, which a real ELM327
    only says to a command it does not have. ScanMyOpel CAN took that as the wrong adapter,
    hung up and started again, every time. There is no search to bypass — the bus is
    known — so it is now OK.
  • ATCAF0, then whole frames. The tool turns automatic formatting off and does its
    own ISO-TP: 02 1A 9A, 03 A9 81 12, the first byte being the frame's own length.
    The bridge acknowledged ATCAF0 and ignored it, so that length byte went to the module
    as the service: 03 A9 81 12 arrived as service 03 and came back "not supported".
  • Receive filters. Before each module it sets ATCM and ATCF (or ATCRA). For
    the engine, mask 5FF over 5E8 lets both 0x7E8 and 0x5E8 through, because GM
    modules answer A9 with one stored code per frame on 0x5E8, not in a reply on
    0x7E8. A request-and-answer exchange can never show them.

3. What the bridge does now

  • ATCAF0 carries whole frames. The client's frame goes on the bus as it is, and
    every frame that passes the client's filter comes back as it arrived, until ATST
    passes with nothing more. No filter set means the addresses an answer can come back
    on, not the whole bus — on this car that is 1300 frames a second.
  • Flow control as an ELM327 does it. When a first frame arrives, the "go ahead"
    goes out by itself, to the address and with the bytes the client set with
    ATFCSH/ATFCSD/ATFCSM, or not at all after ATCFC0.
  • Headers off now answers like an ELM327. It used to print CAN frames in every
    mode. A real adapter prints the message: 41 00 98 3B 20 13 for a single frame, and
    for a longer answer its length and then numbered lines (014, 0: 49 02 …). A client
    checking that the answer to 0100 begins with 41 00 decided there was no car.
    Headers on still prints the frames, protocol byte and padding included.
  • ATBI is accepted.

4. Still reading only

The bridge goes through the same list of services as the rest of the app, in both modes,
so another app on the phone can read what this one reads and no more:

  • Two services join the list, both from what ScanMyOpel CAN sends to find and read
    modules: 0xA9, stored codes by status, a read; and 0x20, return to normal mode,
    which ends diagnostic mode and writes nothing. The most it can do is stop this app's
    own live stream if both run at once.
  • A device command from another app (AE) still needs actuation unlocked here.
    Paid actuator tests in a third-party app do not get past the bridge on their own.
  • A raw frame is checked by the service inside it. Only single frames and flow
    control are carried; a client segmenting its own request would get its service past
    the check one frame at a time, so that is refused rather than reassembled.
  • A refused request answers NO DATA and the session goes on. It used to close the
    connection.

5. The rest

  • Host tests for the bridge session, nine of them, built from the recorded ScanMyOpel
    CAN session: ATBI, both answer formats, the long-answer format, the raw exchange with
    its filter and flow control, ATCRA wildcards, a refused write in both modes, and
    ATZ putting formatting back. 44 host tests in total, all passing.
  • The Kotlin bridge is now ahead of core/src/elm327.rs. Raw mode, the filters, flow
    control and the headers-off format exist only in Kotlin. The README says so; the core
    has to catch up before it replaces it.
  • No dependency changes.

6. Upgrading

  • 0.4.0 offers this update by itself. It installs over it and keeps presets, scans
    and recordings.
  • Update the opel-vauxhall plugin for three new profiles for the Astra J A17DTJ,
    all in one round at 100 Hz: EGR (the valve in volts and percent with the
    temperatures), fuel rail (rail pressure, its target and both regulator readings in
    the same packet, with the EGR beside it), and air conditioning (high-side pressure
    next to the compressor flags, and the cooling fan).
  • To use the bridge: start it on the Link screen and point the other app at
    127.0.0.1:35000 as a Wi-Fi adapter.

Found with ScanMyOpel CAN on a phone against a logging copy of the bridge on a laptop,
over an emulated A17DTJ engine module, on 16 October 2026. Not yet run with this APK on
the phone against the car. Release APK built from the tagged commit and checked against
0.4.0's signing certificate.