Unexplained Fuel Cut on Datalog WOT 1st gear pull
#1
Junior Member
Thread Starter
Join Date: Sep 2017
Location: Baltimore; States
Posts: 190
Total Cats: -35
![Default](https://www.miataturbo.net/images/icons/icon1.gif)
MS2PNP, 1994 1.8l. turbocharged
rev limiter is coolant temp based and set up properly.
overboost protection is spark only and set at 190kpa or higher.
For some reason whenever I do a WOT pull, especially at an autocross in 1st gear WOT, the engine LOVES to fuel cut on me and I have no idea why. I finally had time to re-create the scenario today. Was happy for a moment until I checked the datalog and well the plot thickened.... Because it IS a fuel cut. (PW = 0) but there is absolutely no reason to back up why. It's not OBP because it always happens well lower than the target boost level. Just seems to mostly happen on WOT events right when the boost starts to build and RPM is high but not that high. Any suggestions or guesses guys? Ty
rev limiter is coolant temp based and set up properly.
overboost protection is spark only and set at 190kpa or higher.
For some reason whenever I do a WOT pull, especially at an autocross in 1st gear WOT, the engine LOVES to fuel cut on me and I have no idea why. I finally had time to re-create the scenario today. Was happy for a moment until I checked the datalog and well the plot thickened.... Because it IS a fuel cut. (PW = 0) but there is absolutely no reason to back up why. It's not OBP because it always happens well lower than the target boost level. Just seems to mostly happen on WOT events right when the boost starts to build and RPM is high but not that high. Any suggestions or guesses guys? Ty
Last edited by NASSEX; 06-21-2019 at 09:26 AM.
#3
Junior Member
Thread Starter
Join Date: Sep 2017
Location: Baltimore; States
Posts: 190
Total Cats: -35
![Default](https://www.miataturbo.net/images/icons/icon1.gif)
Thanks here's my tune attached. I'm hoping to have this problem fixed by the next autocross coming next Saturday morning.
I did some looking stuff up online tonight but couldn't find really someone having the same exact problem. It's getting late so I figured it'd be smart to post a topic to read back at in the morning. Have you ever seen that before? It's Pretty odd... I'm hoping it's not like it could be a gremlin somewhere on my overall setup or the MS hardware.
I did some looking stuff up online tonight but couldn't find really someone having the same exact problem. It's getting late so I figured it'd be smart to post a topic to read back at in the morning. Have you ever seen that before? It's Pretty odd... I'm hoping it's not like it could be a gremlin somewhere on my overall setup or the MS hardware.
Last edited by NASSEX; 06-20-2019 at 11:56 PM.
#8
![Default](https://www.miataturbo.net/images/icons/icon1.gif)
Don't see anything glaring in the tune - but my gut tells me it's probably a VR conditioner trimpot (r56 / r52) - but I don't see any sync losses occuring in your log at the same time. Either way, bust it open and turn it a few directions one way, see if it gets better. If it gets worse, turn it the other way.
#9
Junior Member
Thread Starter
Join Date: Sep 2017
Location: Baltimore; States
Posts: 190
Total Cats: -35
![Default](https://www.miataturbo.net/images/icons/icon1.gif)
I would rather not mess with anything inside the megasquirt case if i don't have to. It should be setup properly. The unit is less than a year or two old. I just purchased it 2 months and 1 year ago. I mean I'm comfortable with checking if there's any cold solders and stuff but i think it's setup as it should. Every single thing else has no problems. Car runs great all the features and option pin ports do as they should. It's just weird and having that one problem only with WOT and as it comes onto medium boost quickly.
And also I'm not playing a prank or anything trying to waste ur guys time, that IS my current tune. But nonetheless that issue has been there from the beginnings, it's taught me to stay off WOT and enjoy the car without doing wot from the very first time it happened I've kinda been scared lol. But i always thought it was boost cut or something.
Just since recently I've been doing autocross and going WOT in 1st has made it very apparently consistent. So i want to explore fixing it. Yet my overboost protection is set as spark cut. So what could this be lol
And also I'm not playing a prank or anything trying to waste ur guys time, that IS my current tune. But nonetheless that issue has been there from the beginnings, it's taught me to stay off WOT and enjoy the car without doing wot from the very first time it happened I've kinda been scared lol. But i always thought it was boost cut or something.
Just since recently I've been doing autocross and going WOT in 1st has made it very apparently consistent. So i want to explore fixing it. Yet my overboost protection is set as spark cut. So what could this be lol
#18
Junior Member
Thread Starter
Join Date: Sep 2017
Location: Baltimore; States
Posts: 190
Total Cats: -35
![Default](https://www.miataturbo.net/images/icons/icon1.gif)
Yes, I can part throttle my way everywhere lol I've been doing so for around 8 months now. Part throttle anywhere from 0 to like 60 or 80% it'll hardly ever happen. Anytime it's in the area of 90% or above TPS, it does it.
I can part throttle my way to my rev limiter, my boost target, or even have the overboost protection happen at times with it not happening. It's so freaking weird.
I never realized how weird it was until yesterday because I never investigated it through a data log lol always assumed I was just hitting a safety net of my own
yet I did start thinking to myself more recently when it happens that it couldn't of overboosted, so I assumed it was AFR or Acceleration enrichment related. But now that I've got more into fining out the edges of the tune, it doesn't explain for it.
It might possibly be a AFR safety net feature inside of MS2pnp's code that isn't accessible through tuner studio perhaps?
I can part throttle my way to my rev limiter, my boost target, or even have the overboost protection happen at times with it not happening. It's so freaking weird.
I never realized how weird it was until yesterday because I never investigated it through a data log lol always assumed I was just hitting a safety net of my own
yet I did start thinking to myself more recently when it happens that it couldn't of overboosted, so I assumed it was AFR or Acceleration enrichment related. But now that I've got more into fining out the edges of the tune, it doesn't explain for it.
It might possibly be a AFR safety net feature inside of MS2pnp's code that isn't accessible through tuner studio perhaps?
#19
Junior Member
Thread Starter
Join Date: Sep 2017
Location: Baltimore; States
Posts: 190
Total Cats: -35
![Default](https://www.miataturbo.net/images/icons/icon1.gif)
1 random suggestion for what it could be but i don't know the answer.
Fuel tank was on about 1/4th full. Maybe the fuel pump pickup hit a patch of air, but is mega-squirt 2 PNP capable of sensing when that happens, and cut's the PW / injector duty cycles until fuel pressure is back?? o.O
That's about the ONLY bright idea that I have
Fuel tank was on about 1/4th full. Maybe the fuel pump pickup hit a patch of air, but is mega-squirt 2 PNP capable of sensing when that happens, and cut's the PW / injector duty cycles until fuel pressure is back?? o.O
That's about the ONLY bright idea that I have
#20
![Default](https://www.miataturbo.net/images/icons/icon1.gif)
1 random suggestion for what it could be but i don't know the answer.
Fuel tank was on about 1/4th full. Maybe the fuel pump pickup hit a patch of air, but is mega-squirt 2 PNP capable of sensing when that happens, and cut's the PW / injector duty cycles until fuel pressure is back?? o.O
That's about the ONLY bright idea that I have
Fuel tank was on about 1/4th full. Maybe the fuel pump pickup hit a patch of air, but is mega-squirt 2 PNP capable of sensing when that happens, and cut's the PW / injector duty cycles until fuel pressure is back?? o.O
That's about the ONLY bright idea that I have
Status2 and Status3 show spark cut and fuel cut. After looking at your tune the obvious setting that cuts both is your rev limiter setting. You have a coolant based rev limit set for 5k when over 90% TPS which is where the cut is happening. It doesn't look like it should be triggering at the coolant temps your log is showing but try changing from coolant based to normal.