NefMoto

How to correctly read ME 7.1.1?

K-Tag gives a message to choose as ME7.5.

if your PCB is same with foto ..... read like this

K-Tag has four options for ME7.1.1
1. Family 539
2. HW I Family 50
3. HW II Family 51
4. HW III Family 52

All the discs are different from my record.
The most similar disc appears in the HW I Family 50 option but then a message appears to select ME 7.5 HW I Family 48.

Why not just use galletto? Or immo off and port write on bench with kess

Read Galletto? Just boot the PIN 24 as in ME7.5?

need boot and cnf1...get a genuine tool.

Cnf1 needs to be grounded besides that yes it's the same as any other me7

So where should I connect the CNF1?

I have read it FLS, MPC, EEP, but all EEP is FFFFF...

ktag has cnf1 pin and boot pin and you have already answered your own question some posts above.

I understand that I should use HW I family 50 for my ECU PCB?
Where should I connect CNF1?


I read the FLS correctly, but I also want to read the EEP to have a full backup.

For users that have Ktag (non-oem versions) :

1. swap the eep of Ktag to Trasdata
2. Open Trasdata app, select ME7.5 1MB / F800BB layout
3. Wire the ECU using ME7.1 schematics, and ground 24 Pin of AM29F800 (for get into Bootmode).

You can now read without having Checksum error as KSuite does.

protocol 50 has no cnf1
protocol 53 has but i assume it is not your pcb as you have just posted random pics that don declare what you do have.

Ktag will automaticaly read the eeprom in boot mode on any case and will ask you to save everything seperatly and then you get mpc flash and eeprom.

Ktag usually detect wrong protocols so if it didn`t complain it should give you a complete backup of your ecu..

This is why you buy Genuine tools so they can help you(alientech) do what needs to be done and not confuse or waste everyone's time.

Now if you still can`t figure this out desolder the eeprom and read it with an eeprom reader, then you will have the eeprom too...

In the first post is a picture of my pcb.
My PCB is the most similar to Family 50.
That's why I read it as family 50.
K-Tag reads FLS, MPC, EEP, but EEP is empty FFFF.
I would like to know if this K-Tag can read EEP correctly. Do I have to use other hardware to read the EEP correctly?

gt-innovation thank you for your words.

I have X17 but he does not read ME7.1.1 ST10.

Ground cnf1, remove resistor if it won't go into bootmode and use galletto to read as any other me7. Keep cnf1 grounded the entire time and ground boot pin while on powerup only

out of interest: galletto will read eep?

No ktag will. Use version 2.45 works fine. The other option is just pull it off and put it in a burner to dump the read.

The correct eeprom was read by VAG Dash CAN via OBD.

Yes, VAG Dash CAN read eeprom via OBD correctly but... tryied this with old protocol? R32 st10 ecu is mixed ecu old style with MED9