I just want to know when you guys go out and road tune your car, do you guys just tune the high octane and ignition maps or do you change your low maps too?

 

Also, i cant find the post, but how many counts of knock do you have to pick up for it to change to low maps on a timer?

 

The knock decays the octane counter which starts at 255, when it hits 0 you are on LO maps. I alter my low octane maps, but I have personal reasons with my car.

 

how come i click to log octane, but it lists it as octane flag and its at 100 the entire time?

 

also i think evoscan .97 isnt accurate on load calculation. I did a pull with 0 counts of knock i compared it to my map, i just looked at the incraments of 500 on the rpm range. and my load logged to actual rpm and timing? seemed to always be 20% higher then what it should be compared to rpm and timing? The reason why i ask is because it was consistantly 20% higher.

 

Ding DIng Ding....yeah its not accurate. I havent used .97 yet because when I downloaded it I got .90 for some reason again. From the log I have seen it seems to cap at 159.37 which oddly enough is the boost load cap.

 

what about that 255 octane number?

 

The octane number slower lowers as you get knock. How much knock were you logging?

 

I do not think that the numbers are that much off. Attached is a log with two methids of calculating load, the rpm-airflow method and the Evoscan/MJ method. As you can see they are very close to each other.

 

I stand corrected. The only other V.97 log I saw capped at 160 and I never got the real .97 so I guess there you have it.

 

v.97 the octane rating starts at 100 and goes down from there.

 

It is very accurate actually, I am running 17 degrees timing up top at 220% load and it hits right there at 7000rpm

 

There is ECU Load, which capped around 160 or so, and then the calculated method which both Evoscan and Mitsulogger are capable of. However if your battery voltage varies a bit in your driving, it can alter the accuracy of the calculations if you use the fixed 14v value.. If thats the case you should interpolate the value for 13.9v or so, it will make it more accurate, or create a new formula which does the interpolation for you. I had forgotten to add the 11v entry when I released v1 of my program so this was an available variable, but you can still do it in the requestID.xml file, very similarly to how Evoscan does it.. that will increase the accuracy significantly.

 

The RPM airflow method will likely work best.. But you'd have to use unclipped sources for your data (like an XEDE, ECU+, MaftPRO, UTEC)

The good news is its easy enough to post-process any logs for that from those tools..

 

ok, So in .97 it starts at 100 and counts down, once it counts down to 0 it switches to the lower map on a timer? How long is the timer? Also that seems like a ridiculous amount of knock before switching. If you have to pick up 5 counts to lose 1 point. That means it has to pick up 500 counts of knock before switching over?