Jump to content

Recommended Posts

Posted

I just towed my travel trailer with my new 2020 Silverado, with the factory brake controller. I had a 2020 Colorado ZR2 Bison prior, which was totaled in a crash last month. Prior to that, I had a 2017 ZR2 with the Diesel engine (which was replaced twice). In both Colorados with the factory controller, I would end up with a gain of about 4.0-4.5 and get excellent control of the trailer braking. Towing with the Silverado, I ended up with a gain of 7.5 with the same trailer. In addition, I feel like even with a higher gain setting, the braking performance wasn’t at all what I expected from the bigger truck. 
 

The trailer is a 2018 Keystone passport 175BH, max weight of 4500lbs, probably about 3500 when I’m moving from my house to the storage lot and vise versa. 
 

Am I wrong in thinking that the gain setting would have been about the same with the same trailer, considering they are all GM parts? 

Posted

I’ve never had to go higher than 4.5 and my trailer is usually heavier than that. Anything more and they want to lock up. 

Posted

Have you verified the trailer brakes are still good and operable? In my last vehicle the numbering was different but from min to max but the relative gain was about the same.

Posted
4 minutes ago, jnissen said:

Have you verified the trailer brakes are still good and operable? In my last vehicle the numbering was different but from min to max but the relative gain was about the same.

Brakes are good. I hooked it up to my neighbors Sierra this evening and with the gain set on his at 5.0, the braking was quite a bit better. I'm gonna make an appointment for the dealer to check it out.

Posted
I just towed my travel trailer with my new 2020 Silverado, with the factory brake controller. I had a 2020 Colorado ZR2 Bison prior, which was totaled in a crash last month. Prior to that, I had a 2017 ZR2 with the Diesel engine (which was replaced twice). In both Colorados with the factory controller, I would end up with a gain of about 4.0-4.5 and get excellent control of the trailer braking. Towing with the Silverado, I ended up with a gain of 7.5 with the same trailer. In addition, I feel like even with a higher gain setting, the braking performance wasn’t at all what I expected from the bigger truck. 
 
The trailer is a 2018 Keystone passport 175BH, max weight of 4500lbs, probably about 3500 when I’m moving from my house to the storage lot and vise versa. 
 
Am I wrong in thinking that the gain setting would have been about the same with the same trailer, considering they are all GM parts? 
I have a keystone passport 239 which is probably 5500 lbs fully loaded 2 axles. I seem to settle in at about 6 to 6.5 on the trailer brake depending on truck load to make it feel "right".

Sent from my Pixel 4 using Tapatalk

  • 4 weeks later...
Posted

Just to follow up on this. I had it in the dealer and they did some testing. Tech up cleaning the connector on the truck side and everything works just fine now. Didn't even cross my mind the connector might need cleaning on a brand new truck. 

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

    • 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.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...