Jump to content

Stop For Lunch, Comeback To Crank But No Start

2500HDR

Recommended Posts

2500HDR New Member

2500HDR

Posted
Posted

Ok guys, tell me what you think.

 

First time I've ever had any issues with my '06 2500HD Duramax LBZ/Allison with 74,000 miles all stock. Traveling last Saturday pulling my 5th wheel from Southern Oregon down Interstate 5 back to the Sacramento area after camping for a week. Stopped in Weed, CA for a quick bite after running through the ups and downs in the area, it was 2:30ish in the afternoon and in the high 80's, half a tank of fuel. Left the truck for about 30 minutes, came back, got in, cranked and it fired briefly and stopped. I cranked again but got no start. Over the next 3 hours I tried to restart with extended cranks a few more times. During that time I looked for things out of place and such, checked and had fuel at the bleed screw of the fuel pump housing and finally started pulling fuses for any circuit I though might have something to do with fuel pumps or ignition. It was after the fuse pulling and replacing that the truck started, but I think that was just coincidence. With the truck running I filled up and pulled the rest of the way home with no issues. Check engine light never came on during the extended crank periods and the truck runs fine today. So what are some thoughts? Vapor lock? Intermittent fuel pump?? Fluke???

 

Extra info after the fact. I changed the fuel filter 3 weeks before leaving on the trip with the napa gold plastic fuel filter. Maybe I have a torn o-ring.

 

Oregon uses a blended bio-diesel of 5% or 20% ratios. I purchased the B5 5% product for the week I was there. Is bio-diesel more volatile and prone to vaporization?

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

  • Latest Articles

  • Posts

    • Chuck FB
      Joke Thread

      By Chuck FB · Posted

      This video may not be the exact content for the joke thread but its a lot of laughs so here it is, I've only watched a portion of it so far but if anyone is looking for some light hearted good soap box driving action, its here. As a note in the upper left of the screen it shows the number out of 100 to refer back to any particular vehicle for comment !.    https://www.facebook.com/reel/1351928276956715
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...