Jump to content

Recommended Posts

Posted

Yeah, my dealer pretty much ******. They could do nothing after they hook their tester up and shows fine. I ordered a brake control module from a 21 part number that’s what I had on my last one was and I never had any issues.

Posted
3 minutes ago, Jacejr66 said:

Yeah, my dealer pretty much ******. They could do nothing after they hook their tester up and shows fine. I ordered a brake control module from a 21 part number that’s what I had on my last one was and I never had any issues.

Did the '21 module work on your 2025? I have a module for the '19-23 models that is NIB.

Posted

There's a recall for the 2024s where they replace the TBCM with an updated unit.  The fix was originally to put in a 2023 module.  But last time I had my truck in, they said there was ANOTHER recall on the 2024 TBCM and swapped my module again.  I've towed my RV 6000 miles since then with no brake issues, though I did also install a diode in the line to kill the problem.

 

In the 2024s, the issue was that the TBCM just decided to disconnect the trailer brakes any time the voltage on the trailer exceeded that of the truck.  If you have LiFePO4 batteries and a charge controller for them, you're likely occasionally pushing voltage back to the truck rather than the other direction from the alternator.

 

A diode from the trailer to the truck fixed the issue for the 2024s.  Surprised to see this happening on a 2025.

  • Like 1
Posted
2 hours ago, UWSkier said:

There's a recall for the 2024s where they replace the TBCM with an updated unit.  The fix was originally to put in a 2023 module.  But last time I had my truck in, they said there was ANOTHER recall on the 2024 TBCM and swapped my module again.  I've towed my RV 6000 miles since then with no brake issues, though I did also install a diode in the line to kill the problem.

 

In the 2024s, the issue was that the TBCM just decided to disconnect the trailer brakes any time the voltage on the trailer exceeded that of the truck.  If you have LiFePO4 batteries and a charge controller for them, you're likely occasionally pushing voltage back to the truck rather than the other direction from the alternator.

 

A diode from the trailer to the truck fixed the issue for the 2024s.  Surprised to see this happening on a 2025.

I have a LiFePO4 battery on my crawler hauler. I talked to HydraStar and bought their recommended modules. We shall see how it works next week.

 

I also have a '23 TBCM that is new in the box to go in as well. Hopefully the HydraStar modules work and I can send. It back.

  • 2 weeks later...
Posted
On 9/10/2025 at 5:35 PM, GMCustomerService said:

We know this must be an upsetting problem, Maurice. Our team would like to act as an extra layer of assistance on your behalf during and after your appointment on the 15th. So that we can connect with you, please email us at [email protected] with "GM TRUCKS - mjonesjr84" in the subject line. By sending us a message, you consent to the information you provide being monitored and recorded by GM or those acting on GM’s behalf, subject to the GM Privacy Statement: https://www.gm.com/privacy-statement.

I emailed you a message this morning regarding my truck disconnecting the trailer brakes. This is a major safety issue that I need help getting fixed.

Posted
On 9/25/2025 at 10:51 AM, mjonesjr84 said:

Did the '21 module work on your 2025? I have a module for the '19-23 models that is NIB.

I have not got it installed yet but I will post as soon as I get it done and let you know if it corrects the problem 

  • Thanks 1

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