Files

uhryniuk 4aa5da53d2 Commit tune maps and research so tunes are reachable from the phone

Removes the *.hex/maps_cache gitignore rule (explicit user call, reversing
the earlier no-redistribution stance) so the official TuneECU catalogue
maps, derived SAI/O2-delete composites, and the checksum/composition
tooling are actually available to pull up on a phone browser when using
the real TuneECU app. Also folds in tonight's KWP2000 fixes (TesterPresent
keep-alive, connect-failure cleanup, slow-init StartCommunication fix) and
the accumulated research docs.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FP2GaxS9HkUdL5sLBnjKje

2026-08-27 01:34:05 -05:00

docs

Commit tune maps and research so tunes are reachable from the phone

2026-08-27 01:34:05 -05:00

logs

Commit tune maps and research so tunes are reachable from the phone

2026-08-27 01:34:05 -05:00

research

Commit tune maps and research so tunes are reachable from the phone

2026-08-27 01:34:05 -05:00

src/tunie

Commit tune maps and research so tunes are reachable from the phone

2026-08-27 01:34:05 -05:00

tests

Add tunie: read-only KWP2000 diagnostics for Triumph Keihin ECU

2026-08-10 14:29:50 -05:00

viewer

Mark device-flag confidence honestly (SAI confirmed, O2 probable)

2026-08-11 08:16:22 -05:00

FIRST_READ.md

Commit tune maps and research so tunes are reachable from the phone

2026-08-27 01:34:05 -05:00

maps.json

Add tunie: read-only KWP2000 diagnostics for Triumph Keihin ECU

2026-08-10 14:29:50 -05:00

pyproject.toml

Add tunie: read-only KWP2000 diagnostics for Triumph Keihin ECU

2026-08-10 14:29:50 -05:00

README.md

Add tunie/docs (full context + open-source roadmap); refresh README

2026-08-11 08:21:16 -05:00

RESEARCH.md

Add tunie: read-only KWP2000 diagnostics for Triumph Keihin ECU

2026-08-10 14:29:50 -05:00

STATUS.md

Commit tune maps and research so tunes are reachable from the phone

2026-08-27 01:34:05 -05:00

README.md

tunie

Open, offline tooling for the Triumph Keihin ECU (2010 Bonneville T100, 865cc, Renesas SH7054, mechanical odometer) — a from-scratch, reverse-engineered alternative to the closed TuneECU app. Read the ECU, decode and view its fuel/ignition maps, understand the device flags, and (eventually) tune it.

Independent interoperability research on hardware I own. Contains no TuneECU source — only original code and documented findings. Proprietary map binaries are never committed (see .gitignore).

What's here

src/tunie/ — a read-only KWP2000 diagnostic tool (K-Line/FTDI or Bluetooth ELM327). Cannot write to the ECU by construction; safety.py refuses every flash service before it hits the wire. pip install -e ., then tunie info --port …. Verified frames in tests/verify_protocol.py.
viewer/tunie-viewer.html — a self-contained page (no server, no deps) that drops in a real map .hex, decrypts and unpacks it, and renders the real fuel/ignition tables with RPM/throttle axes, an A→B diff, and SAI/O2 device checkboxes. Build with viewer/build_viewer.py; download_maps.py + serve.py add a catalogue dropdown.
research/ — the reverse engineering: AES-128 seed/key (keihin_seedkey.py), and the map format — decrypt, flat-ROM unpack, table map, and validated SAI/O2 flags (reference-maps/).
docs/ — start here for the full picture.

Read the docs

docs/CONTEXT.md — everything reverse-engineered and built, with per-finding confidence levels. The one file to read.
docs/ROADMAP.md — open-sourcing plan + the technical path to actually tuning the bike + next steps + risk register.
STATUS.md, viewer/FORMAT.md, research/FINDINGS.md, research/reference-maps/{README,TABLES,DEVICES}.md — deeper per-topic writeups.

Status (short version)

Software + reverse engineering are well along and validated against real map files: the protocol, the AES seed/key, the map decryption, the flat-ROM unpack, the fuel/ignition table locations, and the SAI (confirmed) / O2 (probable) device flags. Nothing has touched the real ECU yet — first contact is blocked on wiring a cable to the Triumph diagnostic connector. The write/flash path is future work (see the roadmap).

Safety

The diagnostic tool is read-only; it can't brick the ECU.
The real risk is electrical: confirm the Triumph connector pinout before plugging any cable in (the 2010 twins don't use a standard OBD-II socket).
Device flags are not a tune on their own — disabling O2 forces open-loop and needs matching fuel enrichment. Prefer flashing a complete, matching delete map over hand-toggling a stock one. See docs/CONTEXT.md §7.