Decode report: reverse rechecked, gear inference dropped for a recommended gear

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DDwfd6Ki8UfG4hK6W5YpJz
2026-10-13 21:44:52 +09:00
parent 34140cc666
commit 0eab0e660e
1 changed files with 10 additions and 3 deletions
@@ -47,9 +47,16 @@ jack-stands session and a GNSS-matched drive settle both the byte order and the
 ## Not on this bus (or not seen)
 - **Clutch pedal:** nothing changed in 3 presses, engine off.
- **Gear position:** nothing in 5 gears, reverse or neutral. Expected for a manual. The
+- **Gear position:** nothing in 5 gears, reverse or neutral. Expected for a manual:
-  gear can be computed from rpm ÷ wheel speed once the scale is known.
+  nothing on the car consumes it. Not computed from rpm ÷ wheel speed either (owner's
- **Reverse:** no reverse bit found. The reverse lamp is probably wired directly.
+  call, 2026-10-13): the clutch is invisible, so the ratio lies whenever it slips or is
  down, and the gear matters most at a standstill (no 3rd-gear launch), where the ratio
  says nothing. A *recommended* gear from speed and rpm is the useful form, if any.
 - **Reverse:** rechecked against both reverse stretches (engine-off gear walk, engine-on
  back crawl) versus every other gear, neutral, the forward crawl and idle: no bit
  separates them (the one near-miss, `449.0.0`, is the low bit of a temperature). The
  reverse lamp is wired, not on this bus; a backup camera would take its trigger from
  the lamp circuit. The jack-stands run's reverse step is one more sample.
 - **Steering angle:** not analysed yet (step 5 was done with the engine on, at the end).
 ## Not analysed yet