I have been noticing that even though my BDEL+BCLO are almost the same as the 2 byte load being logged, I still get load error numbers sometimes in the range of +/- 10 or even more.

I was under the impression that BDEL+BCLO numbers that we use should be as close as possilbe to the 2 byte load that we log.

Given that I am still getting load error even though I got the BDEL+BCLO very very close to 2 byte load, could it be that the load error is referencing another load that we are not logging?

Could someone shed some light on this?

 

2-byte is good but its definetly not 100% accurate, I log both and look at both during my log reviews
sometime i see calc load 220-226-235-240
but the 2bype load 222-130-236-248

so obviously i used the calculated load 220 and not the 130 2byte value.
and the timing matches this also.

 

nj, have you changed the boost load path?

I've found changing it to the fuel or timing or whatever load makes it pretty darn close.

 

No I have not. How do I do that?

 

Ah where there you go. Stock boost follows it's own "boost load" which can be quite off from the normal 2byte load.

I'm surprised you haven't changed this yet!

https://www.evolutionm.net/forums/sh...d.php?t=288408

For your Evo 9, Variable for boost control: Stock will read 6B48. Change it to 6B42

 

I have done the mods in the thread you linked me to. But I am not logging "boost load." Do you have the xml info and Evoscan info for load boost?

I remember you mentioned this in a thread on SoCal evo, but I cannot find it.

 

^thats also the address that doesnt change with Temp and Baro, right?

 

Correct ... 6B48 is the temp+baro corrected load that timing is based on.

 

^lol... thanks touring. ive been watching for a year, and am just trying to sprint to catch up to you all now. sorry for all the questions.

 

No problem.

I actually log both 6B42 and 6B48 loads. I do this because of timing variances based on weather conditions.

 

If you did the boost load mod in the thread, you don't need to log boost load. The mod in the thread makes boost load the same (or very close to the same) as 2-byte load.

 

well it replaces the comparison variable in the boost routines with the same 2byte load that we all log.

so now your ECU is trying to set the WGDC based on 2byte load rather than some other load variable!

same principal for JDM MAP based boost, just using a different variable again