Jump to content

issue with AC threw the vents

lykaboss
 Share

Recommended Posts

lykaboss Enthusiast

lykaboss

Posted
Posted

I got a 1997 z71, it blows cold air but will not blow threw the front vents, it comes out the top of the dash and the bottom of the dash...

Any idea on what could be causing this?

1997SierraSLT Enthusiast

1997SierraSLT

Posted
Posted (edited)

there is a a/c blend door actuator motor linkage up under the dash right right below the left side of the stereo. It tends to get gummed up and stuck. Or it could be a failure of the motor itself. Example youtube video below.

 

 

Edited by 97SierraSLT
  • Like 1
lykaboss Enthusiast

lykaboss

Posted
  • Author
Posted

Ok i just changed that blend door motor and the problem is still there. not blowing threw front vents, one thing i just noticed is on the climate control dial it will only "click" in the center, any other position there is not "click"

 

Any one have any suggestions/ideas?

 

Thanks

2018GMC Senior Enthusiast

2018GMC

Posted
Posted

I had the same problem with Heat or Cold not coming through the front vents. Turned out it was the door connected to the motor you just replaced. The door had partially fallen out of place. I was able to remove the bottom heater plastic air flow directional piece (this is the piece that sits in the middle seating position right above the center "hump") and reach up just enough to put the door back in place. It was a mild PITA to get my arm up in there and stick the door back in place. A few rubber chunks fell out from the door degrading over the last 17+ years....

 

Especially with the fan on med - high and high I could hear an obstruction blocking some airflow and I would only get heat or cold air through the defrost or lower vent and defrost. Nothing through vents at driver and passenger position.

 

Anyway now everything works as it should but it is SLOW to change positions, especially to driver and passenger vent position. It changes to defrost or heat quick, but to change back to the drive and passenger vent (far left on knob), it can seriously take 10 minutes.

 

I thought about replacing motor but it seems like mine moves fine, but the actual air changing position takes FOREVER.

  • 6 years later...
JimO New Member

JimO

Posted
Posted

My ac compressor works, my blower motor works and i can hear like a moaning noise when i turn the low/mid/high knob but NO air comes out of any vents. what could be the problem?

  • 1 year later...
Jerry Travis New Member

Jerry Travis

Posted
Posted

I get air to blow out of the very top vents and the bottom vents, but I can’t get any air to blow out of the front vents.  Any help will be greatly appreciated.   

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