Uh-Oh, Houston we have a problem
SteveO -
I am not sure what is going on. I have the turbo setup done, and car was running / driving yesterday. Before that, the 2 bar MAP tune, with the patch installed, was doing seemingly just fine - no issues running it NA with the 2 bar tune. Drove it a fair amount, always started and drove perfect.
Then yesterday, I drove the car and it ran fine. Didn't get into boost, just did some driving around to start with. All seemed well. I did a couple small things (crankcase breather, boost gauge, etc), and then was ready to do a little tuning, but after that the car will not start (talking a few hours later). Smelled of raw fuel it seemed to me.
Had some trouble getting my laptop to communicate with the ECM last night, which was alarming, but now this morning I am able to connect (reprogrammed the chip, reinstalled). I find that the barometric is now set at 10.36kPa!! I have no idea how this happened.
So, then I loaded the tune without the patch, and I think it then updated to current MAP reading (55.0) - which makes sense. So, then I loaded the patched tune back in, hoping that I would see the 54.6 setting in the tune patch, but it's still showing 55.0 via laptop. Does the engine need to be running for the patch to work? The patch doesn't seem to be taking effect, at least with the engine not running.
Then I thought I'd try the 1 bar tune, with the 1 bar sensor, so swapped all that in, but forgot I now have 60lb injectors, not 32. So perhaps that's flooded her again. That tune was for 32's
And it still won't start. I have tried cranking a lot without the INjector fuses in, thinking it may be flooded. Did get some smoke out of the tail pipe, and a bit of chugging, but it didn't really try to run. Then thinking I had it cleared out (no more smoke from tail pipe), I put fuses back in, and still nothing. No firing it seems.
So I guess I need to try to get it running again on the 1 bar tune, 1 bar MAP sensor, and put in the proper injector flow rate to just get it running again and start from there.
What's so perplexing is why it just all of a sudden decided to go stupid on me. Any thoughts?
Up and running, with code issue
OK, so long story shorter, I guess the cap and rotor was the problem. Why it just failed to start all of a sudden, I'm not really sure. Still running the original GM Opti, but now it's the vented style. Cool. Also added a hotter coil for good measure (MSD 8226 replacement drop in). Was able to jump the spark further on my tester than with the stock coil, so it's actually measurably better. Good deal.
Anyhow, the patch that's in the code doesn't seem to work as intended. It doesn't seem to "set" the baro reading manually as we intended, and the ECM is still updating the baro reading later it seems.
There is a reason I thought it worked before. When I use the unpatched code, it will update the baro setting as usual - and come up with 54-55 kPa or so based on 2 bar MAP. Then I go and use the patched code it will stay that same reading for a while, but at some point just putting around it will update again. I don't know what triggers this, but it throws the tune way out. Like from idling at 13.9 or so to idling at 15.7. Bam, all at once.
TunerPro and Scan9495 both report the ECM sees 10.35kPa as the baro reading at that point. (This was what I was seeing when the car failed to start, which sent me down the path of thinking it was fuel related. THey just HAD to be connected right??? :mad1:)
The car runs and drives even with the baro set at 10.35, which is surprising to me. But at least it can get home. It's actually not even that lean under boost when this happens, though not where i want to be. But using the patched code, the Baro does not update at key on, so it's kinda stuck at 10.35kPa.
I'm kinda thinking of trying the unpatched code a little more just to see what it does. Is it possible we fixed something that wasn't broke?
Or should I switch to unpatched code (to get back to 55kPa) , then go back to patched and try to see what circumstances are triggering the reset of baro reading? I think perhaps I can datalog for a bit, and should be able to see that in the log. Scan9495 seems to work better on my old laptop than TunerPro for some reason.