I find my car in the 320+ load will sometimes pull timing but no knocks present?



Is the load going beyond 320+? Not sure what is going on and why...

 

I'm referring to cars that barely go over the load column and often the slight decrease in timing is desirable. However, best practice is to extend that column so that you have full control.

 

What exactly does the "Load %" represent? MAS flow or something?

 

I have extended it to 330. Should I extend it to 340? (from 300) What is the max ecuflash supports?

 

What loads are you actually hitting? There's really no point to extend past that.

 

It's basically an airflow/rev value.

Quoting Bez from one of the disassembly threads:

MAF SIZE is 1/engine_volume

base LOAD=MAF_PULSES_PER_REV*MAF_SIZE*2^17



Eric

 

So, if load % is based on MAF readings (which makes sense for OL), does that mean that an incorrectly scaled MAF will not only throw off the fuel mix, but also the load value the ECU thinks its running on?

Basically, the ECU thinks it's in the 260 cell when it's really in 240?

 

I am not sure which load is being hit but what I do know is that is it must be past 330 load otherwise why would the ECU retard timing if no knocks are present? It has retard the timing by 2 degrees from 330 load?

 

Yes, that is correct.

That is the main reason why most aftermarket intakes need a tune. It is because it is messing up the calibrated MAF readings and throwing you in other load columns that do not really represent your true mass airflow.


Eric

 

Knowing which load value you are hitting is pretty much the basis of tuning with ECUFlash. If you need to know anything its the load value.

Your timing pull could be due to map interpolation. I commonly run between the #2 and #3 timing maps on my IX. I also noticed interpolation at times to the low octane timing map with no knock present.

 

another common problem is evoscan users that don't tell the program their new upgraded injector size.. that'll get you some really low load values in the logs. The signs are when you see people well into the sub 100 load columns when they go WOT.

 

Thats makes sense and is what I suspect... Why or how can it be controlled better? Fuel is 100 octane in Evoscan. High Octane maps 1-4 are same.

(Evoscan is configured correctly for Injector size. The LoadCalc is off and I am going by the timing to enable my load cells. Only sometimes in WOT this happens...)

 

looking at timing can be misleading when you have 3 low octane and 3 high octane timing maps.. which map are you comparing to the log?

 

High octane maps as my octane is reading 100. Also knock shows 0.

 

Best to run 2 Byte load, not to hard a mod now jcsbanks has done the leg work.

MB