Jump to content

Recommended Posts

Posted

Hey everyone so my friend has a 2018 GMC Yukon that only has 30000km on it and since August she has been getting a intermittent very bad exhaust smell in the cab. She has taking it to severely dealerships and they can not find the problem. It only happens once in awhile while driving it. I recently took it for a drive with my personal gas monitor that reads CO and it it started to read a very large amount of CO when I was test driving it and I could smell it very easily. I the took it back to one of the dealers and took a tech for a drive with the monitor and of course it didn’t get any smells on the cab. I tried to change the setting with the heater controls and recirculating air control and it didn’t help. She now has called me again saying it was very bad on the way to work again. The dealerships said they have gone through everything possible? I mentioned maybe a manifold leak but the said it would be noisy if that was the case. I am wondering what could have been missed that I can look at? And what is the best step going forward? 

Posted

It certainly is a head scratcher. Driving me crazy. She said it smells kinda like rotten eggs. I just smelled a exhaust smell when I got it to act up

Posted (edited)

My car had an exhaust leak that I could only smell when stopped.  When driving the air coming through the rad would push the exhaust down the firewall and out so no smell.  Exhaust when stopped would come up the firewall and seep into the intake vent for the heater.  No smell on recirculate but this is a 2007 so recirculate shuts off outside air completely.  Was somewhere by the manifold close to the engine as I could feel hot exhaust if I put my hand down there during a cool day.  Not any nosier though.  This was a 2.4 L 4 cylinder.  Sold the car.  In the old days we would put a potato up the exhaust and if the vehicle stalled then exhaust was sealed.  It is funnier if you just put the potato up there and leave and start the car and rev it up.  Just like a rocket blowing it out.  ?

Jim

 

Edited by jagabom (Esquire)
Posted

Possibly the flex connection after the exhaust banks Y?  Not sure on a Yukon, but typically that would be under the firewall, cab area and would make sense if it's being smelt in the cabin. The rotten egg smell was typical of catylitic

converters of the mid-70's before they were located closer to the exhaust manifolds where they heat up and do their job quicker and more efficiently now.

  • 1 year later...
Posted (edited)

I have the same thing right now. It smells like exhaust/unburned off gas. Worse when stopped at idle with the cold it being really cold. 2014 Chevy Silverado. Did you figure out the problem?

Edited by Arcterrax
  • 2 months later...
Posted
On 1/27/2022 at 6:03 AM, Arcterrax said:

I have the same thing right now. It smells like exhaust/unburned off gas. Worse when stopped at idle with the cold it being really cold. 2014 Chevy Silverado. Did you figure out the problem?

I have the same issue in my 14 Silverado, has anyone found the cause to this? Mine started after a transmission fluid change where i needed to get the exhaust out of the way of the pan using a tie down strap and 2x4 so I'm guessing its in the flex pipe or i destroyed a gasket somewhere. Looked everywhere cold and hot, thought it might even be the oil catch can leaking but it's sealed. 

Posted

Have had the same issue in my 2015 and have yet to find the cause.  Mine started after the first trans replacement (122,000).  Had it tested and found no leaks. Only does it when stopped.  As long as I’m rolling it’s not there. 

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

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...