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

    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
    • Rockauto bud. I pass local stores for parts.   Findya something online. 
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...