Jump to content

Change those cabin air filters, y'all


Recommended Posts

Posted

Yep, one of the most forgotten items.  I'm guilty as well with it being close to 18 months before I checked mine.  It wasn't as bad as this but close.  I just cleaned the K&N cabin filter in my Cruze and it wasn't to bad for being in over 13 months. 

Posted

I have a K&N cabin filter.. Thanks for reminding me i gotta clean it haha  ive cleaned it i think twice now since owning it since about 25k miles.  At 69k now.

 

Posted

It’s 4 T15 screws that holds on the bottom glove box.

 

After removing give it a tug like it owes you money to release the holding tabs.

 

Then look directly forward inside the dash, you’ll see the door.

 

Release the two top tabs and you’re there!

 

Pro tip- if it sounds like a helicopter after you’re done, you’ve dropped a leaf into the blower! Always remove the cabin filter at a snails pace then check to be sure you haven’t dropped one in there!

 

Hope this helps

 

-GM tech

 

Posted

I have to change mine fairly regularly. Lots of oak leaves here. They slither and squirm their way into the fan and make a fish tank aerator noise when one gets into the fan.

Easiest fix without removing all of creation is to put a blower nozzle on your air compressor hose and blast inside the chute where your filter slides in, with the filter removed. Keep blasting air until the noise is gone.

Sent from my SM-J810F using Tapatalk

Posted
16 hours ago, ammoaddict said:

Is it easily accessible or do you have to remove something first?

Sent from my Moto G (4) using Tapatalk
 

No, it is kind of a PITA.

 

Check your owners manual, it walks you through the steps.

 

If you have normal sized (or large) hands, it can be difficult to get the plastic door (panel) that holds the filter in the dash off.

Posted
14 minutes ago, JimCost2014 said:

No, it is kind of a PITA.

 

not kinda..

 

silly that GM couldn't give it clip-release access..

Posted
58 minutes ago, rbrjr1 said:

not kinda..

 

silly that GM couldn't give it clip-release access..

Completely agree, and our Tahoe is even more involved because you do not pull the whole glove box unit away from the dash like in the trucks.

There is a damper "cord" on the side that you have to disconnect, and a total of 6 or 8 (can't remember at the moment) T15 screws that have to be removed, then the same next to impossible "snap cover" that only a small child's hands can comfortably reach to remove and replace the filter.

Posted
2 hours ago, rbrjr1 said:

not kinda..

 

silly that GM couldn't give it clip-release access..

That might have cost them 2 more cents.

Posted
Completely agree, and our Tahoe is even more involved because you do not pull the whole glove box unit away from the dash like in the trucks.
There is a damper "cord" on the side that you have to disconnect, and a total of 6 or 8 (can't remember at the moment) T15 screws that have to be removed, then the same next to impossible "snap cover" that only a small child's hands can comfortably reach to remove and replace the filter.

I have baby hands!

Makes them pretty easy to do [emoji23]

-GM tech


Sent from my iPhone using Tapatalk
Posted
7 minutes ago, tlaw91 said:


I have baby hands!

Makes them pretty easy to do emoji23.png

-GM tech


Sent from my iPhone using Tapatalk

That would definitely help:

See the source image

Archived

This topic is now archived and is closed to further replies.

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