Coding, programming, flashing: where the difference lies

These three words get used as synonyms on forums. They are not. The difference decides how risky an operation is, how long it takes and whether it can be undone.

Coding — flipping switches

Coding changes parameters the control unit already knows about. The function exists in the software; we simply move a value from off to on. Ambient lighting, comfort indicators, video in motion: all coding.

The risk is low because the firmware stays untouched. A wrongly set value can be reset. That is also why coding works reliably over a remote connection.

Programming — updating the software

Programming means bringing a control unit's firmware to a newer level — comparable to a system update. It can be necessary to make a function available at all when the old version does not contain it.

This is more serious. If the process breaks off, for example because voltage drops, the control unit can be left unusable. That is why a charger stays connected during any programming — not optional, mandatory.

Flashing — replacing the engine map

Flashing almost always refers to the engine control unit. The data area holding the maps for injection, boost pressure and ignition timing is overwritten. This is chiptuning.

Technically it is a write operation like programming, but in substance it is an intervention in engine management. That is why diagnostics belong before it and a test drive after it.

The differences side by side

What to take from this

Before any appointment, ask which of the three operations will take place. The answer tells you more about a provider's seriousness than any price.