7 replies to this topic

[owm]

Following previous posts here I managed to construct my own diagnostic cable and successfully connected my jap spec SPI.

Attached are some readings from cold start, couple of minutes later and 15min on.

Any kind soul with experience can comment on anything I should be looking at? I checked the codes and nothing showed up although it appears the MAP reading is high (changing the hoses soon together with the fuel trap), the Lambda sensor reading doesn't fluctuate frequently as it is supposed to?


 Screenshot_2018-02-23-11-30-45-124_com.rovermemslite.png   70.31K   7 downloads  Screenshot_2018-02-23-11-30-47-736_com.rovermemslite.png   69.67K   4 downloads

Attached Files

•  Screenshot_2018-02-23-11-36-48-828_com.rovermemslite.png   70.29K   6 downloads
•  Screenshot_2018-02-23-11-36-51-546_com.rovermemslite.png   70.17K   2 downloads
•  Screenshot_2018-02-23-11-45-24-522_com.rovermemslite.png   68.89K   4 downloads
•  Screenshot_2018-02-23-11-45-26-935_com.rovermemslite.png   68.4K   4 downloads

[gdudu]

Hi

With static data like this, I guess nobody can do something (see my picture)

And what's wrong in the car ?

Attached Files

•  Speed iddle Lambda.png   153.99K   8 downloads

[martinrub]

gdudu is right: you have displayed 2 snapshots in time. Both show a high lambda voltage; almost certainly thats just because each snapshot was taken when the O2 sensor was in its high state. On the other hand. if, for some reason it was stuck high, you simply wouldnt know from the 2 snapshots.

Im fairly sure the MEMSDiag logfile cannot be read by MEMSAnalyser, so the best you could do would be to choose a couple of parameters of interest, display the graph and take a screenshot. I cant remember the extent of the time axis; is it 30 sec? Now, theres only one Y axis scale as I remember, which makes measurement of more than one parameter tricky.

Do you have a problem with the car?

The fuel trim at 81% caught my eye, but again, its a snapshot. Converting kPa to psi, I tend to think you might be right, MAP perhaps ought to be lower. But I really wouldnt commit myself on a snapshot.

Try some screenshots over the full time axis, or a logfile readable by MEMSAnalyser.

[genpop]

or download mems-rosco from here:https://github.com/LeopoldG/mems-rosco

it's available for free again!

build a directory on your laptop and download all files. Then build a directory called "logs" inside and you may work with mems-rosco.When you download memsanalyser from rmrsoft.com (Al Richey) you may see much more.

[gdudu]

Mems-rosco doesn't work on my latpop (windows 10)

Nothings happen when I lauch the .exe

[martinrub]

Please check back on Leopolds mems-rosco Github page. There are a couple of folders that Leopold will add together with instructions. So, I believe, you will end up with 3 folders above all those programs: one called bin, one called platform and one called logs. Logs will be empty until you start generating log files.

So keep watching Leopolds page for the addition.

 

EDIT: Leopold has now added the folders.    But when I tried to run mems-rosco.exe nothing much happened, so I have told Leopold.

 

Leopold has run into a glitch with Github, so please bear with him for now.   The important thing is that he knows about it.

Edited by martinrub, 25 February 2018 - 08:56 AM.

[FlyingScot]

If the car has a problem start with the basics. Correct service and mechanical set up (filters plugs, tappets etc). Then fuel system maintenance, fuel filter, replace fuel trap and new vacuum pipes. Check earths and wiring all in place.
Then diagnose for any sensor or component issue otherwise you will spend a lot of time....

FS

[owm]

Thanks all for the replies! Still trying to figure out using MEMSdiag, have yet to try MEMSAnalyzer.

 

Currently the car is in the workshop to check on cam and ignition timing then I will see what to do from there. All serviceable parts are new or have been replaced.