|
Title: Cluster swap S4 B5 Australian immo3 Post by: bainos on November 15, 2018, 04:12:26 AM Hi all, first time posting on this site and somewhat new to this type of thing. Some background on the problem; So long story short I fried my Australian spec (i think this means immo 3) 2001 S4 B5 cluster (8D0 920 933D), it was pretty much on fire and part of the cluster circuit board is completely toasted along with a number of pins on the blue plug it will never be able to be used again (I was lucky to avoid a real fire inside the car). I have sourced another Australian s4 b5 cluster (8D0920930F) however the problem I am having is when i plug in the new cluster I have an immobilizer warning light that flashes whenever the car is on and I have several codes in VCDS that cannot be cleared.
I had someone desolder the EEPROM chip (93LC86) from my dead cluster and read it as it looked unaffected by the fire in the hope that I was able to get the SKC from it, however I am unsure that the file contains the SKC or if this was even the correct chip to read to find it. I am under the impression that I need to change the SKC of my new cluster to that of my old cluster and this should fix my immobilizer flashing light and the VCDS errors listed below? Further information that may be of use: - Ecu was originally an "N-Box" and has since been re-flashed to an "M-box" with multiple flash tune files (in the form of tune revisions) loaded on since being loaded with an M-box file. The ECU tune is immo defeated and I am able to start and drive the car with the cluster plugged in or not at all. Faults found in VCDS that I am unable to clear (they return upon clearing them): in the ECU (1) there is: 18058: Power train Data Bus: Missing Message From Instrument Cluster P1650 - 35-00 - - in the instrument (17) there is: 01176 - Key 65-10 - Unauthorized - Intermittent 01177 - Engine Control Unit 49-00 - No Communications 01300 - Control Module for Navigation with CD-Rom (J401) 49-10 - No Communication - Intermittent I have attached the cluster dump file from the EEPROM chip of my dead cluster, hopefully someone understands this better than I do. Title: Re: Cluster swap S4 B5 Australian immo3 Post by: macxxx on November 16, 2018, 12:52:11 AM Upload the dump of your new cluster
If you have a kkl cable then you can use Vagepprom programeer to read ir by obd Title: Re: Cluster swap S4 B5 Australian immo3 Post by: bainos on December 08, 2018, 04:25:11 AM Sorry about the long reply time, the cluster had to be sent away to have a ColourMFA installed so I was waiting for that before I could get a dump of the new cluster, however here it is finally.
Title: Re: Cluster swap S4 B5 Australian immo3 Post by: bainos on January 11, 2019, 03:30:48 AM Anyone able to shed some light on this?
Sent from my Pixel 3 using Tapatalk Title: Re: Cluster swap S4 B5 Australian immo3 Post by: macxxx on January 11, 2019, 04:26:14 AM I will take a look at it in the evening ( it's 12.00am in PL right know )
Title: Re: Cluster swap S4 B5 Australian immo3 Post by: macxxx on January 11, 2019, 12:47:09 PM write this one to your cluster , the immo light shoul dissapear ;)
Title: Re: Cluster swap S4 B5 Australian immo3 Post by: bainos on January 12, 2019, 06:39:01 AM Massive thanks, that fixed it along with all my associated fault codes. If it's possible could you explain what you did?
Sent from my Pixel 3 using Tapatalk Title: Re: Cluster swap S4 B5 Australian immo3 Post by: macxxx on January 12, 2019, 06:42:01 AM Copied immo part from your old to new cluster , and corrected adaptation of channel 62 ( from 4 to 0 like in the old cluster )
Title: Re: Cluster swap S4 B5 Australian immo3 Post by: bainos on January 12, 2019, 06:43:40 AM Which lines corresponded to the immo part?
Sent from my Pixel 3 using Tapatalk Title: Re: Cluster swap S4 B5 Australian immo3 Post by: macxxx on January 12, 2019, 06:45:04 AM Compare in hex editor what i did ( the old cluster dump read by programeer is swap byte ;) )
|