I have stories and dyno numbers!

SilverBullet00

New Member
Jul 5, 2004
1,150
0
0
Wichita, KS
I got the mongoose kit dyno'd this weekend!!

Well I put the car on the dyno today. Starting off the car was lean as hell. After a couple half runs he added 10% fuel to try and make the AF more rich. It helped, and we were able to do a full run. We then added 14% fuel and it made the car a lot safer. She ended up laying down 387hp, but for some reason I didnt get the print out...... I just got one for 382 HP and 379 ft lbs of tq.

From the datalogs it looks like it is running out of fuel at 5200 RPMS. As soon as I get the videos uploaded I will post a link....

Looks like I need to send the logs into Tim so he can adjust it a little bit. I also need to look at upgrading my fuel system.

dyno001.webp

dyno002.webp
 

Attachments

  • dyno001.webp
    dyno001.webp
    31.8 KB · Views: 108
  • dyno002.webp
    dyno002.webp
    54.6 KB · Views: 103
yeah, I think I am. My buddy works as a parts runner for a dealership here in town, so I am going to see how cheap he can get me a cobra tank and pumps for...

... I have 3 datalogs that go with the runs. I am NOT pegging the MAF, only 940 AD Counts @ 6000 RPM.

My wideband is a piece. No matter what it reads lean, esp @ WOT. On the dyno it was saying 11.2-12.2 or so and the widband was between 15 and pegged. I need to look at a different wideband setup.

He also said it look like the car was running in closed loop, both normal driving and WOT... does this sound right?
 
Did they use a tailpipe sniffer to check your AF? They're known to have a lot leaner AF reading than normal.

I had my car dyno'd a couple years at a local ricer shop and my AF read through the roof. They suggested retuning it, but it took my car back to Tim. I put it on the dyno and everything was okay.
 
nope, he hooked the dyno wideband sensor up to the rear 02 bung on the x pipe. The other rear bung is where I have my wideband plugged into.

He said that Tims tune was commanding 11.1 AF, and I was hitting 11.4-12.1- he said this was because the MAF transfer was off.... any truth to this?
 
Yes very true. MAF Xfer function is what determines how much fuel will be added. The EEc needs to know how much air is coming in so it knows how much fuel to add to get the "commanded" lambda or A/F. If the Xfer function is off...in your case its too low, thinking a lower amount of air is coming in per X AD counts it wont add enough fuel. See AD counts have an air flow Xper MINUTE value to them. And 0-1024 AD counts is 0-5V. So 2.5V is 612 AD counts and whatever #per min value is there is how much fuel the EEc will add based on comanded fuel and a few other paramteres.

Hope that helps :)
 
Negitive. The tune should switch switch to open loop while @ WOT. If its staying in closed loop. its watching the readings from the 02 sensors. In that case that may cause your A/F to start leaning out from it "learning" that its not @ 14.7 A/F. I belive commanded lambda is only used while in open loop so even though Tim is commanding 11-1 A/F, its not using it.

For instance in normal open loop WOT operation you can determine commanded lambda (or A/F) by watching your short term fuel trims. When you go WOT the EEC makes the front 02s read whatever the commanded lambda is at that RPM range...so inotherwords 0 correction because it thinks its dead on no matter what your actual A/F is.
For a 11-1 your front 02s should be reading .752 in Lambda. 1.0 Lambda is 14.64 A/F BTW so you can just do the math.

Heh its been too long since I have use my PRP! Im forgetting things :(
 
Email replied....he was telling you wrong.

In your second log your car is running closed loop at part throttle and then switched to OPEN when he goes WOT. PERFECT

First log it was running in open loop for the few seconds before and after the dyno pull, and if he just fired the car back up, thats exactly what its going to do. Also probbaly ran closed after due to a setting thats timable to set how long to stay in open loop after WOT or something like that. If thats set high that would explain that. He also could have loaded the wrong PID for that log...sometimes there are a few "MAF ad count" or a few "open loop flag" , ect PID values to log. Some are accurate and others give weird and random readings.

Im not so sure about that "tuner" though LOL.