The accel logger only exists to inform accel-eq's max-accel tuning, and accel-eq
only affects the car when OP has longitudinal control. On a stock-long car it was
pointlessly logging the driver to a CSV (with periodic flash writes) for data
that can never be applied. Skip logging entirely when not CP.openpilotLongitudinalControl.
Port min-feat/dev/fan-controller: split FanController.update() by device.
mici keeps the verbatim upstream 0.11.1 response (OFFSET == 0 there); the older
comma three / three X use the classic pre-0.11.1 curve (setpoint 75) instead of
the +5C setpoint bump, which makes them run hotter with less throttle margin.
Port the accel-eq feature onto testing:
- AccelEq (accel_eq.py): tunable max-accel curve read from the
dp_lon_accel_profiles param (validated, stock fallback, mtime-gated,
personality-linked), feeding the accel clip.
- AccelLogger (accel_logger.py): logs clean human-acceleration samples to
/realdata/accel_log.csv.
- Wired both into the ACM/AEM/APM longitudinal planner.
- Feature README at dragonpilot/accel-eq.md.
params_keys.h is generated from the settings entry at build (not committed
here). Dashy web UI handled separately.
Rick Lan