Jump to content

Cylinder 8 misfire.

Cassy
 Share

Recommended Posts

Cassy Enthusiast

Cassy

Posted
Posted

I've a 99 Sierra 5.3 I got a diagnostic tool and I've got two codes that came up. The one is a cylinder 8 misfire. I replaced spark plugs wires and spark plugs, fuel pressure regulator. I think I did the coil check and the spark plugs check to see if I'm getting a spark. Anyone have any other ideas for me? I'm not familiar with vehicles and what I know is from you tube.

riverbanks Senior Enthusiast

riverbanks

Posted
Posted

Hmm,so intake manifold leak check,then swap injectors,a guy on here a ways back had a #7 problem,he decided to pull the rails,clean them along with injector intake, problem solved,?

Cassy Enthusiast

Cassy

Posted
  • Author
Posted

Was trying to avoid having to take off the rails and injectors. It takes me way longer than most to get stuff done. Took me 9 hours to do the water pump. I'll see if I can find any step by step you tube videos that show me how to take the rail and injectors apart. Would injector cleaner fix the problem?

riverbanks Senior Enthusiast

riverbanks

Posted
Posted

I use techron alot,so if the spray pattern is bad on that injector, should help,if it's on the feed side,it's got no where to go, I'd try it,and you mentioned water pump,it didn't get hot,did it?

Cassy Enthusiast

Cassy

Posted
  • Author
Posted

I'm not sure if the water pump got hot. Heres my story, truck has always had the check engine light on since we bought it. It was a truck that was meant for hauling a few things to the dump. It was driven for several months when it sprung a fuel leak( oring on the cross over bar) it was still driven. Than the serpentine belt and water pump went which left it undrivable. Everyone kept saying they would come fix it and never did after a year and a few months I started watching you tube videos and decided I could do it my self. So I replaced the water pump and serpentine belt. Than I decided to get the diagnostic tool which lead me to replacing spark plugs, spark plug wires, fuel pressure regulator, the o-rings on the cross over bar. I cleared the codes and now cylinder 8 misfires, I checked to make sure spark plug had a spark, I switched the coil pack with another one. I'd rather continue to fix it myself as parks are expensive enough. I'm a girl with little knowledge on vehicles with a huge support team but I'm stuck and don't know where to go from here. The two codes I'm getting is the cylinder 8 misfire and EVAP solenoid. 

riverbanks Senior Enthusiast

riverbanks

Posted
Posted

Ok,so try the techron cleaner,try a socket on intake manifold bolts, maybe a loose one on #8, another would be to spray a mist of water at #8 injector and manifold,listen for a stumble in the motor,might be a air leak, other than that, injector,big thing with that job is cleaniness,shop vac or compressed air to clean intake,so no debris enters injector holes,not a hard job with new orings

chem_man Enthusiast

chem_man

Posted
Posted

Cassy, since you are serious about performing maintenance on your 99 Sierra, purchase a Haynes manual.  They are invaluable and well worth the money!!

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,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined

  • Who's Online   6 Members, 1 Anonymous, 1,658 Guests (See full list)

  • Latest Articles

  • Posts

    • 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.
    • 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 agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...