Pages: [1]
Author Topic: Immo 3 Ecu and Cluster matching?  (Read 9629 times)
aef
Hero Member
*****

Karma: +77/-49
Offline Offline

Posts: 1679


« on: January 23, 2022, 09:51:12 AM »

Hi,

car was pre facelift immo2 1.8t Golf Mark4 enginecode ARZ with bosch cluster.
Car was upgraded to wideband using a bam/amk ecu and immo off. Due to the matching cluster and keys the cluster was clean, no immo warning light.
Now the cluster was upgraded to vdo immo3 and immo warning is flashing. This is what im trying to fix with your help.

Is there a way to match cluster and ecu directly in eeprom? This way i would be able to learn new key transponders.

Another option would be to transfer keys from old immo2 bosch cluster to new immo3 cluster?

Last option would be to dismantel cluster to kill the immo warning light manually.

My first attempt was to write the pin from cluster into the ecu eeprom but this is not enough to match both components.


edit:
might found something
DashDumpedit is able to open the me7 eeprom and insert relevant parts into the vdo immo3 cluster eeprom
https://www.drive2.ru/l/471768829593126099/
just ordered some id48 transponders and will try this at first.
anyway your input is warmly welcome

« Last Edit: January 23, 2022, 10:05:36 AM by aef » Logged
macxxx
Sr. Member
****

Karma: +30/-1
Offline Offline

Posts: 498


« Reply #1 on: January 23, 2022, 11:41:28 AM »

I think its the only way and it will work.

As I remember there was some option in Epprom of VW cluster to disable Immo notification on display  , but I maybe wrong.
Logged
Sandstorm3k
Sr. Member
****

Karma: +10/-14
Offline Offline

Posts: 402



« Reply #2 on: January 23, 2022, 05:26:24 PM »

You can match the immo data from the cluster & eeprom with eepromtool_04

http://nefariousmotorsports.com/forum/index.php?topic=6134.0

Rather easy, proper tool Smiley

Logged
elektronik13
Full Member
***

Karma: +11/-37
Offline Offline

Posts: 207


« Reply #3 on: January 24, 2022, 01:31:36 PM »

Hi,

car was pre facelift immo2 1.8t Golf Mark4 enginecode ARZ with bosch cluster.
Car was upgraded to wideband using a bam/amk ecu and immo off. Due to the matching cluster and keys the cluster was clean, no immo warning light.
Now the cluster was upgraded to vdo immo3 and immo warning is flashing. This is what im trying to fix with your help.

Is there a way to match cluster and ecu directly in eeprom? This way i would be able to learn new key transponders.

Another option would be to transfer keys from old immo2 bosch cluster to new immo3 cluster?

Last option would be to dismantel cluster to kill the immo warning light manually.

My first attempt was to write the pin from cluster into the ecu eeprom but this is not enough to match both components.


edit:
might found something
DashDumpedit is able to open the me7 eeprom and insert relevant parts into the vdo immo3 cluster eeprom
https://www.drive2.ru/l/471768829593126099/
just ordered some id48 transponders and will try this at first.
anyway your input is warmly welcome



enter the VIN of your car here
Logged
aef
Hero Member
*****

Karma: +77/-49
Offline Offline

Posts: 1679


« Reply #4 on: January 30, 2022, 10:31:22 AM »

solution:

I extracted the Immo 3 Data from the me7.5 eeprom with dashdumpedit or eepromtool and insert it to the vdo cluster dump.
By this the ecu is matched to the cluster. only thing you have to do then is to learn the key(s) which is no problem because you can re-use the immo2 transponder.

i previously entered the cars vin into the eeprom and now ecu and cluster is dtc free and looks like oem with correct vin.
Logged
Iron59
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 8


« Reply #5 on: January 03, 2026, 02:26:39 PM »

Hi,

i have the same problem now.

My Car is a immo2 with immo2-ECU and immo2-cluster (Magneti Marelli/Jaeger). I changed the ecu to an another immo2-ecu with immo-off. So no immo flash in the cluster, because cluster and keys are matched.

So now, i matched my immo2-ecu with immo-off with a new immo3-cluster (VDO). I matched VIN, SKC and Immo-ID with AudiDashEdit (ECU to Cluster). But immo still flashing in cluster. I think, i need to match my keys with the new cluster, so like you did. But i can't - VCDS always send FAILURE.

- Is this, because my ECU is immo-off? Do i need to turn immo on? Is that the only solution? I’d rather not go down that route, because then I’d have to remove the ECU and bench-flash it using the boot pin

- So i read the bin from my old immo2-cluster, so i tried to transfer the key data to the new immo3-cluster. But AudiDashUp can't find any keydata (and no other valid data, read was with VAG K+Commander) . Can somebody help me here?

- i also have now in the cluster this failure-codes:
01177 - Engine control unit         49-00 - no communication
01304 - Radio         49-00 - no communication
01311 - Data bus information        37-10 - defect - Sporadic
Is this a problem? I had the Data bus information failure also in my ecu, but i disabled this here.

Best thanks in advance! I hope someone can help me, i am frustrated...
Logged
updatelee
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 3


« Reply #6 on: January 04, 2026, 05:32:24 PM »

The immobilizer light flashes because the keys aren’t matched, immo off with matching keys and you’ll get no light blinking.

Logged
Pages: [1]
  Print  
 
Jump to:  

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