YakkoWarner
Full Access Member
- Joined
- May 29, 2024
- Posts
- 188
- Reaction score
- 252
- Location
- Central Texas
- First Name
- Wolf
- Truck Year
- 1989
- Truck Model
- R2500 Suburban
- Engine Size
- 454
I started a new thread because the previous one where we were trying to solve random shut-offs may no longer be relevant...
Over the weekend I had an out of town music job which meant I needed to run the 1989 Suburban out there (about 70 miles each way). After replacing the fuel pump relay which by all logic should have NOTHING to do with the random shut-offs, it ran all the way out there and all the way back without ever losing the ignition/fuel pulse. That should be a good thing (and in some ways it is), but now other seemingly unrelated problems popped in.
I had no trouble on the way out at all, just my intermittant 44-LeanRun error which is supposedly caused by a vacuum leak which cannot be detected. I think this is a separate issue from the electronic gremlins. I checked the codes once I got to the venue, only error 44.
After the show I had to make a very short trip (2 miles) for food - on the way out it ran almost perfect...it experienced one minor hesitation (almost more like a stumble) which didn't trigger any codes. On the way back, just the intermittant error 44. Loaded all my gear back in, and idled my way out of the parking area (long winding path) just fine, no codes showing.
Once on the actual road, as soon as I tried to accellerate it started bucking and audibly popping back through the air cleaner, and of course immediately the SES light came back on. I ran slowly up the shoulder knowing there was a gas station parking lot about a mile or 2 up the road where I could safely stop, and any time I tried to use more than a slight hint of throttle it would pop and buck again. Out of desperation (and remembering what was happening last week) I clicked it into neutral and switched off the key, then restarted. The restart cleared the popping and bucking - I was able to run at the speed limit from that point, but it sounded almost like there was a misfire on one of the cylinders...by the time I got to the gas station I had intended to pull off into even that had cleared up and it proceeded to run just fine the entire remaining 60-something miles home without any further issues. Once home I checked the codes again and now I have a 32-EGR error, and a 42-SparkControl error, but at no point did it ever actually shut itself off.
At this point I'm afraid to drive it anywhere. Power cycling the ignition system should not fix anything - if the module was bad or overheated, off and on wouldn't magically cool it down. A bad ground wouldn't just become good again. The coil wouldn't just start working again. The turn it off and back on again trick will stop working at some point. The only things that SHOULD be able to make it pop back through the air cleaner like that would be a bad intake valve, serious head gasket failure or incredibly over-advanced timing. None of which should change merely by power cycling.
I was unable to run the checklist from the manual for the no-spark/no-fuel issue because that never reappeared. And when I start it up at home in the driveway, it sits and idles fine for as long as I let it.
If there were any shops that still worked on these things I'd be making the appointment today - I have reached the end of what I can do at home. With only generic vague error codes as guides, there is no real way to determine what else could be happening. This feels for all the world like bad grounding problems, but everything I have read says NOT to ground the ECU itself because that can cause weird current loops. The negative cable from the battery goes right to the engine, if you're not supposed to ground the ECU to the body that presumably there must be a ground somewhere on the engine for it, but I'm 100% stumped on where.
I'm starting to think it is either haunted, or somwhere in the bowels of the black boxes there is a copy of Windows 3.1 running which needs to be rebooted every couple hours...
Over the weekend I had an out of town music job which meant I needed to run the 1989 Suburban out there (about 70 miles each way). After replacing the fuel pump relay which by all logic should have NOTHING to do with the random shut-offs, it ran all the way out there and all the way back without ever losing the ignition/fuel pulse. That should be a good thing (and in some ways it is), but now other seemingly unrelated problems popped in.
I had no trouble on the way out at all, just my intermittant 44-LeanRun error which is supposedly caused by a vacuum leak which cannot be detected. I think this is a separate issue from the electronic gremlins. I checked the codes once I got to the venue, only error 44.
After the show I had to make a very short trip (2 miles) for food - on the way out it ran almost perfect...it experienced one minor hesitation (almost more like a stumble) which didn't trigger any codes. On the way back, just the intermittant error 44. Loaded all my gear back in, and idled my way out of the parking area (long winding path) just fine, no codes showing.
Once on the actual road, as soon as I tried to accellerate it started bucking and audibly popping back through the air cleaner, and of course immediately the SES light came back on. I ran slowly up the shoulder knowing there was a gas station parking lot about a mile or 2 up the road where I could safely stop, and any time I tried to use more than a slight hint of throttle it would pop and buck again. Out of desperation (and remembering what was happening last week) I clicked it into neutral and switched off the key, then restarted. The restart cleared the popping and bucking - I was able to run at the speed limit from that point, but it sounded almost like there was a misfire on one of the cylinders...by the time I got to the gas station I had intended to pull off into even that had cleared up and it proceeded to run just fine the entire remaining 60-something miles home without any further issues. Once home I checked the codes again and now I have a 32-EGR error, and a 42-SparkControl error, but at no point did it ever actually shut itself off.
At this point I'm afraid to drive it anywhere. Power cycling the ignition system should not fix anything - if the module was bad or overheated, off and on wouldn't magically cool it down. A bad ground wouldn't just become good again. The coil wouldn't just start working again. The turn it off and back on again trick will stop working at some point. The only things that SHOULD be able to make it pop back through the air cleaner like that would be a bad intake valve, serious head gasket failure or incredibly over-advanced timing. None of which should change merely by power cycling.
I was unable to run the checklist from the manual for the no-spark/no-fuel issue because that never reappeared. And when I start it up at home in the driveway, it sits and idles fine for as long as I let it.
If there were any shops that still worked on these things I'd be making the appointment today - I have reached the end of what I can do at home. With only generic vague error codes as guides, there is no real way to determine what else could be happening. This feels for all the world like bad grounding problems, but everything I have read says NOT to ground the ECU itself because that can cause weird current loops. The negative cable from the battery goes right to the engine, if you're not supposed to ground the ECU to the body that presumably there must be a ground somewhere on the engine for it, but I'm 100% stumped on where.
I'm starting to think it is either haunted, or somwhere in the bowels of the black boxes there is a copy of Windows 3.1 running which needs to be rebooted every couple hours...