I've been logging for the better part of the day with EvoScan trying to get the maps dialed in better.

One thing I noticed, the timing values that EvoScan is recording do not match the High Octane Timing Map values. I'm consistently running a couple degrees below what the timing map says I should.

NO, I'm not experiencing any knock. Knock sum is 0, I've only seen maybe 4-5 1's, no 2's or 3's.

Here's the kicker.... if I slide over one column to the right to a higher load calc cell for that rpm, everything is in order. Is it possible for the EvoScan load calc column to be logging a lower number than the car is actually running?

 

Yep, its certainly possible.. Your level of mods, and other things can alter what the indicated load calculation is..

This happens to me pretty frequently in Mitsulogger, but not all the time, so I always look at the adjacent cells.

Remember, this is a calculated value and isn't always correct, there are other factors that come into play.

The good news is there is some potential to getting a more accurate reading of load, without resorting to modifying the ROM itself to output 2 byte load, but 2 byte load is the only way to get a completely accurate load value.

With some of the research going on with the MAF calibration tables, there has been correlation to airflow to other settings, and therefore it may be possible to calculate load accurately in the future.

 

I actually thought the load calc in evoscan read higher than actual.... which would explain why i didn't hit boost cut even though my evoscan load calc value was higher than the set boost cut.

What are the exact values that you're looking at? The values in the cells are not actual integers but are carried out quite a few decimal places; so it could just be the numbers getting rounded up or down. Also, could just be from the interpolation between values.

 

I don't know if that was directed at me or malibu, but here's a single data point, but I've got complete logs of similar circumstances.... WOT at 5500 rpm, load calc of 222 per EvoScan, and I'm getting a timing value of 6 when the map says I should be running 9 at 5500 rpm and 220 load. But load cell 240 @ 5500 is calling for 6.

I'm on a 50 trim with GSC 280's, so I can see where malibu's point might apply. The pumping losses may have been freed up enough to make the load calc err on the low side of actual.

Thanks for the feedback.

 

There are two formulas for calculating load. The airflow/rpm*852 fromula (green line) reads lower than the formula used in Evoscan (light blue). If your airflow number in Evoscan does not go higher than 1609 and your hitting the wrong cells, then it is better to use the above load formula. The DLL below shows two load formulas.

 

Good lord whats the peak timing in that log NJ? 30?

 

Haha!

Nevermind.

 

This is the OBDII timing and NOT the xede adjusted timing. Xede adjusted timing is 18.6* from about 7k to cutoff.

 

There may be other compensations going on that are undocumented because whilst I find that the the load calculations are often optimistic compared with the real load, even with that the datalogged ignition timing is often more retarded than the cell would apparently call for - even when the octane number is max and there is no knock sum.

 

From what I see from nj1266's figure, and the topic here (actual ecu calc load vs evoscan), at least it can be assumed that although the loggers are not precise (3%) in displaying ecu load, they sure are pretty darn accurate and consistant, right?

 

ok, I think I've figured out my problem.... I'm running larger injectors scaled at 630 for now in EcuFlash. But, EvoScan v.97 uses a 513 cc/min scaling factor for it's load calc. to datalog. Is there a way to change this value/formaula in EvoScan??? I can't seem to do it.

Edit: Let me recap because the post above makes no sense by itself. I'm consistently logging timing values in EvoScan at specific rpms that correspond to higher load cells than EvoScan is telling me I'm in. I'm sure it's because I'm using bigger injectors and scaled to a higher value (630) than the stock 513 value. EvoScan is using 513 instead of the larger value I'm running for injector scaling. Since it's a multiplier in the formula, EvoScan is recording a load calc value that is not where I'm running in the map.

 

Yes, there is a configuration file you need to change.. I think its data.xml in Evoscan.

Mitsulogger has fields to alter this from the program before you start logging, it was because the tool is designed to be used with different cars so it has several parameters that can be changed quickly from the GUI..

 

um.... ok. I opened that file. Whew! What do I do with it? It's jibberish to me????

 

ya know, I'm not sure, I haven't really used Evoscan recently.

 

I'm computer illiterate, it's a data.xml file. What do I use to open it for modification? It's opening in an internet explorer type window.