Wolf 3D Wolf 3D: Staged Injection Question
02-19-05, 12:35 AM
#2
The staging value (%) is the amount of secondary injector pulsewidth in relation to the primary injectors. So at 50% staging, if you have a primary pulsewidth of 3 ms, your secondaries would fire at 1.5 ms. At least this is how the V3 Wolf worked, someone correct me if I'm wrong with the V4.
From what I have been reading, the RPM and LOAD staging are proportionally related to one another.
For example:
50% Load Band = 15% staging
4000 RPM = 50% staging
So at the 4000 RPM and 50% Load MAP point, you will have 7.5% secondary staging (50% of the 15%).
For instance, if you want LOAD ONLY staging, where the the secondaries come online at specific loads only, regardless of RPM, you would set the RPM staging to 99.6% for all ranges. This would mean that the wolf basically uses 100% of your load staging values.
From what I have been reading, the RPM and LOAD staging are proportionally related to one another.
For example:
50% Load Band = 15% staging
4000 RPM = 50% staging
So at the 4000 RPM and 50% Load MAP point, you will have 7.5% secondary staging (50% of the 15%).
For instance, if you want LOAD ONLY staging, where the the secondaries come online at specific loads only, regardless of RPM, you would set the RPM staging to 99.6% for all ranges. This would mean that the wolf basically uses 100% of your load staging values.
Last edited by eViLRotor; 02-19-05 at 12:51 AM.
02-19-05, 05:38 AM
#3
Send me your BMX parts
Originally Posted by eViLRotor
The staging value (%) is the amount of secondary injector pulsewidth in relation to the primary injectors. So at 50% staging, if you have a primary pulsewidth of 3 ms, your secondaries would fire at 1.5 ms. At least this is how the V3 Wolf worked, someone correct me if I'm wrong with the V4.
From what I have been reading, the RPM and LOAD staging are proportionally related to one another.
For example:
50% Load Band = 15% staging
4000 RPM = 50% staging
So at the 4000 RPM and 50% Load MAP point, you will have 7.5% secondary staging (50% of the 15%).
For instance, if you want LOAD ONLY staging, where the the secondaries come online at specific loads only, regardless of RPM, you would set the RPM staging to 99.6% for all ranges. This would mean that the wolf basically uses 100% of your load staging values.
From what I have been reading, the RPM and LOAD staging are proportionally related to one another.
For example:
50% Load Band = 15% staging
4000 RPM = 50% staging
So at the 4000 RPM and 50% Load MAP point, you will have 7.5% secondary staging (50% of the 15%).
For instance, if you want LOAD ONLY staging, where the the secondaries come online at specific loads only, regardless of RPM, you would set the RPM staging to 99.6% for all ranges. This would mean that the wolf basically uses 100% of your load staging values.
02-22-05, 01:11 PM
#5
hes basically dead on. ill paste my reply to your PM here incase anyone else is interested, but evilrotor hit the nail on the head.. there is some info in this post about wolf software bugs that you all might want to know about when tuning.. so read up
anyway, its pretty simple...
My recommondation is to just leave the RPM map at 100%. This will read strictly from the load based map.
How it works is like this:
We'll say youre at 3000rpm, 43 load. wolf will take the value from the fuel map, we'll say 10 milliseconds to make it easy(it uses the value of injector 1, so if there is any trim on it, i think it takes that into consideration as well. not sure if its before or after tho). then it will look at the staging map at load 43 (say its 80%), and it will look up the value in the rpm map (say its 50%).
so now we have 3 values.
1: duration of injector 1 in milliseconds (10)
2: percent of injector 1 at load 43 (80%)
3: percent of injector 1 at 3000rpm (50%)
these are just random numbers, easy to work with. the values should never be like that =]
so to find out what duration we will fire the secondary injector at, it basically multiplies all of this.
10 * .80 * .50 = 4
so it'd be firing the secondaries for 4 milliseconds
order is unimportant since its multiplication, theres no specific table it looks at first. It just looks at both of them.
the reason I say leave rpm at 100% is because you really dont need to do staging based on rpm. it makes tuning a LOT harder and more complicated. its much easier to just have it look up values from the load table.
if the rpm table was all at 100%, it'd just be 10 * .80 * 1.00, which is the same as ignoring the rpm table.
I generally leave RPM at 100%, and start bringing in load at load band 43. You dont want to stage too abruptly or it will cause rich and lean spots as the software interpolates and brings in the injectors between the 2 bands. if you look at my maps you can see how i bring it in smoothly.
There is a bug in the wolf software tho. It can sometimes be troublesome to tune the staging load map properly. Normally when you go there, it only displays 4 load bands. to have it display all of them, you need to go to your fuel map first, and change the X axis to show every 125rpm. Once you do that and go to the staging/load map, itll give you every load band. was fun figuring that one out =]
If youre still confused on anything let me know. I took like 5 phone calls while writing this so I hope its all coherent
anyway, its pretty simple...
My recommondation is to just leave the RPM map at 100%. This will read strictly from the load based map.
How it works is like this:
We'll say youre at 3000rpm, 43 load. wolf will take the value from the fuel map, we'll say 10 milliseconds to make it easy(it uses the value of injector 1, so if there is any trim on it, i think it takes that into consideration as well. not sure if its before or after tho). then it will look at the staging map at load 43 (say its 80%), and it will look up the value in the rpm map (say its 50%).
so now we have 3 values.
1: duration of injector 1 in milliseconds (10)
2: percent of injector 1 at load 43 (80%)
3: percent of injector 1 at 3000rpm (50%)
these are just random numbers, easy to work with. the values should never be like that =]
so to find out what duration we will fire the secondary injector at, it basically multiplies all of this.
10 * .80 * .50 = 4
so it'd be firing the secondaries for 4 milliseconds
order is unimportant since its multiplication, theres no specific table it looks at first. It just looks at both of them.
the reason I say leave rpm at 100% is because you really dont need to do staging based on rpm. it makes tuning a LOT harder and more complicated. its much easier to just have it look up values from the load table.
if the rpm table was all at 100%, it'd just be 10 * .80 * 1.00, which is the same as ignoring the rpm table.
I generally leave RPM at 100%, and start bringing in load at load band 43. You dont want to stage too abruptly or it will cause rich and lean spots as the software interpolates and brings in the injectors between the 2 bands. if you look at my maps you can see how i bring it in smoothly.
There is a bug in the wolf software tho. It can sometimes be troublesome to tune the staging load map properly. Normally when you go there, it only displays 4 load bands. to have it display all of them, you need to go to your fuel map first, and change the X axis to show every 125rpm. Once you do that and go to the staging/load map, itll give you every load band. was fun figuring that one out =]
If youre still confused on anything let me know. I took like 5 phone calls while writing this so I hope its all coherent
02-22-05, 02:25 PM
#6
so, this means that if you have "zeroes" in either the RPM or the Load bands, then the secondaries will never fire (for the cells you have 0's in) right?
sorry for stupidity #2, but where is one of your maps? i've searched and can't find them.
sorry for stupidity #2, but where is one of your maps? i've searched and can't find them.
Thread
Thread Starter
Forum
Replies
Last Post
Jeff20B
1st Generation Specific (1979-1985)
73
09-16-18 07:16 PM
