|
adam-
|
 |
« on: November 19, 2014, 02:54:19 PM »
|
|
|
Hello again,
Got the clocks in, backlighting is changed and lit needles, MTE work as expected. Got an immo problem. And no; I don't fancy immo-ing off the ECU yet - I want it to work as factory.
Problem is, the clocks won't adapt. Used Turboats file to merge the two files so that now my VDO cluster reads the correct VIN (and immo data I hope?)
Still, logging in with my pin 06870 and trying to adapt Channel 50 just says Malfunction. It did say System not OK, but now it's Malfunction.
From another user:
I have found 7 Bytes in Motometer dump based on Bosh dump. Wink
There are adresses from 10 to 16 in dumps of 1J0920806 clusters by MM/Bosh.
Pasted these 7 bytes to vdo dump in 3 areas and after that key learning done successfully.
Loaded up the Motometer dump in OLS and can find in address 10 a repeating pattern of 7 bytes: FC 27 FA A4 AF 93 FE 70
Matching the windows, I copied this into the Bosch file, still no go.
Doesn't learn, and trying to adapt the key it saves the new key number and then reverts it back to 0.
Do I need a new RFID?
I know this is wordy, but I've tried to cover all the bases on my own without the stupid questions.
Thanks.
|
|
|
|
|
Logged
|
|
|
|
MK2-VRT
Full Member
Karma: +2/-10
 Offline
Posts: 131
|
|
« Reply #1 on: November 19, 2014, 03:08:42 PM »
|
|
|
Are the immo light from Old cluster in the speedo or tachometer ? And where from the new ?
|
|
|
|
|
Logged
|
|
|
|
|
adam-
|
|
« Reply #2 on: November 19, 2014, 03:12:56 PM »
|
|
|
Both in the speedo; as per immo3. Part numbers match up too!  ECU has been crossflashed though; I might try flashing over the original file and see how far that gets me. It doesn't overwrite the EEPROM so it shouldn't affect it? |
|
|
|
|
Logged
|
|
|
|
|
adam-
|
|
« Reply #3 on: November 20, 2014, 04:50:18 AM »
|
|
|
Attached is my original Bosch RB8 cluster dump - I don't know the location of the actual transponder keys.
The 95040 from my ECU and the cluster dump from my new VDO cluster.
Can get the cluster to show my VIN etc, and get it to know the new login code - which is 06870, but still no play.
If I knew where the key bytes were I'd copy it over, but I'm not too sure. That, and the cluster is a diesel one, so the revs are off - but I'll deal with that later!
|
|
|
|
|
Logged
|
|
|
|
MK2-VRT
Full Member
Karma: +2/-10
Offline
Posts: 131
|
|
« Reply #4 on: November 20, 2014, 07:47:30 AM »
|
|
|
Pin from RB8 : 06870 ( 24C08 Eeprom )
Pin from 946C : 01359 ( 93C86 Eeprom )
Both immo 3..
Test with the file in Att, load into the 946 cluster and try to adapt again.
Before, go to 19-can gateway, recode it, ( Not change it and only save ), after that, 17-instruments, 10-adaptation, ch 00, read and save.
Ignition off, ignition on, login with 06870, 10-adaptation, ch 50, login with 01359, ignition off, ignition on, 17-instruments, 10-adaptation, ch 21, put XXX new keys, save..
When he failes at ch 50, make a printscreen from measeringblocks 022 023 and 024
|
|
|
|
|
Logged
|
|
|
|
|
adam-
|
|
« Reply #5 on: November 20, 2014, 08:24:39 AM »
|
|
|
Tried all of that and exactly the same result - System Not OK.
Block 22 says the Key can be coded
Block 23 says immo status 6?
Block 24 says all the lockout times are 0.
|
|
|
|
|
Logged
|
|
|
|
MK2-VRT
Full Member
Karma: +2/-10
Offline
Posts: 131
|
|
« Reply #6 on: November 20, 2014, 08:33:07 AM »
|
|
|
What do you see more in 022 ?
Use new transponder and test again.
|
|
|
|
|
Logged
|
|
|
|
|
adam-
|
|
« Reply #7 on: November 20, 2014, 04:55:27 PM »
|
|
|
Will buy new transponders but wanted to keep the other ones - it says they can be coded though. I'm sure you can copy the data from the RB8 cluster though, I'm sure of it. Tried to sign up to http://www.gti-tdi.de/ because it seems like they really know their stuff on these, but registration is down for just now. If anyone knows anyone, can they pop them a mail, I'd like to get this sorted sooner rather than later. Thanks again! |
|
|
|
|
Logged
|
|
|
|
byzan a4
Full Member
Karma: +0/-1
Offline
Posts: 73
|
|
« Reply #8 on: December 13, 2014, 04:43:58 AM »
|
|
|
Intrigued myself. Similar issue to mine.
|
|
|
|
|
Logged
|
|
|
|
|
adam-
|
|
« Reply #9 on: December 13, 2014, 11:41:32 AM »
|
|
|
Managed to get the guy who had a similar problem on here to fix it.
He played with the dump, but still not sure what he's done. I was using vag k-commander to write to it, and I think that was half the problem. But the second write of his file and it worked.
Still have a coding issue error logged with the key, but it starts fine. Not convinced.
|
|
|
|
|
Logged
|
|
|
|
vampirelo
Jr. Member
Karma: +1/-1
Offline
Posts: 27
|
|
« Reply #10 on: January 23, 2015, 05:11:00 PM »
|
|
|
Managed to get the guy who had a similar problem on here to fix it.
He played with the dump, but still not sure what he's done. I was using vag k-commander to write to it, and I think that was half the problem. But the second write of his file and it worked.
Still have a coding issue error logged with the key, but it starts fine. Not convinced.
Not played - just simle dump works.  |
|
|
|
|
Logged
|
|
|
|
|
