MEMS 1.9

[svenska...@gmail.com]

Hello,

is this project still alive and is there a plan to add MEMS 1.9 support?

-Svenska

[colinb...@gmail.com]

The project is still alive, although there probably won't be any updates until next year. MEMS cars are very rare in the US, and the only car to which I have access -- my Mini SPi -- is off the road for some restoration work right now.

There are currently no plans to add MEMS 1.9 support. (This would probably only happen if I were to buy an S1 Lotus Elise.)

--Colin

[Martin Rubenstein]

There is an Android app "MEMS Diag" that will work with MEMS1.9.

[Martin Rubenstein]

I forgot to mention that the Android app doesn't have the facility to test the actuators and relays. It is possible to run the app on Windows using an Android emulator that passes through USB data - Andyroid for example - but if you already have an Android device or are thinking of buying one, then don't waste time and effort with the emulator.

[sprid...@googlemail.com]

Hello,

Have a look at pscan.eu for the 1.9 or as the post says MEMS-Diag app.  pscan does MEMS 1.9 and the alarm units.

[st8...@gmail.com]

Hi,

i have just discovered your project which is very interesting. As other people here, i would be very interested by a development on mems 1.9 (i own a MGF from 1997). I am located in France, and i can tell you it would be of interest for a lot of friends from the french MG forums and clubs.

If it can help, i can send you an ECU and a 5AS box for free, if you are interested to develop for mems 1.9. These boxes are coming from my car, i had to replace them because apparently the connection was lost between my keyfob recently refurbished, and the system.

The current tools are either quite expensive, or are not performing everything. Memsdiag does not manage 5as system. Pscan does it but is not providing functions like testing actuators or accessing maps (if i am correct). And other tools are very expensive for a private use.

Stéphane

[colinb...@gmail.com]

Thank you for the offer, but there is not much that I can do with an ECU that is not installed in a car. There are almost no MEMS 1.9 cars in the US, so I think it would be best if someone in the UK/Europe were to investigate this further.

--Colin

[dnb...@gmail.com]

Hi

I've just stumbled on to this group while trying to write some PC based diagnostic software working for my Lotus Elise.  MEMSDiag does not work for my phone, and I prefer using a PC for data analysis so it seemed a good use of my time to get back in to doing some software writing for cars.  I could have bought Pscan, but that would be the boring thing to do...

I now have software that can read the MEMS 1.9 ECU and get basic faults and live data.  I am working on translating the things I've found using Colin's website as a guide (Lambda multiplier is 5mV per LSB, not 0.5 as the website says BTW) and I believe bit 4 of one byte of the fault codes is the ambient air temperature sensor.  Not had a chance to do much else since getting comms to work reliably has been the main task.  I'll keep looking and post up my conclusions.

[Alan Richey]

This looks good.   Be very interested in the data format for V1.9 when you figure it out, so I can add the capability to MEMSAnalyser.

Al

[dnb...@gmail.com]

The MEMS 1.9 protocol appears near enough identical to the 1.6 protocol with the exception that it's half duplex so you get an echo of everything sent from the computer as the first byte of "data".  Easy enough to filter this out...  Initiation is the tricky thing.  I haven't got this quite right yet seeing as my software only works one time in three on average...

Is there a handy feature list of memsanalyser?  It seems silly for us to duplicate effort.

[Alan Richey]

MEMSAnalyser doesn't do any data gathering itself, it just provides a way of analysing the output of the ECU, either through MEMSLogger which samples the stream every 0.4 seconds or through the logfiles of MEMSGauge or MEMS_Roscoe.   So I assume you are producing the software that accesses the data stream from the ECU, and I would then adapt MEMSAnalyser to read the data file you produce.   So there is no overlap.    Have a look at it at http://www.rmrsoft.com/mems/index.htm

[broads...@gmail.com]

Any chance of getting the software so we all can contribute? And what cable are you using? The obd2 plug uses conncetion 4 as a ground (5 on some rover models) and 7 as the comm line

[leopold....@t-online.de]

Hi,
mems-rosco is only an enhanced version of colins memsgauge but you find code and working win-programm here:https://github.com/LeopoldG
You have an interface for mems 1.9, try to connect it.You will find data for the interface on colins pages.
Leopold

[broads...@gmail.com]

Colins page only has the info for the Mems 1.6 connection, not the 1.9.
As I really like the working of Mems gauge and Rosco is even a step better! I would like to be able to use it for my 1.9 as well.
I know there is an app called Mems diag but I like to be able to connect a laptop to my car, not my mobile phone!
So I could do with some directions how to make a cable (as the 1.9 only has one wire connected to the 7 pin of the obd2 plug it talks via what's called the k-line. As this is supposed to be a 12V signal it's not possible to use the cable used for the 1.6) if anybody has some.
I tried a cheap Chinese VAG cable but that didn't work.

[leopold....@t-online.de]

Hi ,
are you shure that it is 1.9? I thought the obd2 socket is for 2J. But in any case have a look for " toaf":http://forums.mg-rover.org/mg-zt-rover-75-sponsored-rimmer-bros-90/toaf-worry-ye-not-809649/, it should work with never versions of mems.I havent tested this because i have only a 1.3 version.
Leopold

[Martin Rubenstein]

Have you seen this page from Pawel's site?

http://memsdiag.blogspot.co.uk/2015/01/memsdiag-what-is-memsdiag-memsdiag-is.html?m=1

[broads...@gmail.com]

As I stated before, I would like to be able to use a laptop, not an andriod device

[Martin Rubenstein]

I understand: I'm the same preferring a laptop over an Android device. However, I was reffering you to the page solely for the information on the MEMS 1.9 cable that's in that page.

[broads...@gmail.com]

Well I would like to make my own

[dnb...@gmail.com]

Yes.  Software is no problem once I work out how to share a zip file here...  You should be able to download from here: Lotus diag dropbox link without having to register with Dropbox. The software mostly works, but there are some quirks - successful comms is about 70% on the Lotus - there's some timing glitch I'm not understanding at the moment.

I use a VAG USB "K-line" cable for mine (ebay cheapie), and it works OK.  You need one with an FTDI chipset because I do some odd things with it to initialise comms, and these might not work on the clone chips, and certainly won't work on other brands. 

Sorry for the absence of late - had to do a bit of "real" work and get some house DIY off the list.

Let me know what you all think - and remember I'm not a software engineer!

[leopold....@t-online.de]

Hi dnb,

thank you for the lotus-diag, unfortunately it will not start.I started the CDM21224 but lotusdiag still says it will not work because of a missing FTD2XX.dll.
It would be much better if you gave us the source code as well. By the way "mems-rosco" is written unter "QT"(if sombody wants to improve it)!
Leopold

[dnb...@gmail.com]

It doesn't work because you probably don't have the right drivers installed.  Most of the USB diag leads have historically used virtual comport drivers, but you can't get away with this for MEMS 1.9 (and a few others too) since you need to do odd things to initialise the comms*.  You need the FTDI direct drivers (here is a good starting point: http://www.ftdichip.com/Drivers/D2XX.htm ) to run my program.  Let me know if you can't find appropriate drivers and I will share mine.

I am reluctant to give out source code at this stage, but I won't rule it out in the future once I have it in a sharable state.  What are people's programming languages of choice? I'm fairly old school have used Delphi for this one, but I am happy to muddle my way through most things (Perl and Matlab being favourites)

*Initialising the comms on MEMS 1.9 is a non-trivial excercise, worthy of a thread in its own right, so I won't describe it here.

[broads...@gmail.com]

Hi dnb,

Would it be possible to add a pl2303 chipset into your program?
The ftdi chip is almost identical and the drivers are easy to get. There are loads of cables usd to serial with the pl2303 chip so that would make it even cheaper to make a cable

[aleciss...@hotmail.com]

Just found out my ECU is a MEMS 2J i.s.o. an MEMS 1.9 and it doenst connect. is there anyway i can read the 2J version? both are used in Lotuses

[Martin Rubenstein]

https://blackbox-solutions.com/help/SM072.html gives some info on your ECU, and Blackbox Solutions will probably have a diagnostic system that would work for you, but it will soon add up to a fair amount of money when cables etc are taken into account.

Pawel' Android app MEMSDiag works for MEMS 1.9. http://memsdiag.blogspot.co.uk/?m=1
You cpuld contact him at mems...@gmail.com with any specific queries.

[broads...@gmail.com]

It could be that the missing 30% part has a MEMS 2J ecu (1.6 has a ribbed cover, 1.9 has a cross on the cover but only 1 plug, 2J has also got a cross on the cover but two plugs one black and one red).
You might need to get the software to work with that to cover all Lotus models

[dnb...@gmail.com]

I don't have a pl2303 chipset device to experiment with, but there's no reason it can't work as long as there is an appropriate "bit bang" mode to initialise the comms.  This is the tricky bit of getting anything to work with these ECUs with modern computer hardware.

[dnb...@gmail.com]

I'm sure there must be a way.  I can't believe the comms protocol will be all that different, but perhaps ECU addresses and expected responses are...  Maybe I can come up with a way of outputting useful debug to see where things are failing.

[aleciss...@hotmail.com]

PL2303 apart from the driver of course works identical to the FT232 so adding the option to your Lot-diag should be possible

[aaron.l...@gmail.com]

Hi dnb,

Would you be able to release the source code for whatever you managed to get working for MEMS1.9. Interested in picking this up and seeing where I can take it.

[leopold....@t-online.de]

Hi dnb, any progress with the mems 1.9?
Could we all have the source code?

[jamesp...@gmail.com]

Just on the off chance anyone answers.. is there any source code or explanation of the 1.9 init sequence that someone can share?

Thanks

[leopold]

Hi Jamesp,
in this thread: http://www.theminiforum.co.uk/forums/topic/334463-sniffing-mems-2j/
kangoroomadman works with mems2J and in his source you can find the initialisation code for mems2j maybe it will work for you too.
I thought mems-diag works with mems1.9

[jamesp...@gmail.com]

Oh thanks for that link, I'll have a look.

mems diag can work with 1.9 but I am trying to update my own app to work with it too.

I have mems 1.3 and 1.6 working fine so far on Android app which is completely free

[jamesp...@gmail.com]

I pushed further with MEMS 2J - helping in the last miniforum link posted,

I got 1.9 working fine too, 

It's all going live/free at: https://rovermems.com/

there is a web application there that works using google chrome if you have a working/correct USB cable

[jamesp...@gmail.com]

For anyone struggling in future, the trick is to send 0x16 (22 decimal) through at 5 baud and then a slightly tweaked version of the same code the 1.6 ECUs will work