Jump to content

2011 2500hd 6.0 misfire

casey.mikl
 Share

Recommended Posts

shakenfake Senior Enthusiast

shakenfake

Posted
Posted

Well if you are getting a code for no cats it is going to screw with your fueling. Maybe not a misfire but it will mess with the fuel 

  • Replies 79
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

carkhz316
carkhz316

Lol. Denso is good, but other brands are ok too. You contradict your sentiments by purchasing from Amazon, which is notorious for suppling counterfeit parts (including spark plugs and o2 sensors; amon

Posted Images

casey.mikl Enthusiast

casey.mikl

Posted
  • Author
Posted
47 minutes ago, shakenfake said:

Well if you are getting a code for no cats it is going to screw with your fueling. Maybe not a misfire but it will mess with the fuel 

I’m not getting a code for the cats. I’m getting multiple misfire codes. When it misfires, it goes lean on bank one. 

shakenfake Senior Enthusiast

shakenfake

Posted
Posted

Hmmm I am thinking it has got to be a fueling issue on bank one. did you swap injectors? Move all of bank one to bank two? I don't see that you had

casey.mikl Enthusiast

casey.mikl

Posted
  • Author
Posted
32 minutes ago, shakenfake said:

Hmmm I am thinking it has got to be a fueling issue on bank one. did you swap injectors? Move all of bank one to bank two? I don't see that you had

I have replaced all 8 injectors. I have moved plugs between the 2 banks as well as coils and no change. 

casey.mikl Enthusiast

casey.mikl

Posted
  • Author
Posted
On 10/4/2021 at 5:29 PM, shakenfake said:

I'd say check with the noid light next. 

I got a wiring diagram for the engine harness. I traced the wires to the o2 sensors and they are all fine. I get good solid ground and power to all of them. Bank 1 sensor 1 is holding stead at 1275. I believe that is my issue that’s throwing it all off between the 2 banks. The sensor is good. I took it for a drive and the sensor started reading about the same as all the others and it was fine and then shot back to 1275 and stayed flat. I’m wondering if I have a leaking exhaust manifold and it’s sucking air, thus making the sensor readings wrong. 

shakenfake Senior Enthusiast

shakenfake

Posted
Posted

A leaking exhaust manifold doesn't suck air. Check your injector harness with a noid light.

 

It stays flat when it is in open loop I believe. Can't remember

casey.mikl Enthusiast

casey.mikl

Posted
  • Author
Posted

Found some leaks. Both sides of the exhaust are leaking where the y pipe bolts to the manifolds. Had the trans rebuilt so the y pipe was removed. Also found the rear most manifold bolt on the passenger side totally backed out. 

C0873B66-9E93-4DD9-AB8E-B01C71364E56.jpeg

shakenfake Senior Enthusiast

shakenfake

Posted
Posted

Well that could cause it. But it would lose air, still cause it to be out of spec though! The fuel for that side would just be up

 

Glad you possibly found the result

casey.mikl Enthusiast

casey.mikl

Posted
  • Author
Posted

It does have some exhaust leaks. Mainly on the passenger side. I removed the computer and used fiber optic wire cleaner and a brush and cleaned all the connections. Now it’s running good. But sensor one is flat lined at 1275. 

image.jpg

image.jpg

casey.mikl Enthusiast

casey.mikl

Posted
  • Author
Posted

It does have some exhaust leaks. Mainly on the passenger side. I removed the computer and used fiber optic wire cleaner and a brush and cleaned all the connections. Now it’s running good. But sensor one is flat lined at 1275. 

davester Senior Enthusiast

davester

Posted
Posted
4 hours ago, shakenfake said:

A leaking exhaust manifold doesn't suck air. Check your injector harness with a noid light.

 

It stays flat when it is in open loop I believe. Can't remember

It can.  I know on my truck, which had 6 broken off bolts when I bought it, the O2 sensors indicated mixture was very lean until I fixed them.

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

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