[pawel7924]

I've got a little problem with Micronas CDC3217G+24c32
Dash CPU was burned when Dash was tested on table - no communication
New dash was the same HW/SW other data was the same

I've got dump eeprom of micronas (dump org.bin) (size 4kb - readed via xprog) + eeprom 24c32 (24c32 org.bin) of old tacho

I've got eeprom of micronas in new dash (dump new.bin) (size 4kb - readed via xprog)

Could sb check it is correct ?

I made procedure
1. decrypt 24c32 using dump of micronas (old tacho) (decrypt.bin)
2. encrypt 24c32 using dump of eeprom (new tacho) (encrypt.bin)

I haven't any tool to check it ... could sb look to files is ok or not ...

24c32 org.zip
File Type:
Downloaded:	20 times
Size:	1.43 KB

[23Andi23]

You can not decrypt old eeprom with new flash
If you want to copy immo from old to new dash upload EEprom 24c32 + Micronas Flash from old one and EEprom 24c32 and Flash of new Dash

You only read eeprom you need flash file CDC3217

[torelettrauto]

Brand/Model of car : VW Caddy 1.9TDI
- Year of car : 2008
- Feature in relation : Change cluster with Micronas.
- Version of FVDI : FVDI V21
- Result : Ok, very easy if you know the trick
1: Put spare cluster to car and ignition on, make virgin, turn off ignition.
2: Put back original cluster to car and ignition on, read Immo Data, eeprom and read mileage. Don't turn off ignition.
3: Let ignition stays on and take out original cluster and put spare cluster to car, write immo data, eeprom and recalibrate mileage.
4: Now you can reset cluster and the magic have happend.
5: Turn off ignition and wait 30secound, now you can fire up car.

[pawel7924]

there is no original flash ... but yesterday I made some test
tacho wake up ...

Procedure :
1. Make backup of new tacho cdc3217G flash and 24c32 (backup)
2. copy memory 24c32 from old to new
3. put tacho into car .. display DEF and km 0 ... but VIN number is OK, tacho has communication
4. make immo off in EDC16 (via X-TOOL)
5. by FVDI - erase errors
6. by FVDI - try read tacho data - display IMMO DATA is corrupted ...
7. by FVDI - add new key procedure ... FVDI app display IMMO Data is corrupted ... "do you want continue .. " yes of corse .. FVDI ask "Do you want to flash tacho" , yes ... and ... in this moment CS of component was written to tacho .. key wasn't aded but I've got new tacho with VIN rewrited and CS rewrited without online procedure ...
8. by FVDI I made tacho calibration ... km / trip counter shows ok ...

tacho works ok ... NO DEF/ SAFE

Problems to solve
1. ABS lost his coding (ABS and Power Steering didn't work)
2. Comfort module lost his coding... (Electric window didn't work)

I'm looking for information how to correctly code this modules, anybody could help ?

[raffy haddad]

as a bro on this forum asked me what fvdi = to ????????
and his answer was

f......g vehicle destroyer interface
-D
regards