Jump to content

Recommended Posts

Posted (edited)

Hello. New here, but read some threads on this topic. I have a 2001 8.1 l in a 2500 HD with Allison. Very randomly stalling. Some times it will loose all power. All gauges stay up, but speed falls and absolutely have no power. It then sputters a little and comes back to life. May not give the problem again for weeks. I have replaced the crank sensor, cam sensor, mass airflow sensor, fuel filter, plugs and wires, with no luck. Will not throw a code. Took it to the dealer last week. They did get it to show its horns once with their computer on it. But did not give any fault codes. He also claims he had a fuel pressure gauge on it, and it did not lose fuel pressure. Everything I read sounds like the above replaced parts fixed the issue. Not my situation. Once in a while it will completely die. Will turn over, but nit fire. A minute or two later it will start and run perfect. Any ideas. Thanks in advance! Note: Truck has 115,000 miles on it, and is flawless mechanically and structurally other than this. Its been pampered. 

Edited by Hvactech
Posted

This will surely sound like a broken record to most in this forum..........

 Get some Throttlebody cleaner ( NOt carb cleaner, Actual Throttlebody cleaner)

Remove the air intake and clean the throttle, the plate, BOTH sides and the whole thing inside,

SPOTLESS. Yes Spotless.  This has caused this problem on 2 trucks I have owned similar vintage.

 I guarantee you have dirt on your plate somewhere or throttle housing. beyond the plate on the bottom.

 ps, mine did NOT throw the CE or a code either.

 I would use COPPER never seize on the plug threads...

 Good luck....

Posted

When it's very long between problems the throttle blade doesn't seem like it would be it. Those 8.1's are drive by wire too if I remember right so the blade is always open.

 

These problems are pretty hard to diag when it doesn't happen all the time. Could be the TB itself internally, the pedal assembly or a wiring issue somewhere in the harness.

Posted

Thank you. I will try it. Formulabruce, will I need a computer/scanner to reprogram the idle position once cleaned, or not a concern on this truck? I read on the models a little newer you have to. 

Posted

Ok.....cleaned throttle body as recommended above. Also replaced the throttling position sensor just to rule it out. Took it for a test run. Same ****** happened. Ran perfect. About 15 minutes into the drive, lost power. The gauges did drop momentarily, dash lights, radio ect...stayed on. While coasting, the truck came back to life without me starting or doing anything, and ran fine for the remainder of the drive. I'm striking out here.

Posted

Darn,you think it's worth a fuel pressure test of your own?and do you hear pump after stall with key on for the 2 seconds?

Posted

I ran a fuel pressure gauge up under the wiper cowl to the windshield and drove it for 200 miles over a couple weeks. Never acted up. Took it off and seriously within the first 2 miles it lost power. I'm putting it back on tomorrow.  Honestly, I keep going back to fuel, but I don't know. I'm always driving when it loses power, so can't really hear the fuel pump. The few times its actually stalled, I've been in traffic with a horse trailer, so listening for a fuel pump isn't high on my list. I checked all the battery cables and grounds tonight. Pulled up the fuse box and made sure there were no chewed or burned wires ect.. all looks good. Wiggled every wire harness and plug I could find while idling,  and could not get it to replicate. Did notice that the wires going to the fuel pump on top of the tank were hot. Not melting or burning hot, but plenty warm. Wondering if a fuel pump can thermal out? Getting to the point of changing the pump. Heck, everything else is new, that might as well be to. Fuel filter is new. If anyone has any more suggestions, i would appreciate it. Thanks

Posted

Next is Engine and computer grounds. ( trying easiest first)

 BCM ground is under Driver door cab mount facing rearward. Clean it well, and then put some waterproof grease on it, ( marine grease)

 pass side of engine to cowl or frame should be a ground.

 Intermittent ground could be an issue as this sounds only  electrical now to me

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Latest Articles

  • Posts

    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
    • I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...