Unfortunately we do not accept new members for free, Now Registration cost 30€, if you are interesting Send Email to [email protected]
Audi A3 8L 8L0920900K -> 8L0920900E
10-02-2018, 17:16 PM,
Post: #1
|
|||
|
|||
Audi A3 8L 8L0920900K -> 8L0920900E
Hi guys,
i've replaced my Magneti Marelli / Jaeger instrument cluster 8L0920900K with a used 8L0920900EX. Both have Immo3. I only have a full version of Ross Tech's VCDS interface, so it was not easy to get access to the new dashboard's bin. But i managed it to read a 65.536 Bytes hex file via VCP drivers of my ross-tech interface and the tool "VAG K+CAN Commander v2.5". Newer versions doesn't allow K-Line or are not able to detect my interface. My problem is: The programm shows incorrect login codes and wrong mileage. However, with that *.bin and a hex reader i was able to get the login code for my new instrument cluster. Since the wrong information the tool displays, i dont trust it enough change the mileage directly or upload a different *.bin with it. So my question is: how the hell do i change the mileage now? VCDS doesn't allow it and all other tools i tried doesn't accept the VCP - just the CAN Commander 2.5. It cant be the only way i think. My other problem is that i can't change the coding of the dashboard from 04040 to 00040. VCDS says its saved but displays the wrong 04040 again after it. Even a coding of cannel 19 (to enable temperature display) has a strange behaviour. I expected a 5 digit code, but only a "1" was set. When i enter "30011" it doesn't let me save the value. Entering "00011" results in saving "11". Can there be something shifted while my cluster and ECU connected to each other? It looks like the cluster was in 2 more cars before mine. Thanks for any advice about a different software or a solution of coding via vcds. |
|||
10-02-2018, 18:32 PM,
Post: #2
|
|||
|
|||
RE: Audi A3 8L 8L0920900K -> 8L0920900E
(10-02-2018, 17:16 PM)tmoo Wrote: Hi guys, File Size should be 2kb you need only eeprom of 912dg128 Best is read on bench by Orange or any other programmer and do mileage by soft mileage have CRC if it is wrong you get 999.999km and without good original read not easy to fix |
|||
11-02-2018, 12:33 PM,
(This post was last modified: 11-02-2018, 12:35 PM by zix1.)
Post: #3
|
|||
|
|||
Audi A3 8L 8L0920900K -> 8L0920900E
Had the same problem, trying to adapt new (used) cluster. Cluster ignored any coding or adaptation. So that was the problem. If immo adaptation is not 100% correct, you will get different problems.
In most cases you can’t adapt an used Jaeger cluster to you car, except you transfer 1:1 eeprom immo data. Its also important to know if cluster an car both have CAN or not. You can adapt mileage with vcds if you set it via eeprom under 100 or use Digiprog 3 with st47 I think. |
|||
12-02-2018, 23:06 PM,
Post: #4
|
|||
|
|||
RE: Audi A3 8L 8L0920900K -> 8L0920900E
Thanks so much for your answers. I was going crazy because i thought vcds is trolling me.
Is it a good idea to try to re-adapt the "new" cluster with my car and hope it will fix itself? Or maybe anyone has a virgin dump for 8L0920900E and/or 8L0920900K? Thanks! |
|||
13-02-2018, 06:24 AM,
Post: #5
|
|||
|
|||
Audi A3 8L 8L0920900K -> 8L0920900E
(12-02-2018, 23:06 PM)tmoo Wrote: Thanks so much for your answers. I was going crazy because i thought vcds is trolling me. If you put your old cluster back in car, everything should be fine, because it’s already adapted to your immo. From my experience you can’t adapt 90% of used Jaeger clusters to your car. You need a new one or in virgin state. Eeprom is in HC08 and 912(s) Chip. You can read it by orange5 or maybe Carprog. |
|||
« Next Oldest | Next Newest »
|
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Return to TopReturn to Content