Jump to content

No crank, no fuel pump, no start

DanTheBetterMan
 Share

Recommended Posts

DanTheBetterMan New Member

DanTheBetterMan

Posted
Posted (edited)

Hey guys, I have a problem I can't solve and I'm hoping someone here can help. Last night I was driving my 2011 GMC Sierra 2WD 5.3L and pulled into a gas station. When I got back in the truck I turned the key to the start position but nothing happened besides the dash going black. I didn't hear the starter click and I didn't hear the fuel pump turn on. 

 

So far here's what I've done:

  • Tried to jump the car, no success.
  • Took the battery to get tested and it's fine. 
  • Switched the relays around to see if something else would quit working and the truck would start, but same outcome.
  • I jumped the two big connectors on the back of the starter and the starter turned over, but the truck never started
    • it actually kept turning even with the power off and didn't stop until I disconnected the battery
  • I replaced the battery in the remote but this didn't fix anything. I thought it might be anti-theft related but the the light on the dash isn't on for the alarm and the truck locks and unlocks with the remote.
  • I connected a scanner to it and am able to see the ecm getting an ignition signal when I turn the key to start
  • Through the scanner I can see that the ECM recognizes that the transmission is in park/neutral

Has anyone ran into this before? Is there anything else that would prevent it from starting and cause a no crank, no fuel, no start issue that I need to check? The monitor I'm using has the ability to check basically any sensor value. 

 

Thanks!

Edited by DanTheBetterMan
CamGTP Senior Enthusiast

CamGTP

Posted
Posted

Check/remove and clean all your engine/frame grounds that you can find in the engine compartment.

 

This is where I would start.

  • Like 1
DanTheBetterMan New Member

DanTheBetterMan

Posted
  • Author
Posted

All, I was finally able to figure it out. Here's what I did for anyone else that runs into this in the future:

  1. Jumped the starter solenoid with the key in the ON position
    1. This confirmed that the starter and solenoid were both working and that the truck would start
  2. Checked for voltage at the purple wire going to the solenoid as the key was turned to the start position
    1. No voltage was present
  3. Removed STRTR relay from fuse panel and jumped the battery terminal and solenoid terminal while key was ON
    1. Solenoid did not engage, leading me to believe there was a short in the wire since I was able to see that the wire went directly from the relay terminal to the starter on the wiring diagram
  4. Checked 40A STRTR fuse and found that it was blown.
    1. Replaced fuse and tried to start the truck but blew the second fuse, further confirming there was a short in the wire
  5. Checked for resistance between the purple wire and a ground and found there was conductivity there confirming there was a short somewhere
  6. Traced the wire from the solenoid back to the relay and discovered the harness had been rubbing on the transmission return line to the radiator next to the steering column

Once I figured out the issue I taped the wire back up and used a new harness sheath to protect it from rubbing again. I also rerouted it to avoid rubbing with the same line. 

  • Like 2
diyer2 Senior Enthusiast

diyer2

Posted
Posted
9 minutes ago, DanTheBetterMan said:

Traced the wire from the solenoid back to the relay and discovered the harness had been rubbing on the transmission return line to the radiator next to the steering column

How did this happen?

:)

DanTheBetterMan New Member

DanTheBetterMan

Posted
  • Author
Posted
1 hour ago, diyer2 said:

How did this happen?

:)

@diyer2 the harness was routed between the power steering line and the transmissions line, which only have about 3/4" between them, and the plastic sheath that normally protects the harness was so old that it disintegrated leaving the harness susceptible to the rubbing from the transmission line. Not sure if it was routed like that from the factory, or if someone rerouted it, but it was not very smart either way.

  • Like 1
DanTheBetterMan New Member

DanTheBetterMan

Posted
  • Author
Posted
2 hours ago, davester said:

Thanks for posting you fix, and bonus points for the writeup.  Those kind of electrical problems really suck to find...

I've benefited a lot from forums like this so I figured the least I could do was try to help someone else :)

  • 1 year later...

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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
    • davester
      Replacement Radiator

      By davester · Posted

      And use RA's 5% discount code if you buy from them.  google for the code, one is always available.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...