The cluster removes a module the car expects to be there. Everything it does afterwards follows from taking that job seriously.
Take the cluster out and the car notices. So it puts one back.
The factory cluster is not just a display. It is a participant. It broadcasts frames that other modules depend on, answers diagnostic requests addressed to it, and passes readings from its own sensors back onto the bus for everyone else. Pull it out and the body computer starts logging faults, EyeSight complains, and the HVAC loses information it expects to have.
So the cluster synthesizes the frames the factory unit used to send, with the correct rolling counters and checksums, at the cadence the rest of the car expects. It answers diagnostic requests addressed to the cluster, including multi-frame responses, so dealer equipment plugged into the car finds what it is looking for.
And it gives back what the factory cluster gave back: measured outside temperature, fuel level, seatbelt state, turn signals, ambient light and the odometer, transmitted in the original frames so every other module stays correct. The car cannot tell it is talking to something new.
It is easy to assume a modern car is entirely a network, and that a cluster is a screen listening to it. It is not. Several of the lamps in front of you are hard-wired: a wire runs from a switch to the cluster, and the cluster is what turns the light on. The parking brake, the lights, the high beams, the stability control. No frame, no message, no bus. Just a wire that expects something at the end of it.
So the cluster drives those lines itself, the way the factory unit did. And it reads the analog ones too. The dimmer wheel you use at night is not a bus message either, it is a voltage into the cluster, which is why the cluster reads it directly and dims its own backlight from it. Roll the wheel and the screen dims, exactly as the gauges it replaced did, with nothing to configure.
Every one of those outputs is held down until the board has authenticated itself against its secure element. A cloned board does not merely fail to show you a nice picture. It cannot switch a single line in your car.
The factory brightness knob is an analog signal into the cluster, and it always was. The cockpit reads it directly and drives the panel’s backlight from it, so rolling the wheel at night dims the screen exactly like the gauges it replaced.
Four of them are telltales hard-wired to the cluster rather than sent over the bus: the parking brake, the lights, the high beams and stability control. The other two are the panel’s own power and a switched accessory feed. The cluster drives every one of them the way the factory unit did.
Every one of those outputs is gated on the board authenticating itself against its secure element at startup. A cloned board does not merely fail to display: it cannot switch a single line in your car.
The tick of the turn signal in this car does not come from a relay under the dash. It comes from the cluster. So does the seatbelt chime, and so does the tone when there is a car in your blind spot. Replace the cluster with something that cannot make a sound and the car goes quiet in a way you notice on the first drive.
There is an amplifier on the board for exactly this. The tick is timed to the indicator itself rather than played on a loop, so it lands with the lamp instead of drifting against it. The blind spot warning is per side. The seatbelt chime behaves the way the factory one does, and can be switched off if you would rather it were not there.
It is not a relay under the dash. In this car the cluster makes that noise, and it is timed to the indicator itself rather than played on a loop, so the tick lands with the lamp.
Speed-aware, exactly as the factory one is, and switchable off in the settings menu if you would rather it were not there.
Audible as well as visible, and per side, so a car in your left mirror sounds different from one in your right.
Reading a bus is easy. Being allowed to act on one is not, and it should not be. The interesting part of this feature is not the button on the screen, it is that the car agreed.
Body-control options are stored in the car, not in the cluster. They are changed by writing to the module that owns them over the same authenticated diagnostic session, which is why this has historically been something you pay someone to do with a laptop.
The cluster does it from the settings menu, in plain language, as often as you like. It reads the current value out of your car first, so what you see on screen is what your car is actually set to, not a switch the cluster is guessing at.
None of the data below is new. Your car has always known its own yaw rate, the pressure in each brake line and the temperature of every tire. The factory cluster simply had nowhere to put it, one small screen and a row of warning lamps.
Everything here is decoded continuously, and any of it can be put on screen, recorded to a session file, or used to decide whether to warn you.
Reading is one thing. These are the things the cluster can actually ask your car to do, each over the authenticated session, each from the settings menu.
Thirty things are watched continuously. They are not equal, so they are not treated equally. Each alert declares its severity, which side of the display it belongs on, and which screen it should open when you look at it.
A critical alert takes the display. A transient one shows briefly and hands the screen straight back to what you were looking at. A low tire opens the 3D view of your car with the affected corner highlighted, rather than showing you a symbol and leaving you to work out which wheel.
Reserve a place in the first batch. No payment today. We’ll confirm fitment for your model year before anything is charged.