Ignition On — the Self-Check
The few seconds between ignition on and cranking are when the car powers up its modules, checks itself, and decides what it is prepared to allow.
In plain language
Switching on the ignition does more than light up the dashboard. Circuits are energised in groups, each module powers up and tests itself, the modules introduce themselves to each other over the car's networks, and the warning lights you see sweep across the cluster are part of that check rather than decoration.
If something is wrong, this is usually where you first find out about it: a warning light that stays on, a function that is not available, or a car that simply refuses to go any further.
What the customer sees
Warning lights that illuminate and then go out, or one that stays on. A cluster that comes up late, dims or resets. Functions that are unavailable until the engine is running.
What the module is doing
Powering up, checking its own supply and memory, reading its stored configuration, testing the circuits it is responsible for, and beginning to transmit and receive on the network. Each module also starts monitoring for the messages it expects; a message that never arrives is recorded as a fault by the module waiting for it.
What a technician tests
Whether every module that should be present is awake and communicating, using a full-system scan. Then supply and ground for anything that is not, before assuming the module itself is at fault. Live data is more useful than codes at this stage: what a module reports it can see tells you where the picture breaks down.
The technical detail
Circuits come up in groups, not all at once. Supply groups are switched by relays and electronic switches according to the power mode, and the car's power management decides which groups it is prepared to energise given current battery condition. A module in a group that was never energised behaves exactly like a failed module on a scan report.
Self-tests happen before the car is asked to do anything. Modules verify their own supply and internal state, confirm their configuration matches the vehicle, and where applicable run circuit checks on their outputs. A configuration mismatch is a genuine fault class of its own: nothing is broken electrically, but the module is set up for a different vehicle or specification.
The network handshake is what makes the car a system. Once awake, modules broadcast status and consume each other's messages. A module that is unpowered, asleep or disconnected does not announce that fact; the other modules simply notice that its messages stopped and record it. This is why one missing module generates faults in many others.
Warning-light behaviour is a communication test in itself. Most cluster warnings originate in other modules. A lamp that never illuminates during the check can indicate a missing message just as much as a lamp that stays lit.
Why this matters when something goes wrong
Reading a scan taken at ignition on tells you the shape of the problem before any component is tested. Faults spread across many modules with a common thread — supply, voltage or a single silent transmitter — point at one cause. Faults confined to one module with its own circuits point at that module's circuits.
The ordering also matters when a car is being scanned after a battery has gone flat or been disconnected. Modules record what they experienced during the event, and clearing the memory and re-testing after the electrical system is known good is the only way to separate the history from what is actually wrong now.