The Seal's ADAS re-faults on every comma boot despite the 508 spoof
running. Two prime suspects need data: (a) wrong checksum algorithm on
the spoofed 508 (camera rejects corrupt frames), (b) EPS rejecting our
790 and raising TORQUE_FAILED in stock 508 which we faithfully forward.
--verify-checksums recomputes byd_checksum against real frames per
address and prints match rates + mismatch samples.
--decode-508 histograms TORQUE_FAILED/TORQUE_TEMP_FAILED/LKSPrepare/
Cruise_Activated from stock 508 frames.
The RX table filters panda's own transmissions (bus+128), so the 508
camera-feedback spoof was invisible. Now the dump also prints the
sendcan table (proves the spoof is being sent and on which bus), a
CRUISE_STATE histogram from 813 (tells instantly if the ADAS ECU is in
failure states 8/9 or healthy), and the camera's 790 LKAS_ACTIVE ratio.
The auto-detect picked /data/media/0/realdata/boot (boot logs, no rlog).
Now scans newest-first for a dir that actually contains an rlog/qlog,
skips 'boot', and inserts repo root into sys.path so it runs from any CWD.
BYD Seal reports steering torque on 508 STEERING_TORQUE_ANGLE while the
Han uses 792 STEERING_TORQUE, and PCM_BUTTONS bus assignment is harness
dependent. This tool prints bus/addr/len/rate tables (with key BYD
addresses flagged) from either the latest recorded route (safe, no
hardware) or a live panda sniff (manager stopped).
Quintine