Pages: [1] 2
Author Topic: Audi B5 dash and ECU swap fail Immo2 to immo2 ( i think)  (Read 22398 times)
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« on: September 14, 2014, 09:48:12 AM »

it's taken me ages to find this little gem of info , I just realised it won't work on immo2 after spending ages trying to virginise my ecu and dash with new rfid chips.

Biggest problem for me is i dont have the immo tag from the original dash as i have upgaded to a later dash pod and set it to immo2 on adaption channel 60.

I am struggling to edit in hex as i'm dead old,LOL

Previous cluster saw the keys but the me7.5 ecu that i changed to over m5.92 had to de immo'd to allow it to start, i'd ideally like to get it all paired up and an immo working now i have later ecu and dash.


I have gone from m5.92 ECU to me7.5
and upgraded dash to a compatible( i think) with either immo2 or 3) dash
I'd like to resynch it all if possible

Any help anyone can give would be appreciated
The dash i think is not allowing the keys to synch because of the modded esquare( immo off) on the ecu but even using the virgin file the dash retains the information it managed to slurp in on first connection, so i have no immo id to add even if i could edit the vin in to the dash
I have the SKC for the dash and i think for the ecu, although that chucks me out.

it wont adapt the keys it says command not accepted in VagTacho and just errors in VCDS

Sorry for the disjointed nature, i am trying to keep my little one from mashing buttons

I tried the tuner wizard and turboat's excellent tools
« Last Edit: September 14, 2014, 10:35:39 AM by byzan a4 » Logged
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« Reply #1 on: September 15, 2014, 12:11:04 PM »

the dash is showing a status of 6 as in already matched up. I wonder if there is something i can do to fix that
Logged
ddillenger
Moderator
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #2 on: September 15, 2014, 12:20:56 PM »

the dash is showing a status of 6 as in already matched up. I wonder if there is something i can do to fix that

What's the part number on that ME7.5 ecu? The 032DL and narrowband ecus were immo2, would make pairing easier.
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
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« Reply #3 on: September 15, 2014, 01:40:56 PM »

8N0 906 018 H ecu number flash tuned file and 8D0 920 980G dash. The dash thinks it's immo3 in vageeprom but i set it to immo2 using block 60 of dash.

How can i set the dash to status to allow it to take synching

Logged
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« Reply #4 on: September 16, 2014, 01:33:52 AM »

I'm going to try and add an immo on esq as posted by yourself for Cyril but change id to match ecu . See how that ğoes. I'm sure it's unlocking the dash that needs doing I just cannot find anything regarding it.
Logged
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« Reply #5 on: September 17, 2014, 01:13:52 PM »

Still stuck.  Need to make dash allow itself to adapt. Any tips
Logged
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« Reply #6 on: September 20, 2014, 06:11:08 AM »

Looks like an immobiliser defeat and gaffer tape to hide flashing light. I cannot for the life of me make them adapt
Logged
turboat
Hero Member
*****

Karma: +45/-3
Offline Offline

Posts: 619


« Reply #7 on: September 20, 2014, 12:52:40 PM »

Would like to help, but never tried this and not got an immo2 ecu to try adapting.

I couldn't get a vrs cluster to adapt to an 032hn ecu, ended up pairing them manually by cloning the data and writing it back.

What is the error you're getting in Vcds?
Logged
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« Reply #8 on: September 20, 2014, 01:16:04 PM »

Dash or ecu code?
Logged
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« Reply #9 on: September 20, 2014, 01:21:19 PM »

Ecu has a bunch because I have no engine in atm.  I cannot pair them manually as I don't have the data due to the upgrades.  Who said car modifications are easy
Logged
turboat
Hero Member
*****

Karma: +45/-3
Offline Offline

Posts: 619


« Reply #10 on: September 20, 2014, 02:18:43 PM »

I meant the error when you tried to adapt the cluster to the ecu.
Logged
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« Reply #11 on: September 20, 2014, 03:36:20 PM »

It just says error.  Ecu and dash say no comms but wiring perfect.  I did read some errors can lock ecu out till cleared bit till engine in I can't clear them all
Logged
turboat
Hero Member
*****

Karma: +45/-3
Offline Offline

Posts: 619


« Reply #12 on: September 21, 2014, 01:28:56 AM »

Tbh I'd immo off until it's in, then worry about it. I drove mine around with the immo light flashing for a couple of weeks!
Logged
byzan a4
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 73


« Reply #13 on: September 21, 2014, 02:02:28 AM »

Tbh I'd immo off until it's in, then worry about it. I drove mine around with the immo light flashing for a couple of weeks!
yeah I guess you are right. Was just wanting it all right when engine went in. Lol I'll report back then.
Logged
littco
Hero Member
*****

Karma: +52/-7
Offline Offline

Posts: 903


« Reply #14 on: September 21, 2014, 04:22:54 AM »

yeah I guess you are right. Was just wanting it all right when engine went in. Lol I'll report back then.

Honestly your best bet. In fact only bet is to immo defeat and remove or tape over the led.. Some ecus and dash pods won't code to each other. It's an eeprom issue as recently fitted an s3 dash to an a3 with a 018hn ecu.. should work but wouldn't until a 018h eeprom was loaded onto the ecu same as the dash fitted..



Logged
Pages: [1] 2
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.02 seconds with 17 queries. (Pretty URLs adds 0s, 0q)