those of you running 550 primarys and 1000cc secondaries. or close to it .

what did you all put for required fuel for 1000 secondaries. the calculator on my MS desktop isnt working .
can i just leave it at 9.6 and just tune on the kpa's? im not to sure how to make the right changes for the larger injectors.

if you guys need more info on my setup please let me know . im really stumped on this .

thanks in advanced.

 

req_fuel should be just for the two primaries; the secondaries' size (if you're running them staged anyway) is accounted for in the staging parameters

 

thanks topless im going to check on the labtop for that.

 

In many ways, this is an arbitrary setting. As long as the number is large enough that you don't max out the VE table, and small enough that you don't try to go past 0 on the VE table, it is fine. I generally just put in 10.

 

on ms2 and even more on ms3 it's not completely arbitrary anymore.

Since cranking PW and other settings are based on reqfuel on ms2/extra, it's good to use the calculated value b/c then most of the other settings will "just work."

On ms3, even standard AE is based on a % of reqfuel.

Ken

 

looks like im going to have to stretch my ve tables cause i currently only have it to 10psi and my newer turbo is 25psi max. but im only tuning for 20psi.

thanks for all the inputs guys that helped me out a lot.

 

I'm also thinkering about the req_fuel

I using 2 yellow rx-8 injectors as primaries, secondaries are 2 yellow and 2 red rx-8 injectors..

engine is a stock 6port renesis, fuel pressure is 4bar.. idleVE is around 17 which seems rahter high..?

 

Idle VE of 17 is actually pretty low. Do you have multiply MAP turned off?

Ken

 

I'm running alpa-N, so I have around 1% load at idle.. multiply map is on 'don't multiply'

what did surprise me is that what I was lowing the idle speed and I have a negative load number due the TPS calibration, the load used in the ignition map was on top of the map (100% load), instead of the bottom (2% in my case) is this a bug or is this a safety measure or?

 

It wasn't actually using the top of the map. This is a bug in the .ini file in firmware revs older than 3.0.3. The MS is still actually using the bottom.

Ken