Jump to content

Recommended Posts

Posted

I have a 2011 Chevy 2500hd with 6.0. The truck has developed a misfire at idle and partially on the gas. I have replaced all the spark plugs, all 8 injectors, moved coil packs around, replaced MAF, MAP, b1s1 02 sensor (was getting codes for that sensor only), ECU, fresh gas and added cleaners, cleaned throttle body and swapped throttle body, had cats removed (already were blown out and empty) Nothing has solved the issue. Only bank 1 is misfiring. Mainly cyl 1 and 3. The truck backfires out the exhaust, and under load back fires out the intake. It will clear up like a switch flipped and run fine until the truck is shut off and restarted. I’m at a complete loss. By watching the snap on scanner. It appears as if it’s richen bank 1 and lean bank 2. I’m at a complete loss. It’s happening at idle and slightly off idle until it decides to clear up. I have been getting codes for random misfire and bank 1 sensor 1 02 sensor for heater issue.

 

 

Sent from my iPhone using Tapatalk

Posted

I was thinking possibly crank sensor or cam sensor but what doesn’t make sense to me is that it is only misfiring on bank 1 and not bank 2. And that it is fattening up bank 1 and lean out bank 2. Atleast the pulse width for the injectors is showing off on each bank. When it runs fine they are equal. If not they are off by a lot. Like 3.5-4.0 and 1.5-2.0


Sent from my iPhone using Tapatalk

Posted

?,that backfiring in intake,leads me towards crank sensor,one test is watch rpms on scanner and spray cool water on crank sensor,see if it changes anything, another is,move wiring a little for crank sensor,anywhere it's accessable,and safely

Posted

I’ll have to try the spray on the sensor as that seems a little easier and safer. It will backfire through the intake under load. No load at idle it back fires out the tail pipe.


Sent from my iPhone using Tapatalk

  • 2 months later...
Posted

I haven’t done the test with the water. I had a spark plug that burned out (it had maybe 1500 miles on it) and I had to order a new set of plug wires for it. I’m gonna replace the plug and put new wires in it. I’m going to replace both up stream 02 sensors as well with new bungs. The threads on bank 1 are messed up and the sensor doesn’t seat fully into the pipe.


Sent from my iPhone using Tapatalk

Posted

I replaced the bad spark plug today, along with all of the wires, the body to motor ground, and cleaned the main engine ground. I did notice that the wiring inside of the loom is rather brittle and corroded. I will be replacing the main ground from the battery to the engine. Here are some of the graphs that the scanner is showing. What I’m noticing is that bank 1 (side that always misfiring) 01 sensor number 1 is not nearly as “sensitive” as bank 2 sensor 1. Also fuel trims between the 2 sides seem to be off as well. a5a49ab3afb2c2af925c506bd6eab045.jpg
b865138b46f043bf9a42caa7144305de.jpg
87b28d13fc12c1ecab76a7b95ab582f1.jpg


Sent from my iPhone using Tapatalk

  • 5 months later...
Posted

Okay. Little update if any one is able to help. I replaced the ground cable that was corroded. I checked for power and ground at all the sensors. When I use the sensor grounds, I get 8.70 volts with key on engine off. If I use the sensor positive and the ground of the motor, I get 12 volts. Where do the o2 sensors ground to? I have replaced the factory ground to the battery as well as firewall to rear head ground. Still no luck


Sent from my iPhone using Tapatalk

  • 6 months later...
Posted
6 hours ago, 94TBI said:

Did you ever resolve this issue?

No I have not. I have replaced grounds and cleaned ground points but cannot find the issue. I’m leading towards a wire in the harness or possibly corrosion within a ground wire somewhere. It’s driving me crazy. Recently I’ve had service trailer brake system and trailer wiring. The trailer brake relay was recently replaced and is new. So with the misfire, and now these other issues popping up I’m going to say a ground wire. The trouble is finding which one. I’ve replaced the battery ground cable, rear head tires body ground (which was previously blue and fell apart) and cleaned frame grounds under driver door. 

Posted

Also to update, I did replace the crank sensor. No change. I’m going to try to replace both downstream o2 sensors. The one on the driver side looks like a universal one that you use butt connectors on. Maybe the downstream one is throwing the upstream off or something? Not sure being hopeful at the moment. I’m running out of options. Trying to get the issue resolved so I can sell the truck to get a full 4 door duramax. 

Posted (edited)

Yeah I know. It’s about the last effort unless I change out the whole wire harness. I have literally replaced every other sensor. Or I am going to take it to the dealer and pay for the diag and see what they come back with. I’m about out of ideas at this point. 

Edited by casey.mikl
Posted

Have you checked for compression and spark? Have you also used a noid light on the wiring harness to see if all the injectors are pulsing fuel? 

 

What codes are you getting? 

 

Maybe these are some dumb questions but just want to double check all the basics. I would also suggest take it to the dealer before throwing more parts at it.

Posted

Yeah compression and spark is fine. I have not checked the injectors. When it’s in closed loop it misfires and runs terrible. When it’s in open loop it runs fine and has no issues. I have replaced maf, map, crank sensor, battery, all ground cables, injectors, plug wires, spark plugs, computer, o2 sensors upstream, cut out cats (starting to come apart). I’m going to take it to the dealer. I ran it today and running using the computer as ground I’m getting 14.6 volts. Also same on body and engine. I had a feeling it may have been a ground to ecu issue but it wasn’t. 

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

    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...