Jump to content

2024 silverado 1500 8 speed.

15 Z71
 Share

Recommended Posts

15 Z71 Senior Enthusiast

15 Z71

Posted
Posted

Well at 31,000 miles valve body went bad. Dropped it off at dealer last Friday.  They called me today and said they have one coming.  Also told me gm has a new updated one. Has any one had this new updated one installed? Now I'm nervous I'm going to have problems.  If so has anyone had issues after new one installed? Thanks.

15 Z71 Senior Enthusiast

15 Z71

Posted
  • Author
Posted
23 minutes ago, redwngr said:

Can't answer your question about the 8 speed, but how are you liking the 2.7T ?

Yes, I really thought comming from my last 2 trucks having 5.3's I wouldn't  like it,  but very happy with it. Takes a while to get used to how it sounds.  Just worried about transmission.  Dealership said the valve body they are putting in is supposed to be GM updated one. Just hope that fixes it .and it holds up for along time.

15 Z71 Senior Enthusiast

15 Z71

Posted
  • Author
Posted
5 hours ago, silveradosid said:

what was your tranny doing to warant the valve body to be replaced

Pulled out of a parking lot and it went to shift from 1st to second and just reved like it was in neutral. Then slammed in to 2nd gear. Then check engine light stayed on and it said to reduce power and speed.  

15 Z71 Senior Enthusiast

15 Z71

Posted
  • Author
Posted

Well I got truck back on Friday seems to be all good. Transmission shifts super smooth. I hope the new updated valve body fixes it. I keep my trucks for 8 or 9 years. 

15 Z71 Senior Enthusiast

15 Z71

Posted
  • Author
Posted

I looked up that GM part number does not say anything about an update. So maybe they just told me they put in a updated one and didn't???

  • 4 weeks later...
newdude Senior Enthusiast

newdude

Posted
Posted (edited)
29 minutes ago, 15 Z71 said:

Does anyone actually know the new updated 8 speed valve body GM part number?

 

 

All they did was install a new one in your truck.  There is only one # for 2024 8L80 RPO MFC and its the one on your receipt.  24056035.  No old #s before it, no replacing numbers.  

 

The 10 speeds are the ones that have actual changes implemented to them with the new feed limit low valve design.  

Edited by newdude
15 Z71 Senior Enthusiast

15 Z71

Posted
  • Author
Posted
5 hours ago, newdude said:

 

 

All they did was install a new one in your truck.  There is only one # for 2024 8L80 RPO MFC and its the one on your receipt.  24056035.  No old #s before it, no replacing numbers.  

 

The 10 speeds are the ones that have actual changes implemented to them with the new feed limit low valve design.  

So do you think this will do the same thing in another 30,000 miles?  I guess I'm just nervous it will happen again out of warranty.

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

    • 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
    • davester
      Replacement Radiator

      By davester · Posted

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