From bb47ee5301cf5cde8a6603a75538629bc4fec944 Mon Sep 17 00:00:00 2001 From: Mikkeli Date: Tue, 13 Oct 2026 21:31:52 +0900 Subject: [PATCH] Roadmap and repos: decoder live; signal layouts in contracts' signals.json Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01DDwfd6Ki8UfG4hK6W5YpJz --- docs/REPOS.md | 2 +- docs/ROADMAP.md | 7 +++++-- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/REPOS.md b/docs/REPOS.md index 0d2fbc6..05f6bbd 100644 --- a/docs/REPOS.md +++ b/docs/REPOS.md @@ -24,7 +24,7 @@ contracts repo, not copied into each consumer. | [orin-nano-env-setup](gitea:yukart/orin-nano-env-setup) | Jetson host bring-up | | [app-flutter](gitea:yukart/app-flutter) | Flutter display client | | [contracts](gitea:yukart/contracts) | Topic namespace, payload schemas, signal registry | -| [svc-core](gitea:yukart/svc-core) | Acquisition + processing cluster: `recorder`, `orin-status`, `obd-poller` now; `can-bridge`, `gnss`, `decoder` to come | +| [svc-core](gitea:yukart/svc-core) | Acquisition + processing cluster: `recorder`, `decoder`, `orin-status`, `obd-poller` now; `can-bridge`, `gnss` to come | | [svc-gw](gitea:yukart/svc-gw) | Telemetry gateway — aggregation and the display boundary | | [svc-nav](gitea:yukart/svc-nav) | Navigation service — routing and guidance | | [svc-vision](gitea:yukart/svc-vision) | Camera: capture and the live view; recording and inference to come | diff --git a/docs/ROADMAP.md b/docs/ROADMAP.md index c96569a..9fcf36e 100644 --- a/docs/ROADMAP.md +++ b/docs/ROADMAP.md @@ -62,8 +62,11 @@ mark …`, or the app's Mark button), on the same clock as the frames. - [ ] Correlate captures against the event log; identify recurring frame IDs — prior art and first candidates (engine speed in `0x210` / `0x13D`) in contracts `docs/impl/reports/Z27AG-CAN-PRIOR-ART.md` -- [ ] Build the Z27AG DBC incrementally in `contracts` -- [ ] `decoder` — raw frames to named signals +- [ ] Build the Z27AG signal set incrementally in `contracts` — in `signals.json`'s + `can` blocks, not a hand-kept DBC (one is generated if a tool needs it) +- [x] `decoder` — raw frames to named signals, 2026-10-13: svc-core `decoder`, laid out + only by the `can` blocks in contracts `signals.json` (rpm, accelerator, brake, + handbrake, indicators, side lights, dipped beam, doors, A/C compressor) - [x] `obd-poller` — active OBD-II PIDs, single writer, 2026-10-12: mode 01, the nine `obd2` signals (~10 Hz fast, 1 Hz slow), only while the bus is alive; `can_pcan` out of listen-only. Recorded beside the frames (`vehicle.ndjson`).