Jump to content

fuel pump not working, and my head is scratching.

spankrz

By spankrz
in Ask A GM Technician

Recommended Posts

spankrz Enthusiast

spankrz

Posted
Posted

my truck is a 07 nnbs silverado 1500 extended cab 6.5' bed 4x4 5.3 engine vin "j", almost 170,000 miles.

 

a couple of weeks ago check engine light came on, "lost communication with fuel pump" or something along those lines. cleared the code, light was back on within a few minutes. truck still ran as it should.

 

this morning, got in the truck to get some work done and it would not start. fuel guage still worked. starter would enguage and engine would turn over as it should, but would continue to do so without starting. tried turning key on and off several times to build up pressure, no luck there either.

 

-fuel pump fuse is fine checked with multimeter

-fuel pump relay is fine via swapping with an identical relay.

 

---pulled off bed---

 

-installed new fuel pump from carquest, no change. wiring connections looked clean and not burned. fuel guage works as it should.

 

---called local dealer. they recomended fuel pump control module (located above spare tire)---

 

-installed new gm fuel pump control module. no change.

 

---with my hand on top of the fuel pump and someone turning the key to the "run" position, i can fell that it does nothing at all when it should prime.---

 

sorry for the long post, just wanted to provide any details that someone may ask. i really hope it is not a wiring problem, as i would hate to cut up the nice neat factory harness to check for faulty wiring unless i absolutely have to.

 

ANY help or input would be appreciated. feel free to ask any questions, i usually wind up looking over the stupid simple things...

 

 

scooby5121 Enthusiast

scooby5121

Posted
Posted

i would look into the "lost communication with fuel pump"

error code you originally got with the dealer before pursuing any further with it.

 

It may be the cheapest way for a True Fix...

Scooby

scooby5121 Enthusiast

scooby5121

Posted
Posted

Well if you have a 200 to 2007 old body style Chevy or GMC truck you may
get that annoying abs and sometimes the fuel pump that won’t work. This
is a common issue and usually just a bad ground on the driver-side
frame just under the drivers door by the body mount. Simple repair just
unbolt these grounds and sand the frame where they make contact clean
the terminal as well. I would use 80 grit sandpaper to do this when you
got them clean just bolt them back up make sure they are tight and can’t
be moved by hand. Hope this one helps you out you can do this without
spending a dime.

 

Quotted from A gm site.

Scooby

gmtech4 Senior Enthusiast

gmtech4

Posted
Posted

i would look into the "lost communication with fuel pump"

error code you originally got with the dealer before pursuing any further with it.

 

It may be the cheapest way for a True Fix...

Scooby

^^^^^^^^^^^^^^^ +100 ,stop the shot guning of parts(i think you have at this point) ,,,,,,did ya have the FPCM programmed ?or did someone tell you its plug and play ?let me know ,i can look it up for you if ya want,,,

 

i believe ya looked past the computor controlled truck thing,,,good luck

spankrz Enthusiast

spankrz

Posted
  • Author
Posted

mine is the new body, it is the truck in my signature picture. i was thinking about hitting it hard with the voltmeter tomorrow, seeing where i have power and where i do not, checking my grounds along the way, doing what you said to grounds that arent very strong. i was really hopeful that there was something i was missing that should have been obvious to check, or maybe an electronic part that i don't know about that i need to make sure and check. thanks for your imput, as said before, any response is appreciated. i have a lot i need to haul right now, just trying to get it done.

spankrz Enthusiast

spankrz

Posted
  • Author
Posted

^^^^^^^^^^^^^^^ +100 ,stop the shot guning of parts(i think you have at this point) ,,,,,,did ya have the FPCM programmed ?or did someone tell you its plug and play ?let me know ,i can look it up for you if ya want,,,

 

i believe ya looked past the computor controlled truck thing,,,good luck

no, although my dealer reccomended that i install a new one, they failed to mention that the FPCM needs to be programmed. hopefully this is the "duh" response i am looking for. how do you program them?

gmtech4 Senior Enthusiast

gmtech4

Posted
Posted

no, although my dealer reccomended that i install a new one, they failed to mention that the FPCM needs to be programmed. hopefully this is the "duh" response i am looking for. how do you program them?

dealer programs them

gmtech4 Senior Enthusiast

gmtech4

Posted
Posted

i hope ya have schematics because ya have to understand the systems before self diagnosing ,going by the seat of your pants will not work ,,,,i hope the programing works ,,,,,,

 

good luck ,,,,,,take it there for a programming first !!!

spankrz Enthusiast

spankrz

Posted
  • Author
Posted

i may have to ask my dealer why the reccomended i buy a part, handed me the part new in the box, knowing exactly how i was going to use it, failed to mention that they needed to program it otherwise it was a $150 peice of plastic with a few useless circuts... maybe just a long day. any idea how much time they will charge to program it? half hour? hour?

gmtech4 Senior Enthusiast

gmtech4

Posted
Posted

i dont know ,cant be over an hour ,,,,

 

here is light reading,lol

 


Circuit/System
Description

Modules connected to the high speed GMLAN serial data circuits monitor for
serial data communications during normal vehicle operation. Operating
information and commands are exchanged among the modules when the ignition
switch is in any position other than OFF. The high speed GMLAN serial data
circuits must be operational for the vehicle to start due to body control module
(BCM) and engine control module (ECM)/powertrain control module (PCM)
communications. The theft deterrent module and ECM/PCM exchange information
using the BCM as the gateway module allowing communication between the high and
low speed serial data busses. The low speed GMLAN serial data circuit must also
be operational for vehicle starting.



Diagnostic Aids
  • Sometimes, while diagnosing a specific customer concern or after a repair,
    you may notice a history U-code present. However, there is no associated
    “current” or “active” status. Loss-of-communication U-codes such as these can
    set for a variety of reasons. Many times, they are transparent to the vehicle
    operator and technician, and/or have no associated symptoms. Eventually, they
    will erase themselves automatically after a number of fault-free ignition
    cycles. This condition would most likely be attributed to one of these
    scenarios:
    • A control module on the data communication circuit was disconnected while
      the communication circuit is awake.

    • Power to one or more modules was interrupted during diagnosis

    • A low battery condition was present, so some control modules stop
      communicating when battery voltage drops below a certain threshold.

    • Battery power was restored to the vehicle and control modules on the
      communication circuit did not all re-initialize at the same time.

    • If a loss-of-communication U-code appears in history for no apparent reason,
      it is most likely associated with one of the scenarios above. These are all
      temporary conditions and should never be interpreted as an intermittent fault,
      causing you to replace a part.

  • Do not replace a control module reporting a U-code. The U-code identifies
    which control module needs to be diagnosed for a communication issue.

  • Communication may be available between the BCM and the scan tool with the
    high speed GMLAN serial data system inoperative. This condition is due to the
    BCM using both the high and low speed GMLAN systems.

  • An open in the DLC ground circuit terminal 5 will allow the scan tool to
    operate but not communicate with the vehicle. When the scan tool attempts to
    communicate with the vehicle a message "no CANdi module detected" will be
    displayed.

  • The engine will not start when there is a total malfunction of the high
    speed GMLAN serial data bus.

  • Technicians may find various Local Area Network (LAN) communication
    Diagnostic Trouble Codes (DTC) and no low speed GMLAN communications with the
    scan tool.

  • The engine will not start when there is a total malfunction of the high
    speed GMLAN serial data bus.

    These conditions may be caused by the installation of an aftermarket
    navigation radio module (see bulletins). Some customers may comment of one or
    more of the following concerns:

    • Vehicle will not crank.

    • Vehicle cranks but will not start.

    • Vehicle stability enhancement system warning lights and messages.

    • PRNDL gear indicator position errors.

    • Tire Pressure Monitor (TPM) system warning lights.
spankrz Enthusiast

spankrz

Posted
  • Author
Posted

good reading. i guess here is possibly the most important question... does my dealer have to program the module through the obd2 port, meaning i would have to cough up the money for a tow, or can i hand them the module? i am guessing it will have to be obd2 but i hope not.

  • 2 weeks later...
  • 9 months later...
TJMaine Enthusiast

TJMaine

Posted
Posted

I did the same thing, local "largest GM dealer in maine" sold me the part and didnt say boo... now I got the old one out ( pissing water out of it ) and got the new one in but have to have it towed to drop 100 bones on a program... figures right?

Side note, my truck also has 170k is miles on it

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...