rt338b

iTrader: (4)

Hoe this is what you are looking for.

rt338b

iTrader: (4)

Well I had 1.40 and changed to 3.1 1.55 and it went to1.30 my a/f went to 11.7

denmah

iTrader: (2)

denmah

iTrader: (2)

yes, do this next

rt338b

iTrader: (4)

I answered this above and when I tried to go any lower it didnt want to run. Well I had 1.40 and changed to 3.1 1.55 and it went to1.30 my a/f went to 11.7

rt338b

iTrader: (4)

Does it seem possible that there is something wrong in the box or am I just missing something

tonypaul

iTrader: (2)

try 16.3 and 8.15(ms).....

Forcefed86

iTrader: (4)

You need to be a little more descriptive, it hard to follow what you did exactly. Screen shots would help.


1.)Use the required fuel calculator on the screen below to get your base numbers.

2.)Then only adjust the lower field with the "MS" next to it. If AF is getting richer with your adjustment go the other way. Essentially what you want to do is lean out the AF slowly with required fuel field. Then jump back to your VE map and add fuel.

3.) Keep at this until you get at least 1 on your injector MS gauge. This should allow the injector to run at a high enough pulse width to give you a steady idle.

Thats what I did anyway, not saying it's the best method. I started playing with MS a couple weeks ago.




Third gauge to the right is the injector PW. You want that greater than 1, closer to 2 is better. What is yours at now when it tries to idle.

denmah

iTrader: (2)

dead time on 80s is like 1.3ms so if you get close to that you are going to have resolution problems

IE Fatty mcstallerson

rt338b

iTrader: (4)

First screen is with req fuel at 5.3 second screen is with it at 3.15 1.58ms I cant adjust just the ms in req fuel. Don't know if this is because of newer version of tunerstudio. Thanks for advice will keep trying

denmah

iTrader: (2)

you cant change your Required fuel MS number at all?

thats why you are having trouble for sure

your Pulse width is the same as the injector dead time.

dead time basically means how long it takes the injector to open and close

so you are trying to run the injector at the same opening closing rate as its "refresh rate" basically causing it to sputter and loose resolution

you need to change that MS value even if you load a new project or something in there. and start over.

rt338b

iTrader: (4)

Yes I can change it. I just cant change the lower ms number by itself. If I go to 3.15 top it becomes 1.58 lower. As I lower the required fuel rate it doesn't change the A/F enough to be noticed. Basically I copied your fairmont tune for gas and outside of it running rich as hell on the A/F it doesnt have a stumble or anything acting crazy in the idle. I bought these injectors as EBAY items new and just seem to believe that something is amiss by the gauge even with it working. I cant get this site to upload picture so that is why I have the attachment instead. Thanks for bearing with me on this as I am sure that you are perplexed as much as I am.

rt338b

iTrader: (4)

Well changed everything all around with new tune and new required fuel and am still getting the same old story. Doesnt matter what I change I still end up with 11.1 A/F SO if someone thinks of something still all ears.

Sarg

iTrader: (6)

Have you tried lowering the dead time on the injectors? I know you have them set to what they SHOULD be, but I have had to play around a bit with these settings before on cars. If you have it at 1.20 maybe try backing it down to .90 or .85 or something.

rt338b

iTrader: (4)

I have had them set at 1.30 where they seem to work the best and when I try to go to as low as 1.15 the motor wont stay running and it won't start. If I leave the base pressure at 50 the motor surges like it has a huge blower on it and will eventually die so i have had to lower it to 40. Thanks

C10Lm7

Reviving an old thread but i am having the same problem with my 6.0 micro with deka 80s. Same tune too. I have been messing with it for a week and still no luck. Did you ever solve the problem?

TurboMcNutt

Did you ever get your problem fixed? having the same issues