drive slower
Don’t wash your car?
drive slower
Well, you have such a short span of power loss compared to a big sweeper, but the sound/feeling is similar. Mine just quit until it got fuel again. At Laguna Seca last year I was pulling hard T5 going uphill and stopped so much when it got fuel I had a huge backfire. I hope to find out this weekend at Thunderhill. At least I'll be ready for it if it does and make sure nobody is near me.@weendoggy - Looking like I’m going down the “cure fuel starvation” rabbit hole with you. Apparently, I wasn’t driving my car hard enough or with low enough fuel, to notice this before.
What do you think?
Got to thinking (bad sign) and you're running the Holley HP system, so, you can run a datalog and find out what fuel pressure you have during those times, IF you have a transducer connected to the system. If not, get one, very useful. I have one on my Cobra and nice to see what's happening. This way, you can purposely run the tank down and do a test during your run and I'll bet you see the FP drop like a rock!Well, you have such a short span of power loss compared to a big sweeper, but the sound/feeling is similar. Mine just quit until it got fuel again. At Laguna Seca last year I was pulling hard T5 going uphill and stopped so much when it got fuel I had a huge backfire. I hope to find out this weekend at Thunderhill. At least I'll be ready for it if it does and make sure nobody is near me.
If the transducer is hooked to the HP setup, it'll log it no matter what. You just pull the datalog file and select Sensors, if you don't have a custom one. I'd start the datalog prior to your run and then shut it off after you get through the lights/timer. No hurry, just capture your log. When you overlay the datalog to the tune, you'll see where it is, and/or just the log file will show the pressure drop. Also, mine only does it with 1/2 tank or less so be sure to not have enough fuel, or, do it both ways. Yeah, that's the ticket!Actually, I do log fuel pressure but was not at the time the stutter occured.
If the transducer is hooked to the HP setup, it'll log it no matter what. You just pull the datalog file and select Sensors, if you don't have a custom one. I'd start the datalog prior to your run and then shut it off after you get through the lights/timer. No hurry, just capture your log. When you overlay the datalog to the tune, you'll see where it is, and/or just the log file will show the pressure drop. Also, mine only does it with 1/2 tank or less so be sure to not have enough fuel, or, do it both ways. Yeah, that's the ticket!
If the transducer is hooked to the HP setup, it'll log it no matter what. You just pull the datalog file and select Sensors, if you don't have a custom one. I'd start the datalog prior to your run and then shut it off after you get through the lights/timer. No hurry, just capture your log. When you overlay the datalog to the tune, you'll see where it is, and/or just the log file will show the pressure drop. Also, mine only does it with 1/2 tank or less so be sure to not have enough fuel, or, do it both ways. Yeah, that's the ticket!
Good, but keep in mind the Learn Parameter settings is you setting how much you want the "learn" to adjust. So, if it's up to 100%, it's going to make those adjustments based upon your AF ratio and Base Fuel. The less % you allow, the less it will adjust to so it could still be either too rich/lean depending on where it's making its changes. Kind of a balancing act, but you get the picture. My rule-of-thumb is if I can keep my LT to show anythng below/above 10% adjustments. That tells me I'm really close. My settings are 25% for both CLP & LP, but that's based on doing Open Loop testing to get really close. If you want to test your theory, put it in OL and do some base driving. That'll tell you how close you really are. I learned at the Holley class as well as other good tuners to set the base idle in OL to really know what the engine wants, then go from there. If you have timing adjustability, that can play a role as well.Did some reading over the weekend and made an adjustment to the learn table in an attempt to solve a few issues. Noticed a few times last week that the car was idling very rich and I'd been experiencing low speed stall issues. Looking back, the HP was adding 100% fuel at all RPM/kPa levels and the car was essentially choking itself out when airflow demand was low. So, I revised values to 0% below 1000 rpms and 15% for the remainder of the table. Runs like a champ. The only lingering issue is finding the IAC settings to keep the idle a little higher coming off throttle when coasting to a stop. It still stalls occasionally but I'll accept that for now.
It thought when the holley data logged it did it for all the sensors? At least that has been my experience.
I'd save the tune as "before_adjustment" or something you want. This will save the tune, log, LT and all else. Then, clear the LT, save that one as "after_adjustment", and drive in CL home (hopefully a good drive time) and then you and compare the two LT's. This will tell show you any HUGE differences between the two, given nothing else has changed and the driving style is hopefully the same/equal. IOW, try to be consistant between the two drives. If they both look equally the same, and it drives like crap, find out where the LT is gaining/losing fuel to meet your needs. You can try OL, but be aware that if it's way off, one way or the other, it'll run like crap too!@weendoggy
That being said, my CL table is still set to 100%. I drove the car to work today so, would you suggest that I drive home in open loop or adjust the table to reflect the LT until I have some free time to test theories?
Yes, you can create a custom or modify an existing menu selection to get what ever you want. I take a lot of unneeded stuff from a couple and put what I want in an order I like for my tired eyes to follow and this way I get exactly what I'm looking for. I also split my data log screen to keep the AF and Target AF separate from all the other sensors when viewing.I remember being able to set up a small menu bar of the specific sensors that I wanted to see for the log to make it easy, but that the data from all the sensors was available to put in that little menu bar either before or after the run? I have not messed with it for so long that I might be as up to date on this as I am the nfl.