NefMoto

Hi,

So I have finally got my immo3 B5.5 FIS cluster which replaces my immo2 B5 MFA cluster :D

I have done the key matching, soft coding, distance to empty, welcome message and illuminated needles/dials. The cluster works perfectly.

However, as it is an immo3 cluster, it contains the VIN of the previous vehicle in the EEPROM. Now I know this isn't important as it doesn't affect the operation, but as I have the EEPROM dump and the ability to read/write to the cluster EEPROM I would like to change this VIN to my vehicle's VIN for completeness. Does anyone happen to know how I can do this?

Thanks,
James

have you tried to open eeprom with a hex editor?  ::)

Yes I have, but i'm not sure which addresses to change exactly. I'm also not sure if I will face any checksum issues or anything like that?

well then
use visualme7logger - tools - eeprom

Thanks for the info, the following may sound stupid and if so I'm sorry :D

 Would it be possible for you to briefly explain how to use the EEProm Tools in visualme7logger?

When I open it, I leave the EEProm Application Path to it's default (ME7_95040.exe) and then under Bin Path I select my EEPROM dump. Then I clicked Read (File) and I was presented with "INCORRECT FILE SIZE. EXPECTED 512 BYTES" under the VIN, SKC and Immobilise ID fields. I suspect it's because i'm using the wrong Application Path? Do I need a different path for the Cluster EEPROM vs the ECU or something? The EEPROM dump I opened is direct from my cluster and is the same one that it is currently using successfully...

Use a hex editor with a parallel ascii view like Neo hex editor or something like that. 

No checksum in that area of your cluster so don't worry about it.

Okay I can manage that but I thought the VIN was stored in 3 places, two of which are in the encrypted portion?

Also should I change the immobiliser ID to match my vehicle? I'm not sure if this ID is supposed to correspond to the cluster or the vehicle?

oh sorry
what a day, i thought you mean 95040 from ecu :)

Haha no problem! I thought as much when I started looking into visualme7logger, but at least I've extended my knowledge and now know something about ECU programming/tools

i am guessing you are changing the code on a 2nd hand cluster?

you need to match ALL data up so that is

SKC
VIN
IMMO

from the data of the ECU's EEPROM as they need to match. try finding "VAG EEPROM TOOL" that will be one of the easiest ways to edit your cluster's file

open up your emu's EEPROM so you can gather the relevant 3 pieces of information.

transfer them into the cluster's file. you should be able to tell what value you need in vag eeprom tool by moving the cursor so it is highlighting the beginning of the VIN/SKC/IMMO on the right hand side.

note you will be inputting hex values and not simply typing in your VIN. The characters on the right will change as you input the correct coding from your ECU file.

i was able to figure it out by reading "automan001" post

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

and check out my post here of when i bricked a cluster LOL

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

Thanks for your reply, yes it's for a 2nd hand cluster,  but as it's an immo3 cluster in an immo2 car it will not automatically learn the new vehicles details.

I understand I can change the visible values using a hex editor,  but what from I have read the VIN is stored at 3 locations in the EEPROM, only one of which is in the unencrypted part. How can I change the other two locations?

Thanks for that, his post will be very useful. However I'm still not clear on whether or not the VIN is in fact stored at 3 locations in the EEPROM, only one of which is in the unencrypted area? From what I have read this is the case and if so how can I change the other two references to the VIN?

Know I found out that we are talking about vw cluster ;)

I have made only Audi xxx920xxx clusters but it shouldn't be much more complicated...

I see, well this is a VW xxx920xxx cluster and I would have expected they would be the same tbh. We're the Audio cluster you have done immo3? And did you need to change the VIN in 3 places in the EEPROM?

Audi epprom is diffrent , vin in one place - i changed pin , immo id , immo code and vin and cluster works In a car just out of the box , the only thing i had  to do is add keys. But that was a swap into a immo3 car.

In immo2 car  just changed vin in the cluster after normal adaptation and adding keys.

Well the VW cluster just works without needing to change the VIN as it's an immo3 cluster in an immo2 car. The only reason I want to change the VIN is just for completeness, in reality this only shows when dumping the EEPROM or when connecting to the cluster through VAGCOM. I could change just the one reference to the VIN in the EEPROM (the unencrypted one) and this would mean in VAGCOM and the readable text from the EEPROM it would show the correct VIN, but I would have thought there should be a way to change the other two encrypted references somehow.

change the visible one ad let go , have a beer  ;D

I had a look at a vw 920 epprom - I see only one place with vin and immoID

if you want to make a comparison AUDI/VW i attached two dump here: http://nefariousmotorsports.com/forum/index.php?topic=11610.msg97115#msg97115

haha I probably should, I just assumed that someone would know that was all :P you see one visible location, but what about the encrypted area ;)

Where is the encrypted area? Could write your cluster part no.

Well i'm going by what I have read when I say there is an encrypted area and that there is 3 instances of the VIN. My cluster model is: 3B0 920 847 and I've attached the factory EEPROM dump for it.

Thanks :)

Okay so I figured I may as well finalise this thread and detail what I ended up doing. So firstly I cannot confirm whether there is in fact encrypted instances of the VIN/IMMO ID/SKC so as mccxxx said I decided to just change what I could see and forget about it.

I changed the three instances of the IMMO ID (these come one after the other in readable format if you have an editor that shows both ascii and hex).
I changed the three instances of the SKC (these come one after the other, straight after the IMMO ID, however they are byte swapped - if the hex shows 0A 15 then in the EEPROM it is written as 15 0A)
I changed the one instance of the VIN (this comes straight after the SKC)

Anyway after checking with VAGCOM the extra field of the 17 - Instruments menu shows the original IMMO ID and VIN of my car. Also the original SKC of my car works successfully as the login to 17 - Instruments.

Hope this may help someone else in need,
James

The skc is always a swap byte

Just to stir the pot.  ;)

Why not take a "used cluster" with different immo data.

-Read the stock eeprom from it.
-Put it in your car and adapt it with VCDS.
-Read out the new altered/adapted eeprom.
-open both eeproms in a hex editor and see what areas were changed.

The you will be able to determine is there are indeed more changes/encrypted areas then meets the eye.

It's a good idea and I wish I could do that, but the trouble is that my car is IMMO 2 and so I cannot do IMMO 3 cluster adaptation with my car. That's actually what I first tried to do when I got this IMMO 3 cluster as I was following the Rosstech instructions for matching the cluster to the car, then I realised as my car is IMMO 2 it wouldn't perform the matching (channel 50 doesn't exist in the adaptation menu).

Thanks for your suggestion :)

Error