EMD_Driver
Jr. Member
Karma: +0/-0
Offline
Posts: 28
|
|
« on: August 30, 2014, 08:43:20 AM »
|
|
|
Hi guys, I have a 2003 Jetta with IMMO3. I kept getting a K1:Short to ground and could not track it down. I could not access anything via the DLC. I decided to try another cluster and was suddenly able to access everything available. I figured that the K1 short must be in the cluster itself and decided to try swapping it for the one I picked up. This car is bone stock, so I figured it would be an easy swap. Not! I went through the entire RT swap procedure and it keeps hanging up, when I enter the PIN that I want to store in the replacement cluster. I'm hoping you guys can help shed some light on this for me, or that there might be something I missed. If this is the wrong forum, please forgive me. If there is any available software on this site that can help me out, please let me know. Here's a screen grab.. Note the fields "System" and "Not ok"
|
|
|
Logged
|
|
|
|
EMD_Driver
Jr. Member
Karma: +0/-0
Offline
Posts: 28
|
|
« Reply #1 on: August 30, 2014, 08:45:22 AM »
|
|
|
I forgot to mention... It was ArgDub's software, that made it possible to get the PIN from the ECU.. Thanks ArgDub!
|
|
|
Logged
|
|
|
|
k0mpresd
|
|
« Reply #2 on: August 30, 2014, 10:31:57 AM »
|
|
|
just swap e2p from ori cluster to new cluster.
|
|
|
Logged
|
|
|
|
Allabout
Full Member
Karma: +0/-2
Offline
Posts: 54
|
|
« Reply #3 on: August 30, 2014, 02:49:44 PM »
|
|
|
Have a look on Ross-Techs site Look into immo2 to immo3 cluster swap and also ECU swap.
This should provide you the answers you require. When you swap clusters, you need to resync all car keys as well.
|
|
|
Logged
|
|
|
|
EMD_Driver
Jr. Member
Karma: +0/-0
Offline
Posts: 28
|
|
« Reply #4 on: August 30, 2014, 06:05:54 PM »
|
|
|
I got some help from rand0mher0, in regards to changing the cluster dump of the replacement cluster. Here is what I started with: It has the old IMMO ID, SKC and VIN in it. Here's how it looks, after editing it with the new IMMO ID, SKC and VIN in it: Think it will work?
|
|
|
Logged
|
|
|
|
EMD_Driver
Jr. Member
Karma: +0/-0
Offline
Posts: 28
|
|
« Reply #5 on: August 30, 2014, 07:16:07 PM »
|
|
|
Ok... So I successfully changed the IMMO ID, SKC and VIN for the cluster. Trying to adapt the keys, however, just isn't working. Here's what VCDS is telling me:
Saturday,30,August,2014,21:56:06:14659 VCDS -- Windows Based VAG/VAS Emulator VCDS Version: 12.12.3.0 (x64) Data version: 20140822
VIN: 3VWSE69MX3M103749 License Plate: GREENMIDGET0830
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Address 17: Instruments Labels: 1J0-920-xx5-17.lbl Control Module Part Number: 1J0 920 906 J Component and/or Version: KOMBI+WEGFAHRSP VDO V64 Software Coding: 01232 Work Shop Code: WSC 00050 Additional Info: 3VWSE69MX3M103749 VWZ7Z0B6059414 VCID: 2F6738D0ED240F66327-5106 2 Faults Found:
01177 - Engine Control Unit 65-10 - Unauthorized - Intermittent 01179 - Incorrect Key Programming 35-00 - -
|
|
|
Logged
|
|
|
|
ddillenger
Moderator
Hero Member
Karma: +641/-21
Offline
Posts: 5640
|
|
« Reply #6 on: August 30, 2014, 07:32:56 PM »
|
|
|
There is a 4 byte immobilizer ID somewhere in that file that much match the ecu.
|
|
|
Logged
|
Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!
Email/Google chat: DDillenger84(at)gmail(dot)com
Email>PM
|
|
|
rand0mher0
Newbie
Karma: +0/-0
Offline
Posts: 15
|
|
« Reply #7 on: August 30, 2014, 07:44:42 PM »
|
|
|
Any idea where that is in the ECU?
EMD do you mind posting the ECU file?
|
|
|
Logged
|
|
|
|
EMD_Driver
Jr. Member
Karma: +0/-0
Offline
Posts: 28
|
|
« Reply #8 on: August 30, 2014, 07:48:37 PM »
|
|
|
Here ya go!
|
|
|
Logged
|
|
|
|
EMD_Driver
Jr. Member
Karma: +0/-0
Offline
Posts: 28
|
|
« Reply #9 on: August 30, 2014, 07:54:00 PM »
|
|
|
Just in case, here's the file I uploaded to the cluster...
|
|
|
Logged
|
|
|
|
ddillenger
Moderator
Hero Member
Karma: +641/-21
Offline
Posts: 5640
|
|
« Reply #10 on: August 30, 2014, 07:55:17 PM »
|
|
|
In the ecu it is right after the login code. (4 bytes)
|
|
|
Logged
|
Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!
Email/Google chat: DDillenger84(at)gmail(dot)com
Email>PM
|
|
|
rand0mher0
Newbie
Karma: +0/-0
Offline
Posts: 15
|
|
« Reply #11 on: August 30, 2014, 08:05:41 PM »
|
|
|
Ok, so in that ecu file the 4 bytes after the login is E7 F2 81 55 which decodes to 1434579687. Now I have no idea where that goes in the cluster file. I might need to go grab the eeprom off my ecu...
|
|
|
Logged
|
|
|
|
EMD_Driver
Jr. Member
Karma: +0/-0
Offline
Posts: 28
|
|
« Reply #12 on: August 30, 2014, 08:06:33 PM »
|
|
|
In the ecu it is right after the login code. (4 bytes)
The 4 bytes after the SKC are: E7 F2 81 55 Where does that need to go, in the cluster file?
|
|
|
Logged
|
|
|
|
digitalhippie
Full Member
Karma: +0/-5
Offline
Posts: 111
|
|
« Reply #13 on: August 30, 2014, 08:31:08 PM »
|
|
|
|
|
|
Logged
|
|
|
|
digitalhippie
Full Member
Karma: +0/-5
Offline
Posts: 111
|
|
« Reply #14 on: August 30, 2014, 08:32:46 PM »
|
|
|
Also, you're misunderstanding byte. Byte = 8bits = 1 character. So 4 bytes = 4 characters, not 8 like you posted.
|
|
|
Logged
|
|
|
|
|