From df84b1570f073b23c04f68227f8e1fef00894390 Mon Sep 17 00:00:00 2001 From: Mikkeli Date: Tue, 13 Oct 2026 16:25:38 +0900 Subject: [PATCH] CAN-BITRATE: 71-can-up matches the PEAK by USB id; NAME== never fired on hot-plug Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01DDwfd6Ki8UfG4hK6W5YpJz --- docs/impl/plans/CAN-BITRATE.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/impl/plans/CAN-BITRATE.md b/docs/impl/plans/CAN-BITRATE.md index ffd5c69..8745eeb 100644 --- a/docs/impl/plans/CAN-BITRATE.md +++ b/docs/impl/plans/CAN-BITRATE.md @@ -16,7 +16,9 @@ The OBD port is **not** gatewayed: broadcast traffic is visible passively. Persisted (boot and hot-plug): -- `/etc/udev/rules.d/71-can-up.rules`: on add of `can_pcan`, wants `can-up@can_pcan.service` +- `/etc/udev/rules.d/71-can-up.rules`: on add of the PEAK (USB 0c72:000c, matched like `70-can-names.rules`), wants + `can-up@can_pcan.service`. It first matched `NAME=="can_pcan"`, which never matches on udev 249, so hot-plug left the + interface down and the 2026-10-13 run recorded nothing. Fixed that day; check `can_pcan` is UP after the next replug. - `/etc/systemd/system/can-up@.service`: oneshot; reads `/etc/default/can-`, sets the bitrate and options, brings the interface up, and stops with the device - `/etc/default/can-can_pcan`: `BITRATE=500000`, `CAN_OPTS="restart-ms 100"`