-
Installing used replacement ECU in 2002 Audi TT
Hi everyone,
I have a 2002 Audi TT 225 that I am installing a 3.2 in.
I purchased the TT mk1 3.2 ECU, part 022906032FK, along with the necessary engine wiring harnesses. It's a ME7.1.1G ECU.
I have the original 1.8T ECU sitting around, and the car still has the original cluster and keys installed
Based on the Ross-Tech Immo3 ECU swap instructions page, I understand that I need to get the PIN for the CAR (cluster) as well as the "new to me" 3.2 ECU. So, using Vagtacho and VagCommander, I got both PINs.
I need to connect to the Engine controller (ECU), login with its PIN, then go to adaptation channel 050 and give it the car/cluster's PIN.
However, unlike the Ross-Tech instructions, I don't have a channel 11 in my engine controller for Login (it's Coding II), but I have Security Access (16). the PIN I pulled from the ECU was 7102, so I enter 07102 and click Do It, but it responds telling me the controller refused the key, error 35 - Invalid key. Then I'm locked out for 10 minutes.
Instruments measuring blocks 22-24 show:
1, 1, 1, 2
1, 1, 1, 6.0
0.0, 0.0, 0.0, 0.0
Which I assume means that the cluster half of the immobilizer is happy. But the car/key light flashes in the cluster, and the engine shuts off after a second.
Posted the ECU eeprom dump on facebook and somebody confirmed that the pin I was trying was accurate for the ECU. What else could I be missing here?
-
Update - it's now clear after watching the Immo 3 ECU swap VIDEO that you actually click "Coding II" and enter the PIN THERE to gain access. So I do that, and it's accepted, but once I enter the new pin in adaptation channel 50, I get "System Not OK" instead of the VIN/ IMMO ID populating.
Auto scan:
Code:
Wednesday,28,August,2019,15:23:27:10300
VCDS -- Windows Based VAG/VAS Emulator Running on Windows XP x86(VirtualBox)
VCDS Version 19.6.1.0
Data version: 20190529 DS308.0
www.Ross-Tech.com
VIN: TRUWF28N051004853 License Plate:
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Chassis Type: 8N (8N - Audi TT (1999 > 2007))
Scan: 01 02 03 08 15 17 22 35 37 45 55 56 76 77
VIN: TRUWF28N051004853
-------------------------------------------------------------------------------
Address 01: Engine Labels: 022-906-032-BDB.lbl
Part No SW: 022 906 032 FK HW: 0
Component: MOTRONIC ME7.1.1G 6439
Revision: 00000000 Serial number: AUZ5Z0D5306039
Coding: 0000112
Shop #: WSC 54321 321 54321
VCID: 59B3AB1F93314E87BE-5123
1 Fault Found:
28773 - No Communication with Transmission Control Module
U0101 - 004 -
Readiness: 0110 1101
-------------------------------------------------------------------------------
Address 03: ABS Brakes Labels: 8N0-907-379-MK20-E.clb
Part No: 8N0 907 379 E
Component: ESP 20 CAN V005
Coding: 18446
Shop #: WSC 01236
VCID: 3E7918833A5F89BFAB-4AE5
1 Fault Found:
01315 - Transmission Control Module
49-00 - No Communications
-------------------------------------------------------------------------------
Address 08: Auto HVAC Labels: 8N0-820-043.lbl
Part No: 8N0 820 043 A
Component: TT-KLIMAVOLLAUTOMAT D03
Coding: 00140
Shop #: WSC 01236
VCID: 2855DEDBC8DB270FF1-2573
No fault code found.
-------------------------------------------------------------------------------
Address 15: Airbags Labels: 8N0-959-655.lbl
Part No: 8N0 959 655 A
Component: Airbag Front+Seite 5000
Coding: 01103
Shop #: WSC 01236
VCID: 3E7918833A5F89BFAB-5141
No fault code found.
-------------------------------------------------------------------------------
Address 17: Instruments Labels: 8Nx-920-xxx-17.lbl
Part No: 8N1 920 980
Component: KOMBI+WEGFAHRS. M73 D02
Coding: 07262
Shop #: WSC 06442
VCID: 73EFF9B7419D14D794-4AFF
TRUWT28N621005879 AUZ5Z0A7010001
No Faults Found
or DTCs not supported by controller
or a communication error occurred
-------------------------------------------------------------------------------
Address 22: AWD Labels: 02D-900-554.lbl
Part No: 02D 900 554 B
Component: HALDEX LSC ECC 0006
VCID: 1F47C5079D95E0B780-4AE5
No fault code found.
-------------------------------------------------------------------------------
Address 35: Centr. Locks Labels:. 8Nx-962-267.lbl
Part No: 8N8 962 267 A
Component: Central Lock/Alarm D06
Coding: 15884
Shop #: WSC 06442
VCID: 3F8765873D5580B7A0-4EE9
No fault code found.
-------------------------------------------------------------------------------
Address 45: Inter. Monitor Labels: 8E0-951-177.lbl
Part No: 8N8 951 177
Component: Innenraumueberw. D09
Coding: 00001
Shop #: WSC 00000
VCID: 7CFDD28B6CC35BAFC5-517B
1 Fault Found:
01463 - Alarm triggered by Sensor for anti-theft alarm System
35-00 - -
-------------------------------------------------------------------------------
Address 55: Headlight Range Labels: 4B0-907-357-AUT.lbl
Part No: 4B0 907 357
Component: LEUCHTWEITEREGLER D004
Coding: 00010
Shop #: WSC 01236
VCID: 65CB97EFFF49FA670A-5199
2 Faults Found:
01538 - Motors for Headlight Range Adjustment (V48) / (V49)
29-00 - Short to Ground
00774 - Level Control System Sensor; Rear Left (G76)
31-00 - Open or Short to Ground
End-------------------------(Elapsed Time: 03:26)---------------------------
Last edited by Boki Ar; 08-28-2019 at 04:03 PM.
Reason: [Code] Tags
-
VCDS Distributor
Been there?
http://wiki.ross-tech.com/wiki/index...I_ECU_Swapping
DaveLinger: Update - it's now clear after watching the Immo 3
ECU swap VIDEO that you actually click "Coding II" and enter the PIN THERE to gain access. So I do that, and it's accepted...
Now:
[Adaptation - 10]
Enter 050 in "Channel Number".
[Read]
For the following procedure, use the PIN of the ORIGINAL (OLD) ECU.
-
Originally Posted by
Boki Ar
Yes, I was going based on this page and the corresponding video. The PIN for my "new to me" used 3.2 ECU is 7102, and the PIN for my car's original cluster is 6454. I want to adapt the "used" ECU to my existing/old cluster.
So I start VCDS, go to the engine controller, pick Coding II - 11, enter 07102 as the pin, it says the pin was accepted.
I go back, go to "Adaptation - 10", go to channel 50, click "Read", the text field shows "PIN ?". I clear the default value, enter 06454, and click "Test". The fields change to say "Wait", then to "System Not OK". It should show the VIN/IMMOID from the cluster.
My understanding is the PIN from the cluster would be the same as the pin from the OLD ECU, but tomorrow I can try pulling the PIN from the old ECU to ensure it's 6454, like the cluster.
-
Benevolent Dictator
Since this thread involves an engine and ECU that does not belong in the car, moving to Retrofits.
My recollection is that on KWP-2000 ECUs, the PIN code is entered via Security Access, not Coding-II, and if it is not accepted by the ECU, then I am skeptical that it is correct.
-Uwe-
The engineering problems are likely insurmountable. It would be like proposing to land a rocket booster section on a barge floating in the middle of the ocean.
-
Originally Posted by
Uwe
Since this thread involves an engine and
ECU that does not belong in the car, moving to Retrofits.
My recollection is that on KWP-2000 ECUs, the PIN code is entered via Security Access, not Coding-II, and if it is not accepted by the
ECU, then I am skeptical that it is correct.
-Uwe-
I was trying access via Security Access all morning - couldn't get in, and when I'd go to Adaptation channel 50, it would say Disabled. But when I login via Coding II, it is accepted and Adaptation channel 50 says "PIN ?" as it should. So I'm sure I'm logging in correctly.
-
Update.
I know I have the right new (used) ECU pin because when I login via Coding II - 11, it tells me the control module has accepted my login, and when I subsequently go to Adaptation channel 50, the text readout says "PIN ?". If I am not logged in, it says "Disabled".
I know I have the right old ECU/cluster PIN because when I enter any wrong pin in adaptation channel 50 on the Engine Controller and click Test, it says "Wait" then returns to "PIN ?", whereas when I enter the RIGHT pin in the same box and click Test, it says "Wait" then "System Not OK".
So clearly (IMO) I have the right pins. One guy online said this won't work because the ECU is immo4 and the cluster is immo3, but that can't be right because the Engine controller doesn't work anything like ross-tech's immo4 pages show - it works just like the immo3 pages show.
Is it possible the car/cluster (MY 2002) are immo2?
-
Benevolent Dictator
No, the cluster is not Immo-2, it is definitely Immo-3 because it shows the car's VIN.
What car is the ECU from? Show us what is in MVB 081 in the ECU?
-Uwe-
The engineering problems are likely insurmountable. It would be like proposing to land a rocket booster section on a barge floating in the middle of the ocean.
-
Originally Posted by
Uwe
No, the cluster is not Immo-2, it is definitely Immo-3 because it shows the car's VIN.
What car is the
ECU from? Show us what is in
MVB 081 in the
ECU?
-Uwe-
The ECU is from a 2005 Audi TT 3.2
I "gave up" today and paid $55 for an ebay guy to disable the immobilizer on the ECU and ship it back to me, so no further help here is necessary. (I did lots of googling for the Immo 3 "System not ready" error and the only way I ever saw anyone fix the immo pairing was via eeprom manipulation and re-writing)
HOWEVER, I did take a screenshot of MB 081 on the ECU yesterday, so here's that - 
-
Post Thanks / Like - 2 Likes
-
Benevolent Dictator
So the donor car is a 2005. It's entirely possible that there's some incompatibility between that and the 2002 cluster.
-Uwe-
The engineering problems are likely insurmountable. It would be like proposing to land a rocket booster section on a barge floating in the middle of the ocean.
Reply With Quote