Jump to content

Recommended Posts

Posted

I have a 5.7L TBI engine in my 94 GMC C1500. The truck is running really terrible. It’s sucking in ALOT of air through the intake without pressing the pedal also it has a really rough idle and when accelerating it sputters and kind of hesitates. It started with the O2 sensor code. I replaced it. Code went away then code 32 popped up. I replaced the EGR VALVE and the Solenoid. Still was having issues. I just replaced the TPS sensor, spark plugs, MAP sensor and still having the same issue. 
 

Could it be the IAC Valve messing up or something else? 

Posted
5 minutes ago, riverbanks said:

Have you checked all vacuum lines for leaks?and how does the spray pattern look on injectors?

I’ve visually checked the the vacuum lines I don’t see any tears or disconnection of any lines. And not sure on the spray pattern. I did run a fuel injection cleaner and that seemed to help it a little bit but not much of a difference.

Posted

You could spray some carb cleaner on all vacuum connections all the way to the booster,listen for idle change,and what about p.c.v?stuck open?as far as the cleaner?how dirty was it under the egr? thinking, carbon on backside of intake valves,think another round of cleaner?

Posted
12 minutes ago, riverbanks said:

You could spray some carb cleaner on all vacuum connections all the way to the booster,listen for idle change,and what about p.c.v?stuck open?as far as the cleaner?how dirty was it under the egr? thinking, carbon on backside of intake valves,think another round of cleaner?

The egr was replaced last year when the last one was stuck open. When I replaced it again recently the ports was mildly dirty not to bad. Should I remove it and spray some cleaner in the ports? And definitely haven’t checked with the PCV. I went ahead and ordered a new one (saying it’s only $4 so why not) 

Posted

I wouldn't clean under egr with manifold on, maybe cause a issue,you can't correct without disassemble,so new pcv,can't hurt, possible vacuum leak,spray test on vacuum lines,and with a flashlight,watch injectors for a nice cone spray pattern

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

    • 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
    • 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. 😄
    • 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
    • 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.
    • 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...