How do identify the fault

[scotlan]

This is compiled by Mr Thicky, I built my connector cable/interface as per the Youtube "How to make an ElanScan ECU diagnostic interface cable for the Lotus Elan M100",
and to my surprise I am now receiving bucket loads of information. My first attempt filled a massive Excel spreadsheet with infinite columns of info most of which is complete rubbish e.g. my top speed during test was 147 mph while actually standing still in my garage.
The second effort comes up with the info "Faults 10"
I was expecting a feature fault code which would tell me why I have a very minor hesitation at low revs.

I have also tried the "paper clip / bridging plug" method and get a clear 1 - 2, that is 12 code which is "No Fault"
Any advice would be very well received
Thanks

[Simon_P]

Are you using Elanscan? and then exporting to Excel? not sure why you would want to.

I was expecting a feature fault code which would tell me why I have a very minor hesitation at low revs.

This is 1980's technology you are about 10 years ahead of yourself.

Is the hesitation at 30mph with light throttle?

[scotlan]

.


Is the hesitation at 30mph with light throttle?

Exactly, in fact cruising at 70 on the motorway it runs beautifully.
Reading other notes I checked the plug gaps and found them a bit tight. Adjusted them to .8 . Initial impressions on a nip round the block maybe a small improvement, they are Bosch44C143 plugs so I ordered a new set of NGKBKR6E for a tenner this afternoon
Any other suggestions would be of great interest

[Simon_P]

Are you using Elanscan?

and see here
viewtopic.php?f=34&t=27290&p=356011#p356011

[scotlan]

Yes I set up Elandcan, got readings but I couldn't understand any of the info I was getting. However I never tried it other than stationary. Tomorrow I'll see what happens when I actually drive it with Elanscan connected.
In the other link you mention, I noted that I also have an immobiliser which is tricky to operate, at best. As soon as new rod locks arrive I will be replacing the solenoid which does not unlock the driver's door. I hope this cures the immobiliser issue. The immobiliser is operated from the key centre.

[Simon_P]

No need to drive for elanscan and no need for excel you should be able to view the file using elanscan. Zip the file and post it here so we can have a look.

[scotlan]

Hi Simon_P
yes I would be pleased to send it to you but don't know how to Zip the information that came out on Elanscan

[Simon_P]

save the elanscan .ECU file to your desktop
On the desk top right click
choose send to >
select "Compressed (zipped) folder - It will appear on your desktop
Post here - choose the "upload attachment" tab just below the submit button
"Choose File" to select the zip file from your desktop
"Add the File"

[scotlan]

Here are my efforts, just hope they transmit OK

[Simon_P]

file 2 is gibberish

File 3 is ok but not enough data - Either start from cold and scan at least until the fans come on or go for a gentle drive depending on what fault you are trying to identify
You have a CTS error but with such a small data set it is hard to tell anything - MAT is 35 C so the engine is at least part warm so i'll guess that your engine is a bit hotter than 25C which is what the CTS is reorting.

[scotlan]

Thanks, it's very kind of you to check this out for me, I'll get some better data tomorrow, in the meantime what is CTS ?

[GeoffSmith]

CTS is the Coolant Temperature Sensor.

The garbage is because the latency is not set to 1ms. Not doing so substantially increases the risk of damaging the ECU ALDL port with this type of interface.

[Simon_P]

Coolant Temperature Sensor - see the wiki top left of the screen.

[scotlan]

The garbage is because the latency is not set to 1ms. Not doing so substantially increases the risk of damaging the ECU ALDL port with this type of interface

Thanks, after a lot of jiggery-pokery I learned how to change the latency to 1, it was 25.
Will run the car tomorrow and report back!!

[scotlan]

monday morning zip.zip

Monday morning (2).zip

Well I changed the Latency to 1.
I drove the car up the lane surprisingly the management light was on all the time and so may get a reading faults and all, I hope so. Cut out, ran like a pig.
Up until now I have had an intermittent 2,000 rpm tickover which I believe also indicates a CTS fault.
I hope this info can be read and analysed by you, the experts
Fingers crossed!

Ps ambient temp 0.5°. !!!

[Simon_P]

I'm unable to open either file due to "Invalid floating point"
It might just be me but I can open other elanscan files.

[Fredjohn]

I can't open it either: same response. Did some Elanscans of my own yesterday: no problems creating or re-opening them.

Here's one from yesterday: can that be opened OK?

o2 test1.zip

[scotlan]

Monday 11am ZIP.zip

Oh dear!
So, I just did another run around the country lanes. Temp now 2°.
No management light but still a bit fluttery at low revs.
I hope the attached is readable BUT if not i am thinking I should get a new CTS and fit. It seems that Simon_P felt there was a CTS issue and the 2,000 rpm intermittent tickover also points to that.
Once I have changed the CTS maybe the readings will be more manageable (??)

I believe I can use Delco 25036979.

Thanks again to you all

[scotlan]

Monday 11am ZIP.zip

[Simon_P]

The file works. It shows a CTS fault but there isn't enough data and it might just be a stored fault. To be conclusive you need to do a scan at idle from cold until the fans come on that gives us 3 data points
1. Ambient vs cold engine temp
2. the thermostat opening 82c
3. the fan coming on 110c

Almost cold from start would do, if it is the CTS it is likley to be showing something like -40c.
Some commentary about what the temp gauge reads would also be useful.