U014100 ошибка ауди

Fault code U101400 normally means «Control module incorrectly coded». You will need to post-up the actual fault code details which you can do like this:

After you receive the digitized version of your scan report in the email, copy-and-paste the information here

Don

Hello, Thankyou for replying.

I think this is what you need.

OBDeleven data log Date: 2020-06-14 10:42 VIN: WAUZZZ8V4G1088635 Car: Audi A3 Year: 2016 Body type: Saloon Engine: CZEA 110 kW (150 HP) 1.4 l Mileage: 56568 KM ————————————————————— 09 Central Electrics System description: BCM MQBAB H Software number: 5Q0937084CL Software version: 0175 Hardware number: 5Q0937084AN Hardware version: H24 Serial number: 01061603600507 ODX name: EV_BCMMQB ODX version: 015001 Long coding: 07041A42C24122FD03804004B11807A80000000000000000000000000000 Subsystems: System description: WWS371 160202 Software version: 0585 Hardware version: 043 Serial number: 160209195356 Long coding: 0A47F7 System description: G397_RLFS Software version: 0004 Hardware version: H06 Serial number: 61358275 Long coding: 00006C System description: E1 — LDS MQB Software version: 0032 Hardware version: H05 Serial number: 16 12 2015 00000257 System description: Sensor, DWA Software version: 0316 Hardware version: 005 Serial number: 000000000ZY160192JFW System description: Sirene, DWA Software version: 0313 Hardware version: 005 Serial number: 00000000000034662855 Trouble codes: U101400 — Control module incorrectly coded static

^^^^yes, so as the error says «Control module incorrectly coded static» («static» means that it’s a permanent fault). You must have made changes to the 09 Central electrics module that it didn’t like.

Go to the History option for the module and revert the latest changes back to their original values

Don

Sorry if I’m being dumb so if I select the central electronic module separately and select history, what do I do then? Is it safe to ignore as car as no issues.

Thanks in advance.

^^^ second question first — it’s up to you whether you want to fix the error message, or not? I personally like my cars to have clean scan reports, but not everyone is the same as me — fortunately!!

As for your first question — I find it better to analyze the history report on a larger screen (or even on paper) if there are lots of entries. To do this, I need to digitize the history data and send it to myself via my email address. Once I have received the digitized data via email, I can print/transfer the database to another PC. The instructions for the digitization process are shown below.

So- the records in the History file list in date order the changes that were made to the car. The records show the control module, the date and the before/after values. Clearly from your error message something that you changed was incompatible with the module.

You need to look through the history records and revert the changes to their original values that look suspect. If you have only made a few changes to the hex09 module, this shouldn’t be difficult.

After each reversion of a change back to its original value, clear the error and re-poll the module. If the error does not reappear, the problem has been fixed!!

Don

^^^retroash: great to read that you have solved your problem (and probably that you have acquired some new skills) — well done!!

As for your «last question» the answer is YES and NO! As I have advised previously, it really all depends on the incorrect APP and the nature of the resulting error. The code-cutters @ VOLTAS IT who write these APPS implement lot’s of tests in their software to minimize the chance of inappropriate installation — but the risks are not eliminated entirely. I’ve seen instances of very severe consequences from APPs, but there are also many instances of no perceived effects from errors.

My personal approach is to NEVER use Apps because lot’s of them leave no detailed records of what was changed — and they remove the opportunity to learn how to implement tweaks manually (so you learn nothing). And, of course each APP costs points (don’t tell VOLTAS IT — but I don’t like giving them money for stuff that I don’t believe is worth-it!! )

Don

Well for the time being I think I will leave the car as standard. I will look very carefully into manually changing values. Thankyou very much for your time. It is appreciated.

Ash

good evening, please check if the fault is the same, and if possible how to fix. Thank you

Failure

Control unit: 09 Electronic central electrical system

Active failures: 0

Inactive failures: 1

System Description: BCM MQBAB H

Software Number: 5Q0937084AS

Software version: 0173

Hardware Number: 5Q0937084AN

Hardware Version: H24

Serial Number: 01061517301578

ODX Name: EV_BCMMQB

ODX version: 015001

Failures:

U101400 — Incorrectly coded command unit

Static

Date: 2020-07-04 18:39:11

Mileage: 25191 km

Priority: 2

Failure frequency counter: 1

Counter with reset: 54

Post status 15: on

Post status 50: desl.

Voltage: 12.3 V

External temperature: 23.5 °C

Bremslichtschalter status (HW): desl.

Bremslichtschalter status (CAN): desl.

desl.: triggered

Position light: not triggered

Automatic light switching: not triggered

Low light: not triggered

Light estacion.esq.: not triggered

Light estacion.dir.: not triggered

Letzte Weckursache/ Werte [00;2E]: keine Störschutzursache

CAN-Bus_aktiv: on

Mileage: 25191 km

Date: 2020-07-04 19:01

^ ^^mbarbisan: The description in your fault report certainly looks similar — but as to the cause, it could be the same, or different.

The fault is «inactive» — so first try clearing the fault

If this doesn’t work, again my suggestion is that you carefully look through the latest records in your history report (see my pictorial instructions above) for the Central electrics module. Wind-back each change listed and after each, try clearing the fault.

Don

Don, muito obrigado, limpei o relatório de erros e ainda continua o fracasso, farei o que você passou.

Help please.
I’ve spent many hours trying to work out this problem
I have a fault where my 2015 A3 sportback tail lights are not behaving correctly. Attached is the info yet I can’t connect the dots.
The R/H side amber tailgate light (sportback) is permanently on whenever the car lights are on (it’s the blinker tailgate amber light section, also the L/H side equivelant does not blink with left blinker. Since I have made some lighting changes as per apps I reversed them all to original but the fault remains. I’m desperate since my car is overdue for registration as I try to solve this problem.

OBDeleven data log

Date: 2021-09-11 10:40

VIN: WAUZZZ8V6FA016365
Car: Audi A3
Year: 2015
Body type: Sportback
Engine: CZCA
Mileage: 56311 KM

—————————————————————
09 Central Electrics

System description: BCM MQBAB H
Software number: 5Q0937084AJ
Software version: 0134
Hardware number: 5Q0937084AJ
Hardware version: H18
Serial number: 01011416304487
ODX name: EV_BCMCONTI
ODX version: 013000
Long coding: 07041A42C24122F543D44004000C07080000000000000000000000000000

Subsystems:
System description: WWS370 140525
Software version: 0580
Hardware version: 041
Serial number: 140528142309
Long coding: 0A47F7

System description: G397_RLFS
Software version: 0002
Hardware version: H06
Serial number: 22761398
Long coding: 00006C

System description: E1 — LDS MQB
Software version: 0032
Hardware version: H05
Serial number: 03 04 2014 00000562

Trouble codes:
U101400 — Control module incorrectly coded
static
Date: 2021-09-07 13:15:54
Mileage: 56311 km
Priority: 2
Malfunction frequency counter: 1
Unlearning counter: 192
Terminal 15 status: On
Terminal 50 status: Off
Voltage: 14.5 V
Outside air temperature: 24.5 °C
Status Bremslichtschalter (HW): On
Status Bremslichtschalter (CAN): On
Off: not activated
Parking light: not activated
Automatic high beam assist: operated
Low beam: not activated
Parking light left: not activated
Parking light right: not activated
Letzte Weckursache/ Werte [00;2E]: keine Störschutzursache
CAN-Bus_aktiv: On

Hello I have the same error coming up when I hook up my OBDeleven to my car and it is under the navigating area.here is what I get in the informant. Any help would be appreciated since I am still learning how to use this and still new to owning a Jetta.

OBDeleven data log

Date: 2021-10-21 04:48

VIN: 3VWD17AJ1FM249621
Car: Volkswagen Jetta SE
Year: 2015
Body type: Saloon
Engine: CPRA
Mileage: 216750 KM

—————————————————————
37 Navigation

System description: RNS315-NAR
Software number: 1K0035274B
Software version: 0265
Hardware number: 1K0035274B
Hardware version: H35
Serial number: VWZAZ2M4202970
ODX name: EV_RNS315NARV2UDS
ODX version: A01004
Long coding: 0400040104000F000001100A

Subsystems:
System description: NAR_V2
Software number: 3AA919866B
Software version: 0002

Trouble codes:
B106113 — Left front treble speaker Open circuit
static
Date: 2078-12-06 04:44:11
Mileage: 216759 km
Priority: 5
Malfunction frequency counter: 1
Unlearning counter: 14
B106413 — Right front treble speaker Open circuit
static
Date: 2078-12-06 04:44:11
Mileage: 216759 km
Priority: 5
Malfunction frequency counter: 1
Unlearning counter: 14
B106613 — Left rear treble speaker Open circuit
static
Date: 2078-12-06 04:44:11
Mileage: 216759 km
Priority: 5
Malfunction frequency counter: 1
Unlearning counter: 14
B106813 — Right rear treble speaker Open circuit
static
Date: 2078-12-06 04:44:11
Mileage: 216759 km
Priority: 5
Malfunction frequency counter: 1
Unlearning counter: 14
B104813 — Telephone microphone Open circuit
static
Date: 2078-12-06 04:44:08
Mileage: 216759 km
Priority: 5
Malfunction frequency counter: 1
Unlearning counter: 14
B200042 — Ctrl. module faulty
static
Date: 2071-12-22 08:54:34
Mileage: 199665 km
Priority: 4
Malfunction frequency counter: 1
Unlearning counter: 255
U101400 — Control module incorrectly coded
static
Date: 2078-12-06 04:44:09
Mileage: 216759 km
Priority: 5
Malfunction frequency counter: 1
Unlearning counter: 14
CD changer: OK
Speaker status: OK
Telephone transceiver: Error
Correction for sound system: OK
Status of antenna 2 for radio: OK
Digital radio (DAB): OK
Antenna diagnostic: OK
Telephone baseplate diagnostic: OK
Rearview camera: OK
Traffic sign display: OK

Hello

Someone can help me with this error:

5F Multimedia

Descripción del sistema: MU-S—ER
Número de software: 5F0035824C
Versión de software: 0514
Número de hardware: 5F0035824C
Versión de Hardware: H50
Número de serie: SEZAZ2W0662179
Nombre ODX: EV_MUStd6C1TSAT
Versión ODX: 001015
Codificación larga: 04720000960A000011220001001828002F0205C40120050006

Subsistemas:
Descripción del sistema: ABT_Std-2
Versión de software: 8130
Versión de Hardware: H54
Número de serie: SEZ6ZHW2580361

Códigos de error:
U101400 — Control module incorrectly coded
static
Thank you

otanerist: It’s stating the obvious, but your DTC (error) is telling you that the hex5F module is unhappy because it believes that it is coded incorrectly. Clearly this means that one or more changes that were made to the module was incorrect.

It’s not possible to be any more precise as to what specifically has caused the DTC, If you made changes manually to the module, I suggest that you go through the records in History and examine the changes made. If you use one-click Apps, maybe undo any related to the module

Don

I’m getting this fault on my 2017 seat Ibiza

Unable to clear, I have the OBDeleven app on my phone so I can’t see where to fix this.

It does say it’s static so I cannot remove it.

I also keep getting my screen saying my car is low battery. However I’ve had both my battery and alternator tested and they’re both fine. The OBD reads the battery as low too so I’m assuming the ECU is reading it wrong. Could this be due to the fault code “incorrectly coded”

This is in the multimedia control module

Hello
My car golf mk7 r has this fault . Acc tirepressure hill hold everything doesn´t work
How can i code this correctly?

OBDeleven data log

Date: 2022-03-19 10:43

VIN: WVWZZZAUZEW328727
Car: Volkswagen Golf R
Year: 2014
Body type: 5-dr hatchback
Engine: CJXC
Mileage: 167234 KM

—————————————————————
03 Elektronica remsysteem

System description: ESC
Software number: 5Q0907379AB
Software version: 0557
Hardware number: 5Q0907379H
Hardware version: H31
Serial number: 60474000000501
ODX name: EV_Brake1UDSContiMK100IPB
ODX version: 033001
Long coding: 01FA6BA154222974037E070241CA6980D62A94C0E08296F7F84250F8C204

Trouble codes:
U101400 — Regelapparaat verkeerd gecodeerd
Permanent

fatboy: the error says «Control unit coded incorrectly». Don’t those words suggest a logical answer to your question?

Presumably, the car didn’t have this error before changes were made to the module -so simply unwind the changes that were made! Go to History, look for the records that refer to hex03 modul and revert settings to «old value»

Don

Got exact same problem after using apps. Tried to revert everything to default version but still the problem persists. Any help? I know it is a static problem so no way to clear it. Also reverted all the changes in central electronics but no luck with the error code.

OBDeleven data log

Date: 2022-07-13 12:28

VIN: WAUZZZ8V4J1043850
Car: Audi A3
Year: 2018
Body type: Cabriolet
Engine: DCYA
Mileage: 121920 KM

—————————————————————
5F Multimedia

System description: MU-HS-LN-EU
Software number: 81A035193F
Software version: 0213
Hardware number: 81A035193
Hardware version: 050
ODX name: EV_MUHigScl6C3DELP
ODX version: 001011
Long coding: 01730001FF00000011110005000A00102F002AC401F00100CC

Trouble codes:
U101400 — Control module incorrectly coded
static
Date: 2022-07-11 13:10:13
Mileage: 121892 km
Priority: 4
Malfunction frequency counter: 1
Unlearning counter: 33
Dynamic environmental data: 0286781017555515555555A9

control unit coded incorrectly
Data: 2022-10-04 14:06

    VIN: WVWZZZ3CZFE491356
    Mașină: Volkswagen Passat R-line Blue Motion
    An: 2015
    Tipul caroseriei: Saloon
    Motor: CRLB
    Kilometraj: 167606 KM

—————————————————————
5F Bloc electronic de informare 1

    Descriere sistem: MU-H-N-EU
    Număr software: 3G0035043K
    Versiune software: 0199
    Număr hardware: 3G0035043
    Versiune hardware: H41
    Număr de serie: A599C0FB007737
    Nume ODX: EV_MUHig4CGen2HBAS
    Versiune ODX: 001001
    Codare lungă: 02840101FF00000011110001000808039F0106B4012000001F

    Subsisteme:
        Descriere sistem: ABT_High    
        Versiune software: 0032
        Versiune hardware: H63
        Număr de serie: VWZ8Z9SKL0812L     

        Descriere sistem: ECE 2022/2023
        Versiune software: 0197
        Versiune hardware: —
        Număr de serie: ———————

        Descriere sistem: Gracenote2  
        Versiune software: 1008
        Versiune hardware: —
        Număr de serie: ———————

    Coduri de eroare:
        U101400 — Unitate de comandă codată incorect
            static
                Date: 2022-10-04 13:40:10
                Mileage: 167606 km
                Prioritate: 4
                Contor de frecvență erori: 1
                Contor ștergere: 213
                Date dinamice mediu: 02867B1017555555555455A9

Hello

Someone can help me with this error:

OBDeleven data log

Date: 2022-12-31 00:40

VIN: WAUZZZ4G6FN028371
Car: Audi A6
Year: 2015
Body type: Avant
Engine: CVUA
Mileage: 136846 KM

—————————————————————
5F Informationselektronik 1

System description: MU-H-LND-EU
Software number: 4G1035021P
Software version: 1425
Hardware number: 4G1035021
Hardware version: H33
Serial number: A276J0E7513847
ODX name: EV_MUHig6C3Gen2HBAS
ODX version: 001115
Long coding: 012306010000000013111102308A0093AF0008C57171AF0DBF

Trouble codes:
U101400 — Steuergerät falsch codiert
statisch
Date: 2022-12-30 01:51:59
Mileage: 136846 km
Priorität: 4
Fehlerhäufigkeitszähler: 1
Verlernzähler: 52
Dynamische Umgebungsdaten: 0286851017555555145555A9
B201A00 — Softwareversionsmanagement prüfen
statisch
Date: 2022-12-30 01:52:04
Mileage: 136846 km
Priorität: 6
Fehlerhäufigkeitszähler: 1
Verlernzähler: 52
Dynamische Umgebungsdaten: 02868510024D4455413030392F46726F6E74202020
U11B800 — Schnittstelle für externe Medien keine Kommunikation
statisch
Date: 2022-12-30 01:51:59
Mileage: 136846 km
Priorität: 4
Fehlerhäufigkeitszähler: 1
Verlernzähler: 52
Dynamische Umgebungsdaten: 02868418E801

OBDeleven vehicle history log
Date: 2023-04-20 8:01:57 pm

VIN: WVWZZZAUZGW016093
Car: Volkswagen GOLF R 2012-2017
Year: 2016
Body type: D5 Hatchback
Engine: CJXC kW ( hp) l
Mileage: 102266

U101400 — Control module incorrectly

aptation
Control unit: 09 Central Electrics
Name: Leuchte 0 BLK VL B36
Values:
Lichtfunktion B 0:
Old value: nicht aktiv
New value: Tagfahrlicht

Lichtfunktion C 0:
Old value: nicht aktiv
New value: Standlicht allgemein (Schlusslicht, Positionslicht, Begrenzungslicht)

Dimmwert CD 0:
Old value: 0
New value: 127

Lichtfunktion E 0:
Old value: nicht aktiv
New value: Blinken links Dunkelphase

Dimming Direction EF 0:
Old value: maximize
New value: minimize
Mileage: 102258 km
Date: 2023-04-20 4:06:24 pm

Adaptation
Control unit: 09 Central Electrics
Name: Leuchte1BLK VRB20
Values:
Lichtfunktion B 1:
Old value: nicht aktiv
New value: Tagfahrlicht

Lichtfunktion C 1:
Old value: nicht aktiv
New value: Standlicht allgemein (Schlusslicht, Positionslicht, Begrenzungslicht)

Lichtfunktion E 1:
Old value: nicht aktiv
New value: Blinken rechts Dunkelphase

Dimming Direction EF 1:
Old value: maximize
New value: minimize
Mileage: 102258 km
Date: 2023-04-20 4:08:29 pm

I tried to do Hazard Lights As DRL’s but stopped working so I tried to reverse the code but this resulted in my right indicator to stop working. Urgent help required!

jayislamm : emergency remedial code-changes below

Don

Did you mix-up the «right indicator» in your post — because the changes in your history records refer to the Leuchte-set for the left-side turn-signal lamp?

If the front turn-signal lamps on this car are incandescent — do this:

Leuchte 0 BLK VL B36
Lasttyp 0 > 12 — Blinkleuchten
Lampendefektbit Position 0 > 34
Fault Middle Byte DTC-DFCC 0 > 14
Lichtfunktion A 0 > Blinken links Hellphase
Lichtfunktion B 0 > not active
Dimmwert AB 0 > 100
Lichtansteuerung HD AB 0 > Always
Lichtfunktion C 0 > Blinken links Dunkelphase
Lichtfunktion D 0 > not active
Dimmwert CD 0 > 0
Dimming Direction CD 0 > minimize
Lichtfunktion E 0 > not active
Lichtfunktion F 0 > not active
Dimmwert EF 0 > 0
Dimming Direction EF 0 > maximize
Lichtfunktion G 0 > not active
Lichtfunktion H 0 > not active
Dimmwert GH 0 > 0
Dimming Direction GH 0 > maximize

If the front turn-signal lamps on this car are LED, do this:

Leuchte 0 BLK VL B36
Lasttyp 0 > 33 — LED-Modul Blinkleuchten
Lampendefektbit Position 0 > 34
Fault Middle Byte DTC-DFCC 0 > 14
Lichtfunktion A 0 > Blinken links Hellphase
Lichtfunktion B 0 > not active
Dimmwert AB 0 > 127
Lichtansteuerung HD AB 0 > Always
Lichtfunktion C 0 > Blinken links Dunkelphase
Lichtfunktion D 0 > not active
Dimmwert CD 0 > 0
Dimming Direction CD 0 > minimize
Lichtfunktion E 0 > not active
Lichtfunktion F 0 > not active
Dimmwert EF 0 > 0
Dimming Direction EF 0 > maximize
Lichtfunktion G 0 > not active
Lichtfunktion H 0 > not active
Dimmwert GH 0 > 0
Dimming Direction GH 0 > maximize

Hi Guys ,

I did a mal coding in my Skoda Octavia 2018 , can someone help me to erase this error ?

—————————————————————

5F Electronique d’information 1

Description du système: MU-E—ER

Numéro de logiciel: 5E0035871D

Version de logiciel: 8755

Numéro de Matériel: 5E0035871D

Version matériel: 671

Numéro de série: 30111700020387

Nom du ODX: EV_MUEnt4CGen2LGE

Version ODX: 001041

Codage long: 03730100FF00000041110001000100232F0000C40000010003

Codes d’erreur:

U101400 — Calculateur mal codé

statique

mmoha : The information in your post simply confirms that the MMI (the unit in the glove-box) has been incorrectly coded. As to why this has happened -I suggest that you refer to the records in History. Look for changes that were made to the 5F module and revert the settings to «old value».

Don

Hi Guys ,

Can you explain how to revert the last modification that give the error «central electronics error U101400»

Historique des log des véhicules OBDeleven

Date: 2023-05-06 09:05

VIN: TMBAJ4NEXJ0244303

Voiture: Skoda Octavia

Année: 2018

Type de carrosserie: Saloon

Moteur: CRVC

Kilométrage: 94179 KM

—————————————————————

App

nom: Static Cornering Lights Settings

Ancienne valeur: 0 — 40km/h

Nouvelle valeur: 0 — 20km/h

Kilométrage: 94179 km

Date: 2023-05-05 20:31

—————————————————————

Scan complet

Unités de contrôle: 14

Nombre de défauts: 1

Kilométrage: 94179 km

Date: 2023-05-05 20:21

—————————————————————

Réglages de base

Unité de contrôle: 5F Electronique d’information 1

nom: Validation de la fonction SWaP

Statut:

Kilométrage: 94179 km

Date: 2023-05-05 20:12

—————————————————————

Adaptation

Unité de contrôle: 5F Electronique d’information 1

nom: Transmettre le code de validation d’une fonction SWaP

Valeurs:

—:

Ancienne valeur: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

Nouvelle valeur: 110200060300035E0035871D546D62616A346E65786A3032343433303300645554A30000000000000000003B0FC769BFFF15ECD445B8196D2203D6D56BD8F22748B37D68F863DAC57E23C90A5FEEF0C06394C8D48A2EAA4F0FB658557400E66441DDC7D5AC3610AA4D45056C0C6E17C7E4B60C40E52FFA891938AF186ED20AE83A99EB10F3088479E6CBD2770C1563B5AE235B440BEF16EBE696576E108F2F9F897D963DEFBAD3ABDF2FFE000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

Kilométrage: 94179 km

Date: 2023-05-05 20:12

—————————————————————

Session de diagnostic

Unité de contrôle: 5F Electronique d’information 1

valeur: Mode fin de bande (EOL)

Kilométrage: 94179 km

Date: 2023-05-05 20:09

—————————————————————

Réglages de base

Unité de contrôle: 5F Electronique d’information 1

nom: Validation de la fonction SWaP

Statut:

Kilométrage: 94088 km

Date: 2023-05-04 15:05

—————————————————————

Session de diagnostic

Unité de contrôle: 5F Electronique d’information 1

valeur: Mode fin de bande (EOL)

Kilométrage: 94088 km

Date: 2023-05-04 15:04

—————————————————————

Scan complet

Unités de contrôle: 14

Nombre de défauts: 3

Unités de contrôle:

76 Aide au stationnement

Description du système: PDC 4 Kanal

Numéro de logiciel: 5QA919283B

Version de logiciel: 0044

Numéro de Matériel: 5QA919283

Version matériel: H07

Numéro de série: 00030841961734703218

Nom du ODX: EV_EPHVA14AU3700000

Version ODX: 009033

Défauts:

Aucun code d’erreur trouvé

5F Electronique d’information 1

Description du système: MU-E—ER

Numéro de logiciel: 5E0035871D

Version de logiciel: 8755

Numéro de Matériel: 5E0035871D

Version matériel: 671

Numéro de série: 30111700020387

Nom du ODX: EV_MUEnt4CGen2LGE

Version ODX: 001041

Défauts:

U101400 — Calculateur mal codé

statique

Date: 2023-05-04 11:34:21

Mileage: 94087 km

Priorité: 4

Compteur de fréquence des défauts: 1

Compteur de désapprentissage: 112

Données ambiantes dynamiques: 0286791017555555555555A8