MEMSAnalyser
------------

This program package is for analysing data from the MEMS1.6 ECU as fitted to early Rover engines.  The readmems.exe program was written by Colin Bourassa and I gratefully ackowledge his invaluable contribution to this package. 

It comes with a three example data files.  One from an early run I did in my car, which demonstrated I had a broken lambda sensor, one after I fitted a new senspr, and one from a log file produced by MEMDiag, an Android app.

INSTALLATION
=============
1.  Unzip the files into a folder on your PC  (I use C:\Spare\MEMSAnalyser\)

2.  Run MEMSAnalyser.EXE and you should be able to load and analyse the example files.

SETTING UP THE BATCH FILE
========================

1.  Open the MEMSLogger.bat file in a Text editor.

2.  Change the first line to reflect the folder path where you have put the program 'readmems.exe'

3.  Change the second line to reflect your COM Port and the location of where you want the log file to go.   I use a sub-directory /logs/ in the program folder. 

Note:  Windows is very protective as to where you can post log files.  For example, it will not let you write to the root C:\ directory or anywhere in \Program Files\ and problems have been reported using the Desktop.  So if the log file is not being produced then make sure you have write permission for the selected folder.   As above I find C:\Spare\... is safe, and also anywhere in the \Documents\ folder should be OK.

4.  Save the changes to the .bat file and exit the text editor.

PRODUCING YOUR OWN LOG FILES
============================

The basic idea is that MEMSLogger.bat starts Colin's readmems.exe which reads data from the ECU and produces a log file. Then MEMSAnalyser.exe reads the log file and creates graphical displays.

1.  Plug your laptop into the ECU diagnostic port. For cable requirements see http://www.rmrsoft.com/mems

2.  Turn on the ignition.

3.  Run the MEMSLogger.bat file.  If it connects OK, you should get an open Command Window with just 2 lines displayed.  If it disappears very quickly, open the log file in a text editor and find out the problem (You did have the lead plugged in and the ignition on I hope :-) ) 

4.  Do your test drive.

5.  When finished, close the Command Window.

6.  Rename the logfile to something relevant, or it will be overwritten next time you run MEMSLogger.bat

7.  Run MEMSAnalyser.exe to analyse the log file.

Any comments/suggestions, please send them to mems@rmrsoft.com

Al  