NefMoto

Thank you to anyone who can contribute to this thread in advance, but I'm trying to confirm with what I believe to be correct about the ME7_95040 EEPROM program, just so I can better understand the conditions where it can be used:
 
It has the ability to read 95040 eeproms through the OBD interface/port using a dumb KKL cable while ECU is still installed (intent was to create an easy backup alternative from having to remove the ECU from the vehicle)
 
It has the ability to read the 95040 eeproms while on the bench using OBD protocol
(with an adequate power/data bench setup provided)
 
It can only write to the 95040 eeproms while on the bench in "boot" mode.
(immobilizer cloning/immobilizer defeat)
 
I've come across the cli "--SKC" option which is essentially the reason I'm attempting to better understand the program, but I feel like I'm missing a component of it. I've been able to use NEFMOTO to pull down my binary with a little bit of "FTDI driver" jockey-ing, and baud rate adjustment, and I've also been able to get VCDS lite to communicate, but I'm still unable to get ME7_95040 to initiate a connection while the ECU is in the car. Am I confused; should I be creating less forum posts, and be focusing more on creating a bench setup. I really just want to get my SKC pin at the moment for key adaptation, I figure I’ll learn the rest as I go.
 
Is it possible my ECU doesn’t have the 95040 EEPROM?

ECU hard 0261207939
ECU soft 1037366446
ECU Part 8E0909018A
 
no matter what I do the program returns error
"Initiating communication ... FAIL. (error=0x01)"

Is not working on all installed in car ecus.
In that case perhaps you have to use it via bootmode to read your eeprom.

You do have a 95040 in that box.

As the Prof said it doesn't always work in the car. Your best bet is to bench it. The error you list is a general one so I can't really help other than that sorry.

Are you telling the eeprom program what port the cable is using?

You have to specify what port with the option -p (ie. p1 or p2)
Just use the device manager to see what port the cable is using and add that option. See if that fixes it.

yep, I've attempted:

me7_95040 --OBD -r -p 3 test.bin
me7_95040 --OBD --SKC -p3 --screen

The only thing that might be contributing to the issue is that I'm running it on a VirtualBOX WinXP session, I'll eliminate that variable next.

All wrong!


Works fine on VB

Use the following switch

Me7( name of 95040 prog) -p ( comport cable is attached to ) -b 10400 -r x.bin

So from dis command it looks like

Me7 -p 2 -b 10400 -r Immo.bin

Or for writing

Me7 -p 2 -b 10400 -w Immo.bin

This has to be in boot mode on the bench harness

thanks littco, I'll give it a try; so I don't need to specify OBD protocol? and the baud rate appears to be set to 10400 by default, do I also need to force this speed as well?

You are correct, anything set to default that relates to your setup you can leave. Thus if you are on comport 2 and Baud 10400 then you can just run me7 -r x.bin etc

I was just stating the -p and -b switch to show you don't need the --obd and --skc..