Injector Scaling with ECU Flash
#16
EvoM Guru
iTrader: (5)
Originally Posted by racegate
I almost think it would be easier if the number displayed in the fuel map was the actual bit value (0-255). Because having a 'calculated' value there, and the inj scalar not really corresponding to an actual inj size somewhat muddles things. If there were a scalar number, which was multiplied by the bit value displayed, then one could fairly quickly rough the on-time needed for various fuel setups to do base mapping very qucikly. And it would make scaling for various fuel systems very straight forward using standard math and no conversions. Maybe if there could be a toggle to between a raw value, and calculated value, it might be useful?
#19
Former Sponsor
iTrader: (3)
Join Date: Mar 2003
Location: Arlington Heights, IL
Posts: 793
Likes: 0
Received 0 Likes
on
0 Posts
From my experience going from a stock injector to the larger injectors we use you can adjust inj. scaling but it's not a straight shot across the board. You really don't have to take out that much fuel on the lower load levels to keep fuel trims near zero. Take out too much and the car runs like crap. For example, going from the stock injector to a 680cc/min inj (ours) there is very little you need to do a low load levels & rpm levels (low pulsewidth conditions), but you do need to remove quite a bit of fuel at higher PW's.
Ford EEC tuning Ted? EECTuner all the way!!
Ford EEC tuning Ted? EECTuner all the way!!
#20
Evolved Member
iTrader: (2)
Originally Posted by AMS
From my experience going from a stock injector to the larger injectors we use you can adjust inj. scaling but it's not a straight shot across the board. You really don't have to take out that much fuel on the lower load levels to keep fuel trims near zero. Take out too much and the car runs like crap. For example, going from the stock injector to a 680cc/min inj (ours) there is very little you need to do a low load levels & rpm levels (low pulsewidth conditions), but you do need to remove quite a bit of fuel at higher PW's.
If this was the case though, I would imagine the effect to diminish as RPMS increase, since the injectors would be cosuming much more fuel.
Eric
#21
Evolved Member
iTrader: (11)
Originally Posted by racegate
I almost think it would be easier if the number displayed in the fuel map was the actual bit value (0-255). Because having a 'calculated' value there, and the inj scalar not really corresponding to an actual inj size somewhat muddles things. If there were a scalar number, which was multiplied by the bit value displayed, then one could fairly quickly rough the on-time needed for various fuel setups to do base mapping very qucikly. And it would make scaling for various fuel systems very straight forward using standard math and no conversions. Maybe if there could be a toggle to between a raw value, and calculated value, it might be useful?
Yea that would be nice but beggars cant be choosers lol, Its freeware the guy has already still did an awesome job. I can think of plenty requests to add also like speed density, cell block follow, on the fly tuning hahaha, but we cant complain its free.
#22
Evolved Member
iTrader: (2)
Originally Posted by AMS
From my experience going from a stock injector to the larger injectors we use you can adjust inj. scaling but it's not a straight shot across the board. You really don't have to take out that much fuel on the lower load levels to keep fuel trims near zero. Take out too much and the car runs like crap. For example, going from the stock injector to a 680cc/min inj (ours) there is very little you need to do a low load levels & rpm levels (low pulsewidth conditions), but you do need to remove quite a bit of fuel at higher PW's.
It will have less of an effect at idle because of the relatively low pulsewidth compared to say, cruise, where the pulsewidth would be roughly double, say 1ms-2ms. I have seen numbers like this with DSMLink.
That latency or deadtime of the injector may be matched nearly perfectly for the 1ms of so of pulsewidth at idle, but when you get to much larger pulsewidths, that latency is getting to be a much smaller percentage of the total pulsewidth time, so now, more fuel must be removed.
For example, say that your injectors are 10% larger than stock, but the deadtime is .1ms (100uS) more than stock. At a 1ms injector pulsewidth that would cancel out and your idle would be mostly unaffected (you're getting 10% more fuel, but at 10% less time (.9ms)). But now at a larger pulsewidth like say 5ms, you're getting 10% more fuel due to the 10% larger injectors, all but this is in 4.9 ms in actual time due to the .1ms deadtime increase. So, you;re really only losing 2% of time. This percentage would go down as the injector pulsewidth goes up.
So, this would go in line exactly with what you have experienced.
Eric
Last edited by l2r99gst; May 18, 2006 at 10:33 AM.
#23
Evolved Member
iTrader: (11)
Originally Posted by MalibuJack
You can actually change that yourself.. Change the scaling in the defintions to uint16 or uint8
#30
Former Sponsor
Join Date: Jun 2004
Location: Arizona
Posts: 117
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by racegate
I almost think it would be easier if the number displayed in the fuel map was the actual bit value (0-255). Because having a 'calculated' value there, and the inj scalar not really corresponding to an actual inj size somewhat muddles things. If there were a scalar number, which was multiplied by the bit value displayed, then one could fairly quickly rough the on-time needed for various fuel setups to do base mapping very qucikly. And it would make scaling for various fuel systems very straight forward using standard math and no conversions. Maybe if there could be a toggle to between a raw value, and calculated value, it might be useful?
Thread
Thread Starter
Forum
Replies
Last Post
mr.almeida
General Engine Management / Tuning Forum
4
Mar 15, 2010 06:23 PM
HiVoltEVO8
Vendor Service / Parts / Tuning Review
49
May 11, 2006 11:50 AM
shiv@vishnu
Evo Engine / Turbo / Drivetrain
213
Aug 5, 2005 03:05 PM