First Scan - anybody fancy a gander ?!

[simonbuk]

Just attempted a first scan - I've zipped it, maybe somebody would like to see if they can open it ? Anybody that has the time to have a look through it I would be eternally grateful. Car just doesn't seem to get going at higher revs - seems to struggle/gets held back.

Scan1SimonBUK.zip

[simonbuk]

Oh - that doesn't seem to have worked

[simonbuk]

Jesus..........what format do you save the file in ??

[simonbuk]

I've got this slightly reduced excel file -

Scan1SimonBUK.zip

[TorqueHorse]

When you are in ElanScan and you have the captured data, I typically do File>Save As> and then give it a name, but keep the .ecu file type extension. Then in your File Explorer, you can just change the suffix from .ecu to .zip instead of actually zipping it. Just let folks know when you post it that they need to manually change the file type back.
That's what I did to the one I've attached here.

23_01-01_ridehome.zip

[simonbuk]

Ok thanks, seem to have lost my ECU file ??!!

From a quick look I noticed that I have had maximum boost but rarely had over 100 bhp ? Only once I think - seems odd ?

[chrism]

Yep, unless you tell it specifically where to go it usually ends up in 'downloads' or perhaps, even, 'documents'...

Here's what I do. I called this file (say) log5 when asked to 'save as'

This white log5.ecu file is like the one you need to ZIP up (right click on it->compress->ZIP):-



and you attach the yellow 'zipped' file in the same way as you'd do with a pic...

Your zipped file came through as this and I'm not sure what it can tell us, especially about bhp and boost...



Sooo.......zip and attach your whole EScan log file so's we can see all the elements of your data - then perhaps a LEC 'star' will be able to illuminate your running problem (hur...)

[simonbuk]

Yes ignore that graph - it doesn't relate to what I was saying !
Looks like I'll have to do it all over again unless people like looking at Excel spreadsheets !

[chrism]

Erm...Escan might be a little more digestible

[simonbuk]

Oooh - what's that ?! How did you get it to that ?!

[chrism]

I don't use excel much at all so I don't know much about it but I unzipped your 2nd scan - the excel one - and pushed a graph-drawing button .

I think it's drawn some sort of graph of everything but the axes and scales don't make a lot of sense, if any, and I couldn't see an obvious way of seperating the elements. I'd imagine there's a way of drawing graph lines seperately for chosen columns but I can't imagine excel to be as 'clevva' as EScan by sorting out axes and scales in order to make the data mean anything more sensible.

Just a couple of thoughts:-
1. Why not do a (say) 5min tickover EScan data grab that might outline anything basic before giving it beans to check bhp or boost etc. That way the 'horse' could be inspected for injury before it bolts out of the stable and gallops off down the road?

2. Your excel data shows you're on promid 1499, your air:fuel ratio is constantly spot-on at 14.7:1 your boost peaked at just about 0.6 at 86mph (line 2008) - so a standard ecu map? Horsepower readings made no sense on line 2008. I couldn't see an O2 sensor voltage, so I wonder if you're using Ron's excellent EScan_beta update and new protocol?

3. ps it looks like your highest revs were ~4200 at your highest speed...again line 2008 on the excel spreadsheet

[simonbuk]

Thanks for having a look - saw the air/fuel ration was good too.

It is standard as far as I know but a new car to me so anything could have happened.

Good idea about just doing another run just on start up
I'll start again, delete all files and downloads and go back to the beginning !

[simonbuk]

Right - here we go again - deleted everything, started again.

Please see attached -

SimonBUK1.zip

I'll go out for a run once I know this has worked !!

This was simply starting it up and letting it idle for 5 minutes.

Any help appreciated.

[chrism]

log7.zip

Yep, that's much better

I've attached a recent .zip scan of mine. I'm no EScan expert but if you overlay my data on your graphs I think you'll get more of a 'feel for the normality' of your m100.

Lots of bits co-incide but in particular if you compare O2 sensor volts with mine (yours are blue mine's are black) they're VERY different - yet your air:fuel ratio is fine - so I'm a bit confused.



My first thoughts are a 'duff' O2 sensor, or perhaps a different version of Escan + its protocol, so let's hope an EScan guru might be able to provide more insight.

[simonbuk]

Interesting - I followed the links and instructions from the 'Manuals' page as thought that would be best, maybe thats not the latest ?

I could remove the O2 sensor from my other car to prove a point i guess ?

[simonbuk]

@ChrisM - think you might be onto something !

Checked the O2 sensor and had no reading when checked with an ammeter, checked the one in my other car and had a reading of .35 (or maybe 3.5 ?! can't remember ).

But the one in my new car seems dead. I'll swap them over when i've found a tool big enough ...........

As you say though, odd that the air/fuel ratio seems corrct .

Is there a second sensor after the cat that might be helping

[Tuga2112]

Checked the O2 sensor and had no reading when checked with an ammeter,

are you sure you used an ammeter ?

i dont think a current check would be helpful

[simonbuk]

Checked the O2 sensor and had no reading when checked with an ammeter,

are you sure you used an ammeter ?

i dont think a current check would be helpful

Multimeter......

[chrism]

simonbuk, if you get stuck then pop in. I've got a sensor removal tool - and a spare sensor, actually...long story

With the greatest of respect I've found that the older/original legacy EScan stuff is a bit 'dated' esp for later win10 and all win11 users.

There's a LEC post mostly by RonR/Matts1972/KenS that's effectively rescued it from obscurity, upgraded it for current windows versions, ironed out some errors and made it relevant and accurate again This is where you'll find the new ElanScan_beta and its new protocol software.

In fact, I think the new Elanscan_beta + protocol is now a 'sticky' in the Elanscan section so's us LEC-ers can have access to the up-to-date 'goodies' w/out spending ages trawling for the original thread.

[simonbuk]

Found the new file so I'll replace it shortly.

I wonder if a diesel injector tool is the same size - as I have one of those - somewhere.

I might yet come up to you