Documentation · Build and flash · Dashboard · Plugins
Safety warning: CAN injection can change safety-critical vehicle behavior. This page is educational and experimental. Begin with a listen-only or isolated bench setup, never a public road. You are responsible for local law, vehicle safety, hardware isolation, and the consequences of every frame sent.
The project can observe and, when deliberately enabled, modify selected CAN frames used by hands-on-wheel or driver-assistance experiments. It does not disable the vehicle’s safety systems, prove that an ECU accepted a message, or make a vehicle autonomous.
Nag-suppression traffic belongs on Party CAN in the supported experiments. Do not assume that a connector or pinout is the same across models or build dates. Do not connect this feature to Vehicle CAN or Chassis CAN because a diagram looks similar.
Use Tesla’s Model 3 Electrical Reference or the correct service documentation for the exact vehicle to identify the bus. Verify H/L polarity, transceiver voltage, termination, and 500 kbit/s traffic with a listen-only tool before enabling any write.
Before creating or enabling a rule, confirm from captures, tests, or authoritative documentation:
Do not infer a signal from its name alone. A decimal ID and its hexadecimal form are the same ID; for example, 880 is 0x370.
Dashboard ESP32 builds keep injection blocked until CAN has initialized, the startup delay has elapsed, and more than 1,000 valid frames have arrived. Additional AP, gear, freshness, mode, and plugin gates can still block a send. Unknown or stale state must block a write.
The firmware enforces a complete 12-bit torque encoding and hard -1.80 Nm to +1.80 Nm bounds (0x74E through 0x8B6) for the built-in nag path. A plugin cannot safely be assumed to have these semantics; review its operations and target frame separately.
Dashboard builds expose the built-in path as Off plus Modes A, B, and C on Legacy/HW3. Mode A uses fixed positive torque, Mode B uses a bounded four-value burst/pause cycle, and Mode C requires fresh DAS hands-on status 0x399 and valid steering context 0x129. HW4 permits Modes A/B for Party CAN experiments; Mode C remains blocked after extended hardware testing reported red take-over plus traction-control and auto-hold faults. A stored HW4 Mode C selection fails closed to Off. These controls are direct firmware settings, not plugins, and default to Off.
Never use Last Write Check as the only safety instrument. It detects a later overwrite; it does not prove ECU acceptance or physical response.
Stop transmission and disconnect the interface. Save the Support report, serial log, board environment, local profile choices without secrets, bus wiring, bitrate, and a sanitized capture. Report exact IDs/DLCs and timestamps. Do not “fix” a mismatch by widening filters, bypassing a gate, or increasing a limit.