Not used/tried boot mode yet. Until I can get simple data logging first I won't play further.

Euro box code 511D.

I also only have the cmd prompt open to try and read ECU info or even data logging.

I must be going crazy.  The me7_95040.exe program is running properly and is saying that the .bin file is saved - no obvious issues there.  But I cannot find the file that was supposedly saved.  It should be in the same folder as the .exe but it's not there.  I searched for the file as well, no luck.

Any ideas?

"current working directory"

No, it is the directory you are in when you run the .exe

Please provide a copy/paste of the dos box (including the output of the "dir" command after running the program). PLEASE DO NOT POST A SCREEN SHOT.

You can copy/paste text using the "mark" function.


Time to learn

http://dosprompt.info/

Command lines will always be relevant.

ME7_95040 v1.31
Allows to program ME7 ECU's EEPROM (95040).
This software needs a dumb serial to k-line cable for connection with the ecu.

Usage: me7_95040 [OPTIONS]... [FILE]...
 -p, --comport COMPORT     Set COMPORT.
 -b, --baudrate BAUDRATE   Set BAUDRATE, default: 10400.
                           Allowed baud rates: 9600, 10400, 19200, 57600.
     --OBD                 Use this option to read the EEPROM over OBD port.
                           Currently, only read is supported in OBD mode.
     --bootmode            Use this option to program the EEPROM in boot mode.
 -r, --read                Save EEPROM contents to file.
 -w, --write               Write file to EEPROM.
 -s, --screen              Print EEPROM contents to screen.
     --help                Display this help and exit.

Usage example:
   Read EEPROM over OBD port:         $ me7_95040 --OBD -r -p 1 95040.bin
   Print EEPROM contents to srcreen:  $ me7_95040 --OBD -p1 --screen
   Write file to EEPROM in bootmode:  $ me7_95040 --bootmode -wp1 95040.bin

It's free for hobby use.
This software is provided "as is", with NO WARRANTY.
email: agv.tuning@gmail.com

C:\WINDOWS\system32>"C:\Users\Fred\Desktop\A4 USP\bin\me7_95040.exe" --OBD -r -p
 4 readout.bin
Ver: 1.31
Com Port: 4
Baud Rate: 10400
Opening COM4 ... OK
Initiating communication ... OK
ECU ID response: 4Z7907551M
                 2.7l V6/5VT     G
                 0001
                 SoftCod: 06752, WSC: 27665
Reading EEPROM ............................................................... O
K
File saved
Closing COM4

Thanks for the tip.  I learned the cd prompt and have been navigating around.

Interesting point, changing absolutely nothing from what I was initially entering into the dos command, but using my older computer, I was able to read and save the file on the first try.

So there must be a safeguard in place on my current laptop.  I will now proceed to smash it with a large hammer of sorts.

Even when (using the cd command) I selected a different directory, i.e. C:\ECU\, it wouldn't save the bin files to the computer.

I'm logged in as an administrator on this computer as well.

Your original command:

C:\WINDOWS\system32>"C:\Users\Fred\Desktop\A4 USP\bin\me7_95040.exe" --OBD -r -p 4 readout.bin

try changing the saved filename at the end:

C:\WINDOWS\system32>"C:\Users\Fred\Desktop\A4 USP\bin\me7_95040.exe" --OBD -r -p 4 C:\readout.bin


* I'm not sure if that's what you said you did with the "c:\ECU" in your previous post. If that's what you tried ("C:\Users\Fred\Desktop\A4 USP\bin\me7_95040.exe" --OBD -r -p 4 C:\ECU\readout.bin)
then you might want to move the file me7_95040.exe also in that directory.

Then:

"C:\ECU\me7_95040.exe" --OBD -r -p 4 C:\ECU\readout.bin

Just to be safe, make sure your prompt says C:\ECU>

If not, the quickest way is to type (one command at the time)

cd\

cd ecu

The first (cd\) will go to the root of the drive (c:\), and the second command will go to the "ecu" folder.
From there, the command should work fine. Windows shouldn't block anything there.