PDA

View Full Version : 2003 Audi A4 RB4 learning experiment



ledojo
21st February, 2012, 09:00 PM
I have a cluster from a 2003 Audi A4 (Cabriolet?). Anyhow, It was dropped off with a problem stating the Tachometer and Speedometer were in-op.

3.0L, Automatic, gasoline, US-model.

I opened it up. There's a NEC mcu. I got dump from 24c08.

I was wondering maybe this was a failed correction via OBD? And somehow something was corrupted?

Any chance that the 24c08 dump could correct problem? Or, must the NEC be read/corrected.

Note: This is something I'm just experimenting with to learn--If anyone is willing to point me in the right direction or even share their experience--That'd be great, but totally understood if not.

(btw, I have no pro tools for this as this is not usual work for me. I have UUSP, VCDS, and have installed the VAG eeprom Programmer, but have zero experience in this field. I also have Digimaster II, but didn't see anything for the NEC offhand. Not sure if any other tools worth mentioning. Again, just trying to learn something from this is all)

Thank you all in advance.

z786
21st February, 2012, 09:04 PM
what hav u fot on odo display
does mileage show?
have u checked the fuses?

smokey08
21st February, 2012, 09:05 PM
First thing to do is an output test with VCDS to see if needles move.

ledojo
21st February, 2012, 09:12 PM
what hav u fot on odo display
does mileage show?
have u checked the fuses?

Mileage shows. Car starts and runs. Tach and Speedo appear to be only parts not working.


First thing to do is an output test with VCDS to see if needles move.

I did do output test at their garage and all needles move.

ledojo
21st February, 2012, 09:16 PM
Before they dropped off the cluster, they said they took to an Audi Specialist with a used cluster, but he could not get used cluster to work or maybe he couldn't program the keys? idk... He was using VAS.

So, anyhow, I told them to drop off the cluster and I'd mess around with it (I wanted to see what I would learn). If nothing comes of this, that'd be horrible, but I think I will learn something from this process none-the-less.

smokey08
21st February, 2012, 10:08 PM
EEprom data is prob bad then. Fitting the customers secondhand cluster would be easiest, Use vag eeprom to get the pin from it then program it with VCDS.

ledojo
21st February, 2012, 10:14 PM
EEprom data is prob bad then. Fitting the customers secondhand cluster would be easiest, Use vag eeprom to get the pin from it then program it with VCDS.

I'm not sure, but would I need a new key for this?

And, do I need pin from old cluster also? Or is it the pin from ecu? I think I found that it's a 7-digit pin from reading other posts.

I will try as you say and post results.

Thank you.

smokey08
21st February, 2012, 10:30 PM
Use a 4 digit pin (there is an option of 4 or 7 digit)

I think old key will adapt to secondhand dash once it has be coded with the right immo id/pin.

Pin will be in ecu. yes you need pin from old and new clusters. Lupu sandu did a good video on how to set used modes and read these rb4 clusters with vag eeprom programmer.

Have a look at this (http://wiki.ross-tech.com/wiki/index.php/Immobilizer_III_Immobilizer_Swapping_%28Instrument _Cluster%29) webpage for instructions to program secondhand dash.

ledojo
21st February, 2012, 11:19 PM
Very good info! Looks like I need to do a mileage correction afterwards--RT says "you will not be able to change the mileage of a cluster that has more than 100 km on the odometer."

tranzavanza
22nd February, 2012, 06:25 AM
I have a cluster from a 2003 Audi A4 (Cabriolet?). Anyhow, It was dropped off with a problem stating the Tachometer and Speedometer were in-op.

3.0L, Automatic, gasoline, US-model.

I opened it up. There's a NEC mcu. I got dump from 24c08.

I was wondering maybe this was a failed correction via OBD? And somehow something was corrupted?

Any chance that the 24c08 dump could correct problem? Or, must the NEC be read/corrected.

Note: This is something I'm just experimenting with to learn--If anyone is willing to point me in the right direction or even share their experience--That'd be great, but totally understood if not.

(btw, I have no pro tools for this as this is not usual work for me. I have UUSP, VCDS, and have installed the VAG eeprom Programmer, but have zero experience in this field. I also have Digimaster II, but didn't see anything for the NEC offhand. Not sure if any other tools worth mentioning. Again, just trying to learn something from this is all)

Thank you all in advance.

Your digimaster 2 can read some NEC. look for it under the programmer/cpu programmer/NEC. You should have the NEC adapter and the 14wire ribbon connector.

ledojo
22nd February, 2012, 07:44 PM
@tranzavanza I noticed the adapters before--never had a need to use, but I will double-check as my Ross-Tech cable did not work with the VAG eeprom programmer.

Still, I need to figure out how to get the VAG eeprom programmer to work. For two reasons. 1)I need to get the PINs. And, 2) I need to correct mileage with the new cluster.

From the other post about VAG eeprom programmer, it appears the Ross-Tech should work. It came with a RT dll, but I copied over my current one also and neither worked. Something like "No ECU"...

OR... This is something I was wondering. Everything on the old cluster appears to work--just not 'coded' properly. I'm thinking about doing some research on Ross-Tech site and maybe if I go through coding process, all will be well? Anyone have any experience and can tell me if this is even worth a try?

Last note. I'm in the Los Angeles area and if someone is mobile would like to do this as a job, PM me and I'll give you the info.

ledojo
23rd February, 2012, 12:42 AM
Just ordered a KKL cable... Hope it gets here soon enough.