Jump to content

Recommended Posts

Posted

So, we were on a trip and truck was running great no issues and had put 1600 miles into the trip.

Driving along and truck went into limp mode with a P2101, P0152, and a P0300 code.

I had a Jet performance TB on it for about 40k and had sprayed cleaner into it and wiped it all out but did not remove it before trip, I also had cleaned the air filter and MAF sensor as well as changed the oil.

P2101 or P02101 was referencing a dirty TB or TB Actuator, so I took it off and cleaned it til it shined like a mirror inside and out.

Reset code and drove GREAT for about a day and a half then thru the code again, so I triple checked everything and was stressing out about driving home with trailer attached and it going into limp mode when on the freeway.

So I ordered a low priced Amazon alternative  TB as where I was  there were none locally in stock nor at the GM dealer.

It worked perfectly til we got home and now  these 2 codes in the title came up and I reset em and they came back.

Where do you guys think I should start? 

I can do most anything mechanically but don't want to start buying parts.

I looked up the codes of course and the likley culprits but I know there are some GM techs on here that may have a better gauge on things than a Google search or GMcodes.com  ..lol 

TIA Gents

Posted
15 hours ago, johnnyquick said:

So, we were on a trip and truck was running great no issues and had put 1600 miles into the trip.

Driving along and truck went into limp mode with a P2101, P0152, and a P0300 code.

I had a Jet performance TB on it for about 40k and had sprayed cleaner into it and wiped it all out but did not remove it before trip, I also had cleaned the air filter and MAF sensor as well as changed the oil.

P2101 or P02101 was referencing a dirty TB or TB Actuator, so I took it off and cleaned it til it shined like a mirror inside and out.

Reset code and drove GREAT for about a day and a half then thru the code again, so I triple checked everything and was stressing out about driving home with trailer attached and it going into limp mode when on the freeway.

So I ordered a low priced Amazon alternative  TB as where I was  there were none locally in stock nor at the GM dealer.

It worked perfectly til we got home and now  these 2 codes in the title came up and I reset em and they came back.

Where do you guys think I should start? 

I can do most anything mechanically but don't want to start buying parts.

I looked up the codes of course and the likley culprits but I know there are some GM techs on here that may have a better gauge on things than a Google search or GMcodes.com  ..lol 

TIA Gents

Year, make, model, engine, drivetrain, mileage, etc?

 

It's an interesting combination of codes though. 

P2101 throttle actuator control motor circuit, range/performance

P0152 O2 sensor circuit high voltage, bank 2 sensor 1

P0300 detected random or multiple cylinder misfires

P2099 post catalyst fuel trim system on bank 2 is reading as too rich

P0174 lean condition on Bank 2

 

Based on the total collection of codes, I would inspect the Bank 2 (passenger side), sensor 1 (pre-cat) O2 sensor, and wiring. It seems the sensor is messing up and producing abnormal readings (P0152, P2099, P0174), leading to possible miss fires (P0300).

 

  • Like 1
Posted
6 hours ago, asilverblazer said:

Year, make, model, engine, drivetrain, mileage, etc?

 

It's an interesting combination of codes though. 

P2101 throttle actuator control motor circuit, range/performance

P0152 O2 sensor circuit high voltage, bank 2 sensor 1

P0300 detected random or multiple cylinder misfires

P2099 post catalyst fuel trim system on bank 2 is reading as too rich

P0174 lean condition on Bank 2

 

Based on the total collection of codes, I would inspect the Bank 2 (passenger side), sensor 1 (pre-cat) O2 sensor, and wiring. It seems the sensor is messing up and producing abnormal readings (P0152, P2099, P0174), leading to possible miss fires (P0300).

 

Sorry my bad.. 2020 Silverado 1500 6.2 70000k miles babied mostly all its life

Posted

the pre cat sensor is reading to much oxygen and the ecm is adding fuel to compensate which makes the post cat read rich. you either have an intake leak on bank 2 or possible  weak injector which could cause the random missfires.could also be a valve problem, hook up a vacuum gauge and if it is steady around 18 to 20 then that would rule out the valves

  • Like 1
Posted
4 hours ago, silveradosid said:

the pre cat sensor is reading to much oxygen and the ecm is adding fuel to compensate which makes the post cat read rich. you either have an intake leak on bank 2 or possible  weak injector which could cause the random missfires.could also be a valve problem, hook up a vacuum gauge and if it is steady around 18 to 20 then that would rule out the valves

THE ECM should be CUTTING fuel to resolve the P0152 and P2099, those are RICH conditions. Although the P0152 isn't exactly a 'rich' condition, it's an unexpectedly high voltage. That makes me think the P0152 (and P2099) isn't necessarily an actual rich condition, rather a faulty pre-cat sensor reading too high. The previous, code of P0152 means the ECM saw a voltage coming from the pre-cat O2 sensor that wasn't just high as in rich, it was so high that it was "circuit high voltage" - or outside the expected range. The ECM is now seeing a low(er) voltage from that same sensor (P0174), a lean condition in combination with the post-cat sensor reading rich (P2099). Those two codes can't really exist together, the bank is either rich or lean - not both. So which Bank 2 sensor do you believe?

 

The key here I think is the P0152, the pre-cat sensor is doing things it shouldn't, so I don't trust the P0174. Given that the two O2 sensors are disagreeing with each other, I am inclined to say the problem lies with one of them.

 

 

  • Like 1

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
  • 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   5 Members, 0 Anonymous, 1,769 Guests (See full list)

  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...