Control
CAN first. Servo last.
This page is architecture, not a kit. Nothing here commands a vehicle today.Patent Pending.
1 · CAN bus (ideal)
Read speed, motor RPM, torque, and pedal. Command a torque or acceleration limit so the host tracks the subject curve. Drive subject-car audio from the same telemetry.
2 · Official Tesla mode
Zero BOM. Expanded Chill with discrete profiles. Every Plaid becomes a comparison tool that ends on Unlock — and sells the next Tesla.
3 · IMU fallback
Phone or external G-force when CAN is unavailable. Interim UX: countdown, floor it, profile as percent torque versus time after GO.
4 · Limit-only servo (footnote)
Does not apply throttle. Springs so the driver can still overcome it with a harder press. Concept only until certified. Not sold from this site.
5 · Pedal / bus intercept
Read the host accelerator signal and substitute a subject-limited demand. Tesla and many hosts use dual analog APP voltages in a 2:1 ratio (FMVSS 124 / ISO 26262 plausibility). Scale both channels by the same k ≤ 1 so the ratio holds, a real pedal fault still faults, and throttle cannot be applied uncommanded. Pass-through on power loss. On the bus: any vehicle network now or later, receive the frame, send a reduced one. Prefer an isolated segment. Never increase demand above the driver.
6 · Subject losses
Wheelspin of FWD and RWD subjects, gear-change torque holes, clutch slip at launch, plus optional rev limiter and turbo lag. The host still only reduces torque. Launch load in this preview already dips for the first fraction of a gear so ICE subjects do not pull like an EV.
7 · Virtual shifter and clutch
A temporary or permanent H-pattern, sequential, or DCT paddles, and an optional clutch pedal in the host footwell when the subject has a clutch. A DCT subject skips the clutch pedal; shifts are quicker. Gear and clutch position feed the subject model over CAN, a dedicated wire, Bluetooth, or Wi-Fi. Other subject accessories (boost, two-step, e-brake) are the same class of controller — not a closed list.
8 · Any layer. Not all layers.
The patent family treats model and control as OR, not AND. A product may ship one pairing. Models: g-force, engine dyno, chassis/hub dyno, hp/tq, timeslip, coast-down, subject CAN log, pedal map. Control: pedal travel, APP sensor, VCU torque request, bus frame, inverter current, pack-current limit. Closed loop on IMU, GPS, wheel speed, or motor torque is optional at any of those. One layer that actually slows the car is a complete embodiment.
9 · Clutch regimes
Not one switch. Launch at the line, shift, coast, bite, stall. Fully in is electrical neutral: motor torque ≈ 0 and regen off so the host coasts like an ICE. Friction brakes stay. Watchdog restores drive and regen. Dumping the clutch launches at the lesser of subject clutch, subject engine, and host tire μ — including wheel hop. The Tesla’s chassis is the ceiling.
10 · Simulated damage
A missed upshift pegs the limiter. A 5-to-3 money shift injures the subject model — power cut, lock-out, reset to repair. The host motors never exceed OEM limits. Video-game consequences, real longitudinal feel.
11 · E-brake and steering
Optional remote e-brake for skid and drift. Closed course only: two-step arm, then yaw from steering, throttle, foot brake, and e-brake, with ABS/TC in a drift-allowing map if the OEM permits. On the road, steering overlay is gentle weight only. Understeer and oversteer are modeled always; they are experienced only when armed.
12 · Instrument reskin
Cluster, MCU, HUD, shift lights, ambient lighting take the subject’s era: needles, redline, boost, fonts. Driven by the same rpm as the torque model. True speed and real telltales stay. Exit restores the host. A web cluster on the Tesla screen is a complete skin even if the OEM cluster is not opened.