Jump to content

Recommended Posts

Posted

I have a 2004 Z71 Tahoe 4x4 with rear AC and 225K miles.  It has all original AC equipment so this is its first failure. No codes, no cold air. HP Tuners shows “AC Pressure (Disable)” and I am able to override that and get the compressor turning and cold air as shown in the video so the compressor clutch circuit is fine.  You can watch the voltage pressure rise when the compressor engages in the video. I replaced two pressure sensors, one on the Receiver Drier (two wires) and one on the discharge line (three lines) and still no spinning compressor.  The All Data shows a third pressure switch on the back of the compressor but there isn’t one on my truck and no wiring harness for one so I don’t think All Data is correct.  Since HP Tuners is showing “AC Requested”, I figure my HVAC control box inside the truck is working.  Any ideas?  Is there a safety pressure switch internal to the compressor and wired to the AC compressor harness?  Which pins on the ECU should I test out for broken pressure sensor harness wires?  Thanks!

 

 

Posted

My guess is that the freon charge is low. What are the pressures with the a/c on max, windows open, compressor running?

Posted

I’ll check it on Monday.  I didn’t hook up my gauge mainly because the >1.0 volt on the pressure side and being short of time prior to going on a road trip.  I figured that pressure voltage would unlock the computer to engage the clutch, but I’m not sure how the ECU is programmed.

  • 2 weeks later...
Posted

My Hi/Low refrigerant pressures are good.  Switched from using HP Tuners scanner to my old Autel and have a B0229 diagnostic code on the HVAC controller.  Pulled out the fresh air, recirculation flap actuator and it is locked up.  Getting this thing out was not fun.  Anyway, I guess the HVAC controller disallows the compressor clutch when it looses control of the fresh air flapper.  Why HP Tuners shows “AC Disable (Pressure)” is another mystery.  I wouldn’t have coded the HVAC controller that way but it is what it is.  Parts come in tomorrow.  Probably time to repaint the dashboard anyway…

Posted

it kind of makes sense with HP tuners calling it that way. You have 2 ways to tell the compressor not to be on, being wide open on the throttle (WOT) or having a fault that tells it to stay off even when you want to tell it to turn on.

 

Seems weird to disable the compressor with the actuator failing but I can say that some cars will cycle the clutch when you are in recirculate mode but will let the compressor run full time when you're pulling in outside air too.

Posted (edited)

So apparently I screwed up the AC configuration when I added electric fans to my truck.  Playing around with Hardware settings in this screen and these settings allow the compressor to turn on and the FAN #2 to turn on in my 2004 flex fuel Tahoe.  Why these are right (or are they??) I have no idea…. Hack hack hack.  The recirculation actuator was a separate issue.  Had to replace my dash controller and the actuator to get that fixed but it still didn’t get the clutch to turn on…

 

Image.jpeg

Edited by stagrlee

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

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