Need a little Evoscan guidance for checking for knocks

[Kaldek]

Hi folks,

I have EvoScan and the cable and all that, but my EvoScan skills are still crap. Doesn't help that it's a bloody hard interface to use...

Anyway, I'd like to set up some quick logging to check for knocking. Car is going in for a tune soon and I'd just like to make sure there are no hidden surprises for Steve which I could potentially fix in advance.

I saw someone post some log images that showed knock events. I just don't know how to drive the interface to get that kind of graph up.

 

[mookers]

I don't know that you need to bother. Steve looks at all that stuff and fixes it when he tunes anyway.

(unless you think there is a problem with your turbo plumbing or fuel lines or something, and are using Evoscan to find it)

 

[d3ck5]

id like to know too!

 

[Kaldek]

Ye

I don't know that you need to bother. Steve looks at all that stuff and fixes it when he tunes anyway.

(unless you think there is a problem with your turbo plumbing or fuel lines or something, and are using Evoscan to find it)

Yeah that's my concern. Just in case there's something odd going on.

Car is running on 98 RON, but I could swear at high rpms there is a subtle sound of pinging. It could just be induction noise it's so subtle, hence I'd like to have a look. Boost is stock.

The last thing I want to do is rock up for a tune and have Steve tell me that the tune he managed to put in given the time available was a bit shit because there is a mechanical issue I needed to deal with already. I've got two weeks to fix anything I find, which is plenty.

 

[Dice]

I just log using Evoscan (or mitsulogger) then check the log in Excel. You can then sort the knock fields in numeric order to check max counts.

 

[VOLK]

I used mitsulogger, then graphed via a google docs spreadsheet. Also, filter upon the knock column to only show rows with knock > 0 etc.

Got yourself an openport 2?

 

[Kaldek]

OK so I did it. 3rd gear pull all the way to redline. Gosh, you need a fair bit of road to do that.....*cough*.

Anyway, I just ran EvoScan leaving the defaults and just said "start Datalogger", did the run and then "Stop DataLogger". Copied the CSV file from the EvoScan directory in my documents directory and edited it in Excel.

Basically, the engine did not knock (as far as the ECU is concerned). I know enough about fueling to know what the basic data means, and everything looks good except the ECU says that WOT is only 95% throttle.

 

[Kaldek]

Hrm, apparently the 95.68% throttle reading at WOT is normal - i.e. don't mess with it. Looks like I have a healthy car.

 

[jungle]

Depends on the version of EVOscan and your ECU defs, If they're ok then it will graph in EVOSCAN

 

[Legnum in America]

I am also needing help with reading my EvoScan. I just had the timing belt, water pump and seals replaced last week. I ran a EvoScan today without WOT. I will run another one on my way home with WOT. Thanks in advance.
https://drive.google.com/file/d/1V64...ew?usp=sharing

Here is the log with WOT.
https://drive.google.com/file/d/1z37...ew?usp=sharing