Jump to content

fuel rail pressure

Chris Hester
 Share

Recommended Posts

Chris Hester New Member

Chris Hester

Posted
Posted

i have 03 Silverado w/6.0 ...truck idles fine until you start drivingand try to accelerate then it goes to missing, coughing and sets 0332 code? fuel rail pressure shows to be 50 psi and will drop some at high idle...is it the fuel pump???

davester Senior Enthusiast

davester

Posted
Posted

not sure if '03 is returnless or return fuel system (ie, if there is one fuel line or two running from the tank to the engine).

 

If it is returnless (only 1 line), then yes, it's probably the fuel pump.

 

If it is the earlier return style, then it could be the fuel pressure regulator mounted on the fuel rail, or possibly the fuel filter (on the inside of the frame rail under the driver's seat).

CamGTP Senior Enthusiast

CamGTP

Posted
Posted

2003 is still a return style fuel system.

 

The knock sensor code is kinda unrelated to the fuel pressure issue. The rear sensor hole in the valley always get filled with water and moisture which ruins the sensor. New AC delco sensors and a harness usually fix it.

Chris Hester New Member

Chris Hester

Posted
  • Author
Posted

knock sensors have been replaced, new fuel filter and I just replaced the fuel pump...started the engine and fuel rail setting on 52psi...needless to say I'm a little perpexed to whats going on

CamGTP Senior Enthusiast

CamGTP

Posted
Posted (edited)

Any knock sensor code that is pending or current will pull the maximum amount of timing allowed in the calibration. Should be right around 8 degree's of timing. A scan tool would show this timing amount being pulled as well.

 

Even new sensors can be bad or out of spec right out of the box.

 

What does your fuel pressure do under load though. 52 at idle is fine but if you get on the throttle under load orfull throttle and it can't maintain or 52psi that is a problem. It should rise to about 58psi under heavy load.

 

 

A scan tool will also show you if you are having misfires on certain cylinders, would better help see if that is something to look at.

Edited by CamGTP
Chris Hester New Member

Chris Hester

Posted
  • Author
Posted

my 03 silverado is still having issues...rough idle, no power under load, will not take throttle and is loading fuel to no. 1 bank...any suggestions where to start looking?

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

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined

  • Who's Online   4 Members, 0 Anonymous, 1,803 Guests (See full list)

  • Latest Articles

  • Posts

    • 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.
    • davester
      Turning radius

      By davester · Posted

      Just don't turn the steering wheel as much?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...