- After the DID scan, the log page reads the 327 PCM DIDs of unknown meaning
round after round and logs every change ("W did data"), 3 per request if
the PCM allows it (reply split with the lengths from the scan)
- tools/make_watch_dids.py generates src/watch_dids.h from the scan logs
- README/CLAUDE.md: scan results, test-drive plan, git remote
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
OBD Speed (JC3636W518)
Vehicle speed from an ELM327 over BLE, shown as a big number + arc gauge on top of an animated GIF.
Uses the shared board library and LVGL 9.6 (../shared), NimBLE-Arduino 2.5.1.
Use
- Speed page — speed in km/h (
--= no data: not connected, or ignition off), arc gauge 0–200 km/h, status pill below the number (adapter name when running, otherwise what it is doing). Battery voltage (ATRV, every 2 s) as a small arc in the bottom gap (11–15 V) + number; color: red < 11.8 V, orange < 12.2 V, green < 13.0 V (resting OK), blue ≤ 14.8 V (charging), red above (overcharge). - Swipe left → adapter menu — scans while open. OBD-like adapters (name OBD/ELM/…, or service FFF0/FFE0/18F0) are listed first in green. Tap one to select it: it is remembered (NVS) and connected immediately. Forget clears the remembered adapter, Done (or swipe right) returns to the speed page.
- Swipe left again → settings — screen rotation 0 / 90 / 180 / 270 degrees, and screen off without data Off / 2 / 5 / 10 min (default 2). Both remembered in NVS.
- Swipe left once more → background —
Built-inplus every GIF in/gifson the SD card (size and dimensions shown; not 360×360 in orange). Tap one: it is copied into the device's flash (progress shown) and played from there, so the SD card is not needed afterwards. At boot the device checks (in the background) whether the chosen file on the SD card changed (size/date) and re-copies it. Rescan re-reads the card. - Swipe left once more → CAN log (temporary: diagnostic scan to find the cruise/ACC set speed and speed limit, see below).
Start/Stop (remembered: logging resumes by itself after power-up), Mark, scan progress, Reset scan,
and the file on the SD card. While logging, the speed page shows a red
REC <marks>pill and a tap on the speed page adds a mark (pill flashesMARK n). - Idle — after that time without speed data (ignition off, adapter gone) the screen goes dark, the GIF pauses and
OBD polling stops; only
ATRVevery 30 s (answered by the adapter itself, doesn't wake the car's bus). Wakes on a touch (the touch is swallowed) or by itself when the voltage rises above 13.2 V (engine started). Not used while no adapter is chosen. - On power-up the remembered adapter is connected automatically; if the link drops or the adapter is not there (car off), it retries every 3 s. With no adapter remembered, the device starts on the menu page.
How it talks to the ELM327
Service FFF0, notifications + commands on FFF1 (verified with the user's "OBDII" adapter, see
docs/2026-10-23_ble_scanner_car_test.txt, made with the BLE scanner tool that was removed afterwards — in git history); other adapters: first notify+write pair.
Init: ATZ, ATE0, ATL0, ATS0, ATH0, ATSP0, 0100; then 010D (speed) is polled continuously.
Serial (115200) prints status changes as [obd] ....
Log page: diagnostic scan (finding ACC set speed / speed sign)
Neither value is a standard OBD PID. First test drive (2026-11-02, docs/canlog): listening on the OBD port
(ELM327 ATMA, ID survey with wildcard filters) saw no broadcast frames at all, only diagnostic replies: the
Fiesta Mk8's gateway passes only diagnostics to the OBD socket. (Broadcast candidates from opendbc for newer Fords,
for reference: 0x165 Veh_V_DsplyCcSet, 0x202 Veh_V_RqCcSet, 0x3D9 IsaVLim_D_Rq; the Mk7.5 Fiesta sheet in
github.com/consp/ford-can-stuff lists 0x3CD "Traffic Recognition Data" on the infotainment bus.)
So the values have to be asked from the modules. While logging is on, the OBD task runs a read-only scan
(only UDS 22 ReadDataByIdentifier in the default session; nothing in the car is changed), progress kept in NVS
(namespace scan) so it continues on every drive:
- Unfiltered listen check (once): 2 × 5 s
ATMAwithout filter, CAF off and on. - Module discovery:
22F188(software number) to every address 0x700..0x7EF (ATSH+ATCRAaddr+8,ATST19= 100 ms timeout). Logged asD <addr> <reply>, list asI. Repeated if the PCM (0x7E0) didn't answer. - DID scan: all 65536 DIDs of each module, order 0x706 (IPMA camera), 0x764 (CCM radar), 0x720 (IPC), 0x7E0 (PCM),
then the other modules found; per module the DID ranges D000-DFFF, 4000-4FFF, 0000-3FFF, 5000-CFFF, E000-FFFF.
Positive replies
S <addr> <did> <data>, other negative responses than 0x31R <addr> <did> <nrc>. A module without service 22 (NRC 0x11) is skipped; 20 requests without a reply = module asleep: back up and wait. The<request>1suffix (return after the first reply) is used when the adapter supports it. Probe (once, after drive 2 found only the PCM):3E00TesterPresent with a 1 s timeout to every address not found yet. DIDs are asked 3 per request (22 D000 D001 D002, one CAN frame; the module returns only the supported ones) when the module passes the test22F1FFF188F1FE; a hit is re-asked one DID at a time.E progressevery 512 DIDs (with ms/DID). - Every 2 s
ATSH 7DF/ATAR+010D(speed, so the display keeps working, a bit laggy) andATRV. - Watch (once the scan is done): the 327 PCM DIDs of unknown meaning in
src/watch_dids.h(generated by../tools/make_watch_dids.pyfrom the scan logs; leaves out F1xx identification, F4xx = mode 01 copies, DExx tables, D01A text, DD00 clock, DD01 odometer) are read round after round; every change is logged asW <did> <data>, each round asE round N done, s, changes. 3 DIDs per request if the PCM allows it (tested with22D100D134D137), the reply is split with the lengths from the scan.
Scan result (2026-11-12..18, logs docs/canlog/scan, scan2): only the PCM 0x7E0 answers (also with 3E00 and a 1 s
timeout); 389 supported DIDs, ~175 ms per request, the multi-DID test 22F1FFF188F1FE timed out (single requests).
Known: F190 VIN, F188 JB2B-14C204-ADA, DD01 odometer (0x021676 = 136 822 km), F4xx = mode 01 PIDs.
Page: Start/Stop (remembered), Mark, progress (module, DID, %), modules found, DIDs found, last positive reply,
Reset scan (starts over the next time logging runs). While logging the speed page shows REC <marks>; a tap on
it adds a mark.
Log: /canlog/log_NNN.txt (new file per session, appended every 2 s; kept in RAM while the card is missing).
Lines <ms> <type> <data>: C adapter, P protocol, V speed, B voltage, M mark, D/I modules,
S/R DID replies, F raw frame, E adapter message/note.
Download over USB (no card reader needed): serial commands ls and get <file> (115200 baud).
Files
| File | What |
|---|---|
src/main.cpp |
LVGL UI (tileview: speed, adapter menu, settings, background, CAN log) |
src/obd_link.cpp/.h |
BLE scan, connect/reconnect, ELM327 init and speed polling, diagnostic scan steps (background task on core 0) |
src/font_speed_120.c |
Montserrat Medium 120 px, digits and -, 4 bpp (generated with lv_font_conv, see header) |
src/can_log.cpp/.h |
Log buffer + SD writer (background task), marks, info shown on the log page, serial ls/get |
src/sd_card.cpp/.h |
Shared, reference-counted SD_MMC mount (background store + logger) |
src/bg_store.cpp/.h |
Background GIF from the SD card: list /gifs, copy into the bggif flash partition (header written last), mmap for playback, change check at boot (background task) |
partitions.csv |
4 MB app (no OTA) + 11.9 MB bggif raw area + NVS |
docs/canlog/ |
Logs of the test drives |
data/bg.gif |
Built-in background (ezgif-5-cb56986bc7.gif, 360×360), linked into the firmware via board_build.embed_files |
sd/gifs/ |
(not in git) GIFs converted with ../tools/gif_to_360.py, ready to copy to the SD card |
GIFs for the SD card
Convert any GIF to 360×360 (scale to cover, center crop, frame timing kept) with
pip install pillow
python ../tools/gif_to_360.py <gif files or folders> -o sd/gifs
and copy the files into a folder gifs on the SD card. Max ~11.5 MB per GIF. GIFs are played from flash at their own
frame rate (360×360: ~10–12 ms decode per frame).
Replace data/bg.gif to change the built-in background.