Jump to content

Recommended Posts

Posted

Just had my cabin air filter replaced yesterday. Now when the fan is turned up high I have a loud and distinct whirring noise that's super annoying. Before you just heard air rushing but no fan noise. I'll be taking it back after work but just wondering if anyone had any ideas why I would be hearing this now. Tech put the filter in wrong or forgot to close something up?

Posted

I've experience the same thing from the middle passenger side vent, no worries it'll quit. Or try cutting off the air flow to the vent making the noise to stop it.

 

 

Sent from my kayak

Posted

The wifes car has a cabin filter. To expensive for a new one IMO unless allergies are a factor. I bought some filter media and cut my own, way cheaper and better air flow. I think the cabin filters are to restrictive, more like an air cleaner filter for a motor.

Posted

A leaf or some debris fell into the fan when he removed the filter. Happens all the time with the filter / fan design.

Easy enough to access the fan I can get to it myself or bring it back and the tech can get to it without tearing everything apart?

Posted

there was probably some kind of debris on top of the filter which sits over the fan if your not careful when you pull the filter out it drops right in the fan

Posted (edited)

It doesn't sound like a fan blade hitting something though.

 

Dammit tried uploading video but can't figure out how

Edited by novembervictor
  • 5 months later...
Posted

I know this is an older post. Sorry. Anyone have an easy way to clean the crap out of the fan? I changed my cabin filter, and I now have the same issue.

Posted

Did you try a shop vac with a crevice tool attachment?

 

 

I know this is an older post. Sorry. Anyone have an easy way to clean the crap out of the fan? I changed my cabin filter, and I now have the same issue.

Posted

Tried it. No joy. Too tight to get my shop vac in there. Even used the wife's Dyson, and still no go.

Posted

My Shop-Vac crevice tool barely fits into the slot, but it didn't have enough suction to get out whatever fell into the fan. I can JUST feel the fan w/ my fingertips, but I can't feel anything in it.

 

I'll have to investigate further. Thanks!

Posted

The wifes car has a cabin filter. To expensive for a new one IMO unless allergies are a factor. I bought some filter media and cut my own, way cheaper and better air flow. I think the cabin filters are to restrictive, more like an air cleaner filter for a motor.

What did you use to do this. Curious as I agree the airspeed I think could be better. Especially for my ac.

 

Sent from my Nexus 6P using Tapatalk

Posted

All you have to do is take out like 4 screws holding the fan in place in the passenger footwell. I had to do this last time I replaced it. One leaf was causing the noise. I only replaced 3 of the screws because one was at a weird angle and stripped the head of it.

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