Fault code · VW · Audi · SEAT · Škoda · Cupra

U101400 and U101300: control module incorrectly coded or not coded

U101300 and U101400 show up when a module's coding doesn't fit the car: after a replacement, a retrofit or a used part from another car. On newer Volkswagen Group cars the fix is usually online coding, not typing in a code by hand.

By Harshit Vadgama, automotive engineer · Updated

In short

U101300 means a control module is not coded, and U101400 means it is coded incorrectly for this car. Both usually follow a module replacement, a retrofit or a used part. On current VW Group cars the correct coding comes from the factory backend through SVM in ODIS. One known exception is a harmless U101400 in some 2019–2020 Audi telematics modules.

U101300Control module not coded (older: 01042)
U101400Control module incorrectly coded (older: 01044)
Usually afterModule replacement, retrofit, used part, wrong manual coding
Proper fixSVM configuration check / online coding in ODIS
Known exceptionAudi telematics J949 (address 0075), 2019–2020 models

What the codes mean

Each control unit carries coding: a value that tells it which car and equipment it's in (engine, gearbox, country, options). When a module has no coding at all, it stores U101300 "Control module not coded". When the coding doesn't match the car, it stores U101400 "Control module incorrectly coded". Older cars and scanners show the same faults as 01042 and 01044.

Common causes

  • A replacement module fitted without the replacement procedure
  • A used module still carrying the coding of the car it came from, for example a climate panel from a different model
  • A retrofit, such as a camera or radar, where other modules also need new coding
  • Manual coding mistakes with an offline tool

Coding often has to happen in a set order. Technicians fitting a new windscreen camera, for example, report that the power steering module had to be coded before the camera before the code cleared. Coding only the module that shows the fault is a common reason it keeps coming back.

Why manual coding often doesn't work any more

On older cars you could look up the right coding and type it in. On current MQB and MLB evo cars many modules get their coding and parameters from the manufacturer's backend through SVM. Audi has even published a bulletin listing control units that, for a period, could only be coded with the manufacturer's help after replacement. If the coding isn't right in the factory record, typing a value in by hand is a guess.

The Audi telematics exception

On 2019–2020 Audi A4, A5, Q7, A6, A7, Q8 and Q5 models, the telematics module (J949, address 0075) can store U101400 because of a start-up timing issue, without any real coding fault. Audi documented this in a service bulletin. If that's the only module with U101400 and Audi connect works, it's likely this case.

How it's fixed properly

  1. Full scan and gateway installation list check: which modules are affected, and which are fitted.
  2. Online SVM configuration check in ODIS, so coding comes from the factory record for your VIN.
  3. Adaptations and basic settings for the module and anything that depends on it (cameras and radar need calibration).
  4. Rescan and function test.

If the part is used and protected, Component Protection may need releasing first. All of this can be done remotely: see VAG online programming or new part coding after replacement.

Frequently asked questions

What's the difference between U101300 and U101400?

U101300 means the module has no coding. U101400 means it has coding, but the wrong coding for this car.

Can I fix U101400 with VCDS?

Sometimes on older cars, if you know the correct coding. On current VW Group cars the coding usually comes from the factory backend through SVM in ODIS, so manual coding is often a guess.

Why does U101400 come back after I clear it?

The coding still doesn't match the car, or a related module also needs coding. Some jobs need modules coded in a specific order.

Is U101400 in my Audi telematics module serious?

On 2019–2020 A4, A5, Q5, Q7, A6, A7 and Q8, Audi documented a start-up timing issue that stores U101400 in the telematics module without a real fault. If it's the only affected module and everything works, it's likely that.

Sources