Potentially, the WO2 has done this a couple other times a while ago, although I replaced the sensor and calibrated it fairly recently. I can try to make this happen again, during that last log it occurred after entering PE mode.
Sent from Tapatalk mobile
Right, only the wideband reading. I have a chance to replicate the conditions of my log tomorrow, I'll try to recreate the problem. It's been an anomaly though, not sure if I'll be able to replicate that lean reading.
Sent from Tapatalk mobile
No, it's not just the wideband. Take a look at his last log... it loses the MAF Freq and MAF airflow from frames 2905-2921. Also, the wideband freezes at 16.9AFR for those same frames and it looks like fuel trims freeze for frames 2908-2921. I've also been trying to dial in a chronic rich tip-in and all of a sudden I now have a severe lean tip-in. It's like I'm starting from scratch. There's something really wrong here.
I think that 2905-2921 loss of MAF is when I turned the ignition off (still had it in gear for a moment while moving). The WO2 stays at 16.90:1 from 2904-2959, which correlates to when I turned off the ignition, turned it back on, and a few seconds later the WO2 booted up and started outputting data again. This is also the same period that my voltage goes to zero.
Although that's not to say that something wonky is not going on. I'm wondering if it's related to the electrical charging system? I say that for a few reasons, as follows:
1. The car has 198,000 miles on it. I got it with 105,000 miles in 2012, and replaced the battery in 2013 or 2014 (no date code on the battery). So things are old.
2. When I have the headlights on, the engine will surge a bit when I put it in neutral, or if I'm doing on/off clutch maneuvering in a parking lot or driveway. If I turn the headlights off, surging is almost non-existent.
3. Last week when it was ridiculously cold here (below freezing), I had the ignition on for a few minutes in the morning before I left for work playing with the windshield wipers and it drained the battery enough that it wouldn't start.
Voltage in the logs looks fine to me. In the last log, if you remove the data from the end of the log when I turned the ignition off and the portion of data from 2905-2919 where I turned the ignition off while moving, voltage is 12.5-14.2V for the whole log. The 12.5V drop is at frame 10,893, and everywhere else I'm 13.9V or higher.
Any thoughts on that? Any potential troubleshooting tasks I can perform?
Okay. I didn't know that you turned off the ignition while you were driving. Let's assume for now that changing over to the new MAF sensor has made the fueling go a bit wonky. We're still dialing that in... so it just means that it will take a bit longer now to do that. The logged battery voltage is good... so your charging system is good, but you might want to consider getting a new battery soon. I don't know why your wideband randomly goes crazy and I don't know all that much about wideband troubleshooting, so I can't offer any suggestions there. Maybe joecar will be able to help with that.
With this update I'd like you to do your normal driving log, but right at the end of the log before you shutdown the engine I'd like you to do something extra... I want you to let it idle for a few seconds with headlights off, then blip the throttle and let the idle settle for a few seconds, then put the headlights on and let it idle for a few seconds and then blip the throttle again and then let the idle settle for a few seconds again.
Last edited by statesman; May 2nd, 2019 at 01:41 AM.
Not a problem, I have a bad habit of not being very clear! I'll try to do better with that. I'll start looking at new batteries, it's probably due for a replacement.
I flashed your tune, let my car warm up a little bit, reset the fuel trims, and took the long drive home. Overall there's a little less bucking, and the engine definitely does a better job not surging when in neutral. I had the headlights and heater on the whole drive home due to weather, but did as you asked once I got in my driveway. Below are my notes on the log:
ECT hits 80C at frame 1303.
Bucking during deceleration:
Frames 1917-1964
Frames 2143-2181
Frames 3685-3719
Frames 4215-4346
Frames 5582-5608
Frames 5891-5950
Frames 5989-6028
Frames 8975-9014
Frames 10305-10369 (stronger bucking here)
Bucking under light throttle:
Frames 2091-2135
Frames 2581-2702
Frames 3012-3091
Frames 4351-4398
Frames 4576-4653 (stronger bucking here)
Frames 10088-10116
Once I got in my driveway, I did the idle/blip for you.
Headlights on, frames 14020-14247
Headlights on, idle, frames 14019-14099
Headlights on, small roll forward, frames 14095-14138 and 14154-14196
Headlights on, quick throttle blip, frames 14200-14240
Headlights off, frames 14285-end of log
Headlights off, idle, frames 14337-14362
Headlights off, small roll forward, frames 14299-14336 and 14364-14401
Headlights off, quick throttle blip, frames 14427-14460
I then pulled in the garage, let it idle with the lights off, and turned it off. Surging in neutral seems to be much better, although if you look at frames 12276-12320 you can see some surging while I battle traffic.
Let me know what you think. Again, thank you very much for the help! If you think of any other specific tests you want me to run, just say the word and I'll give it a shot!
Log:
GTO Feb 11 2019 IBC to home.efi
This must have been a horrible car to drive before I started helping you.
I'm making quite a few adjustments with this tune update. It should be alright, but there's a small chance that some of the changes will clash with other changes and could make the bucking worse in some situations... so if your bucking gets any worse with this update, just say so.
Do your log the same as last time, including the throttle blips at the end of the log. Also, try to replicate the surging while battling traffic.
Last edited by statesman; May 2nd, 2019 at 01:41 AM.
Alright I'll flash it and get a log, making sure to get some idle surging and throttle blip data. It was definitely not enjoyable when cruising around traffic. I thought I was making some headway, but then I hit a wall and started this thread.