Jump to content

Recommended Posts

Posted (edited)

Long story short the dealership has my 2020 Silverado 1500 4x4 with 60k miles, that I took in for the AC not cooling. It worked perfectly, blowing very cold until it didn’t one day. Like the switch wasn’t activating the clutch on the compressor.  Anyways it is showing 180lbs on the high pressure side and 120lbs on the low side. Obviously very high on the low side. GM is recommending a $958 replacement of the expansion valve first and then if that doesn’t work then $2800 to replace the compressor!!  The mechanic thinks it’s the compressor and I tend to agree begrudgingly. I hate to blow $1000 on a 50/50 chance and then have to replace the compressor anyways. I have a couple of questions below. 

1. Any ideas one way or the other on the diagnosis?  The electrical all tests out and the compressor is running. 

 

2. If the compressor needs to be replaced what are the issues I would run into doing it myself?  Not the recovery or the charge as I have a good friend that can take care of that. I’m mainly talking what has to be removed to get to it and get it out?  The truck has a 6” lift and I was thinking removing the wheel and inner fender to access it from the side. I don’t have the truck to even look at it so I’m not sure what that area of the compartment looks like.  I’ve done plenty of mechanical at this level but I don’t want to damage it. She’s a beautiful truck that mainly just gets used to tow my boat or a 14’ enclosed trailer so she’s mainly a garage queen. 
 

 

IMG_1932.jpeg

Edited by JhnyRed
Cover license plate
  • 2 weeks later...
Posted

if you friend can evacuate the system, i would do the expansion valve yourself. it only takes about 20 minutes to change with the system empty. 958 to change it is just criminal for a 1 hour job

Posted

We’ll long story short. With no information anywhere that I could find on changing the compressor and not being able to even see it on the truck with all the stuff in that part of the engine compartment, I negotiated with the dealer. I didn’t feel it was the valve, but it sure seemed like the compressor was toast. That said with some doubt I didn’t want to ruin a new compressor if there was a chance the valve was the culprit. I offered just pay $3000 to do the compressor and expansion valve at the same time. That would be about $800 less and we won’t know if the valve was the cause. The service manager came back with a counter offer. They would replace the valve first per GM’s recommendation. If that repaired it then I would just pay the $958. If not they would do the compressor for a total of $3200. It put some risk on them and a possibility of only paying for the valve for me. I really didn’t have any other options in my area so I said do it. Sure enough the valve replacement didn’t do anything so they replaced the compressor. Not a happy ending financially but it’s a bad design of where the compressor is in the truck. With the $188 hr labor rate it’s brutal for just a compressor. The service writer was a good guy and I at least got them down $600 and there was the possibility it could have been under a grand. Oh well. I figured I would at least share my experience for the next guy. It’s all fixed and it’s cool in my cab again!

  • Like 1
Posted

Don’t feel all too bad. If the compressor had internal damage and was pushing bits through the system, changing the expansion valve along with the compressor makes very good sense. Of course, I am assuming they also did the accumulator while they had the system open, and hopefully they also flushed the rest of the system to get any trash out.

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