• Welcome to The Truck Stop! We see you haven't REGISTERED yet.

    Your truck knowledge is missing!
    • Registration is FREE , all we need is your birthday and email. (We don't share ANY data with ANYONE)
    • We have tons of knowledge here for your diesel truck!
    • Post your own topics and reply to existing threads to help others out!
    • NO ADS! The site is fully functional and ad free!
    CLICK HERE TO REGISTER!

    Problems registering? Click here to contact us!

    Already registered, but need a PASSWORD RESET? CLICK HERE TO RESET YOUR PASSWORD!

Stalled today and set codes

Chief915

915A Maint Tech
Messages
406
Reaction score
1
Location
Cecilia, KY
I have put almost 600 miles on the suburban since I got it almost two weeks ago and haven't had any problems or hiccups until today, it has ran great up until now.

I was riding along this morning at about 30 mph and had to slow down for a traffic light. Pretty much as soon as I took my foot of the pedal, the truck shut off just like I had shut the key off. The dash stayed lit with the battery light, but no check engine light if I remember right. Of course my first thought was something like :WTF: I stopped at the light and tried to start it, it turned over a good 10 - 15 times and fired up with a pretty decent shot of black smoke out the exhaust and idled noticably more rattly than usual. It still ran smooth, not like it had air in the fuel lines, just a lot noisier/rattly than normal. Once it started, the check engine light was on and it had very low power, but no smoke at all, and when I say low power... I had to go about 1/2 throttle to slowly get up to 30 mph. I pulled into a parking lot and looked around under the hood, didn't see anything out of place.

I drove it home, about 3 miles, and checked the codes. I had 18 ( Pump Cam Reference Pulse Error) and 35 (Injection Pulse Width Error (Time Short)) stored. I know these two were from the stalling event, because I had checked for codes out of curiosity the night before and there weren't any current or historical codes in the ECM. I cleared the codes and drove it the rest of the day. After clearing the codes, power and everything was back to normal. Later on in the day the check engine light flashed on for about 2 or 3 seconds, then went back off again. It didn't stall or anything and drivability stayed normal the rest of the day. When I checked the codes again, after the second check engine light, I had a code 36 (Injection Pulse Width Error (Time Long)).

Any thoughts?
 
Well now you know why they sold it!

Check your grounds.

Then look at the PMD relocation checking wires etc.
 
pmd sets those codes just went thru same problem but check all grounds and fuse box for corrosion on fuses also unplug all engine connecters and clean with tv tuner cleaner then put correct electical anti corrosive lube back on the connectors use very little dont goob it all almost forgot gm had promblems with ignition keys switch turning off the power to computer pull all connecters to steering colume clean and lube
 
As always,check fuel supply first and change filter.

Fuel system - It has a fairly new looking LP on it, I know looks don't matter, but the LP runs and has good flow from the FFM drain tube. I drained about half a soda bottle out a couple days ago and the fuel looked very clean, no water or junk in it. The fuel filter looks fairly new as well, but I will change it out this weekend just so I KNOW it's new.


Well now you know why they sold it!

Check your grounds.

Then look at the PMD relocation checking wires etc.

I hope it doesn't have secret gremlins hiding on me......

PMD is relocated on the skid plate with a heath kit. The weatherpack connectors are in good shape, no corrosion or water in the plugs.

I will clean grounds this weekend too, it was already on the TO-DO list.

pmd sets those codes just went thru same problem but check all grounds and fuse box for corrosion on fuses also unplug all engine connecters and clean with tv tuner cleaner then put correct electical anti corrosive lube back on the connectors use very little dont goob it all almost forgot gm had promblems with ignition keys switch turning off the power to computer pull all connecters to steering colume clean and lube

I will clean these connectors too this weekend.



Thanks for the help.
 
These are Optical Sensor (OS) issues on the IP that sent your truck into backup fuel mode, aka limp mode. The 18 specifically is an OS signal failure, but you didnt get other OS failure codes. The 36 is something also IP related, can be PMD related, or fuel or air in the fuel or any number of things. Neither should stall the truck necessarily, which is why I would suspect that air in the fuel caused the codes and stalled the truck. The truck can run on one of two timing sources, the Crank Position Sensor (CPS) or OS. When you only have one starting time is extended to about 10 seconds and it will be in limp mode with high idle and set a constant fuel pulse width, which is why it was stubborn to start and more rattly.

You can inspect for potential air intrusion areas, or you can also try cleaning the OS eye which would then require a scanner to get the OS reinstalled correctly.
 
These are Optical Sensor (OS) issues on the IP that sent your truck into backup fuel mode, aka limp mode. The 18 specifically is an OS signal failure, but you didnt get other OS failure codes. The 36 is something also IP related, can be PMD related, or fuel or air in the fuel or any number of things. Neither should stall the truck necessarily, which is why I would suspect that air in the fuel caused the codes and stalled the truck. The truck can run on one of two timing sources, the Crank Position Sensor (CPS) or OS. When you only have one starting time is extended to about 10 seconds and it will be in limp mode with high idle and set a constant fuel pulse width, which is why it was stubborn to start and more rattly.

You can inspect for potential air intrusion areas, or you can also try cleaning the OS eye which would then require a scanner to get the OS reinstalled correctly.

That all makes a lot of sense.

How do you go about cleaning the OS eye? I have a scanner (a pro-link), but I cannot perform TDCO with it. It will show me a data list that shows all sensor values, will this scanner work for getting the OS resinstalled correctly?

Thanks for the help
 
You should set the TDCO after getting the OS dialed in. GMTDScanTech is good for that. I would first check out the fuel lines on top of the fuel tank to the LP, see if they are rotted, where the LP can pull air in, and try the clear hose on the IP.

But to get the OS dialed in you just need to be able to read the commanded fuel rate, which should be approximately 8mm3 at warm idle. There is more info in the attached file
 

Attachments

  • Mnx&Mods info.pdf
    1.7 MB · Views: 16
Back
Top