Looking for help with MPSCAN and ECU identification

[adamsys]

Thanks Wayne!

I'm pretty sure that I have the FTDI cable set up correctly. I used FTProg to invert the signal. I also hooked up a loop back and get an echo on keystrokes in a terminal emulator.

I suppose that the first step is to get MPScan up and running. I have a hard to trace "check engine" light anyway.

So the text file posted as code early in this thread with the memory addresses, what file extension does that get? I suppose I could open all the files in the directory with Notepad and see what matches the structure. But if more than one file type has the same structure, I could easily get it wrong.

[wheming]

Adam those txt files that Morris posted are there to help in troubleshooting issues. They are files that get written with some data for the com port and the connection. So, It's not really of a concern other than to post them when things aren't working.
So try to connect to your ecu using mpscan. Post those .txt files if you have problems. Try to log something simple, just to verify the connection.