STEUER14 codes Porsche control units from a Mac or Windows laptop over a standard ENET cable. Change single parameters in a table editor, code a unit to the car's vehicle order the way the factory rules do, or apply a whole retrofit with a coding recipe. Every write is backed up to the server first and read back afterwards.
Coding writes a control unit's configuration: which equipment it should expect, which functions are switched on, which market variant it runs. It does not replace the unit's software; that is programming, sold separately (see pricing). Nothing is written until you confirm.
| Platform | Coding in STEUER14 |
|---|---|
| Taycan (9J1) | Manual coding, automatic coding, coding recipes, vehicle-order edits |
| 911 (992) | Manual coding, automatic coding, coding recipes where published, vehicle-order edits |
| Panamera (971, 972) | Manual coding, automatic coding, coding recipes where published, vehicle-order edits |
| Cayenne (9YA) | Manual coding, automatic coding, coding recipes where published, vehicle-order edits |
| Macan Electric (XAB), Cayenne Electric (PO54X) | In testing: manual coding (most control units need an SFD2 unlock first); no automatic coding yet |
Recipes are written per platform; the Coding recipes tab shows the ones available for the connected car. On newer cars many control units protect coding with SFD2, and a write is refused until the unit is unlocked (see special functions).
If the backup can't be secured, the write is blocked. Undecoded bytes of partly decoded records are written back unchanged. Full walkthrough: Coding.
Automatic coding does what the factory tester does: it reads the vehicle order (the car's PR equipment codes) and the unit's identity, checks every coding record against the factory rules and writes only what deviates. Details shows which PR code sets which bits.
Code control unit takes a full backup first and verifies every write; bits the rules don't define keep their value. You can also edit the vehicle order (add, change or remove PR numbers, backed up first) and let automatic coding follow it. See automatic coding and vehicle order in the manual.
A coding recipe is a ready-made job written on our server for one platform. It bundles what a retrofit needs across one or more control units: coding values, vehicle-order PR changes and automatic-coding runs. Which recipes there are depends on the platform.
A step changes only the options it names and leaves the rest of the record alone. If a step is refused, the verdict says which and why. More: Coding recipes.
Every coding write is recorded in your account history. In the coding editor, Restore… lists the backups taken before earlier writes on this car; Confirm restore backs up the current state, then writes the chosen backup byte for byte and verifies it. The vehicle order has its own Backups tab.
No. Reading and clearing fault memory, the Taycan's high-voltage battery module and actuator tests that need no security unlock are free. Coding needs a car licence or the workshop plan.
Yes. Every write is preceded by a server backup of the control unit, and Restore… writes an earlier backup back and verifies it.
Coding changes a unit's configuration; programming replaces its software. Programming comes with a programming pass (€49 per car for 7 days, coding included) and with the workshop plan; coding alone comes with the car licence.
Usually because of stored faults on that control unit, or because the unit is locked with SFD2. Clear the fault memory or unlock the unit, then write again.
Fault memory is free on every control unit: check the connection to your car before you buy anything.