| Coding or adaptation | Typical models | What it changes | How it is done |
|---|---|---|---|
| Needle sweep on start-up | Audi A3, A4, TT | Gauges sweep at ignition | Instrument cluster coding |
| Auto lock at speed | Golf, Polo, Octavia, Leon | Doors lock when moving | Convenience module coding |
| Cornering fog lights | Golf Mk5 and Mk6, Passat | Fog lamp lights the turn | Central electrics coding |
| DRL menu option | MQB platform cars | Adds on and off switch | Body control long coding |
| Throttle body alignment | Petrol models after cleaning | Relearns idle position | Basic settings procedure |
| Steering angle calibration | Any model after alignment | Clears code 00778 | Basic settings procedure |
| Service interval display | All VW Group models | Matches fixed or LongLife | Adaptation channels |
| Gateway installation list | Cars with retrofits | Registers added modules | Prevents phantom fault codes |
A full auto-scan interrogates every control module in the car, not just the engine, and reports fault codes with freeze frame data showing the conditions when each fault occurred. It also records each module's part number, software level and coding. That gives us a complete electronic health check, and it is an excellent pre-purchase check before buying a used VW Group car.
Done properly, yes on both counts. Before we change anything we save the module's original coding, so every change we make can be reversed exactly. The risks people read about almost always come from guessing at long coding values or copying settings from a different model year. We code only documented, tested changes appropriate to your exact hardware.
It depends entirely on the model, year and fitted hardware. Common requests include needle sweep, auto locking at speed, cornering fogs, lighting behaviour changes, extra display menus and comfort closing of windows. Some features need hardware the car does not have, in which case coding alone cannot add them. Tell us your registration or exact spec and we will confirm what is genuinely available.
Both, depending on the fault. Some problems really are software or adaptation issues, a steering angle sensor needing calibration for example, and VCDS resolves them on the spot. For mechanical and electrical failures, VCDS is the diagnostic stage: output tests and logged live data prove which component has failed, and we then quote for the physical repair with genuine or OEM parts.
Enabling built-in convenience features is generally invisible in day-to-day use, but a dealer can see coding changes, so on a car under manufacturer warranty we advise keeping changes modest and reversible, which ours are. For insurance, coding that alters vehicle behaviour or adds equipment can count as a modification, and disclosure is your call. We keep a record of everything we change either way.
Usually, yes. Retrofits commonly stall at the coding stage, where the new hardware needs adding to the gateway installation list and coding into the relevant modules. We handle that regularly for cameras, cruise control, headlight upgrades and similar additions. Note that some retrofits on newer cars need online component protection work, which we carry out with ODIS rather than VCDS.
Because clearing a code removes the record, not the cause. A code that returns is telling you the fault is still present or still intermittent. This is where logging comes into its own: we record live data while the car is driven and catch the moment the fault sets. Repeated clearing without diagnosis just delays the repair and can mask a developing problem.
VCDS covers scanning, adaptations, basic settings and most coding on VW Group cars, and for that work it is the right tool at the right price. Jobs that need the factory online systems, such as official software flashing, online coding of replacement modules, immobiliser adaptation and component protection, need ODIS, which we also run in house. You get whichever tool the job requires.