Jump to content

Disable OEM integrated trailer brake controller

GMequalsPOS

By GMequalsPOS
in Troubleshooting & Recalls

 Share

Recommended Posts

GMequalsPOS New Member

GMequalsPOS

Posted
Posted

Good day,

 

Every time I start my 2017 Sierra 1500, I get a msg on the DIC, Service Trailer Brake System.  Was too costly (repair shops want $180 just to diagnose the issue) to get the integrated one fixed and an aftermarket controller was only $120.

Despite the aftermarket controller being installed and working fine, I still receive the msg on the DIC.

 

How can I disable/remove/disconnect/stop that f'n msg on the DIC, about the brake controller.  I'm hoping there's a way to remove the OEM controller and/or tell the truck it doesn't have a trailer brake system...  I've googled to no avail.

 

Thanks.

64BAwagon Senior Enthusiast

64BAwagon

Posted
Posted

You might try disconnecting the wiring at the 7 way plug on the rear of the truck. Sometimes the error is due to corrosion in that plug. It wont cost anything and its relatively simple. I would put something over the connector afterwards to keep debris out of it.  

newdude Senior Enthusiast

newdude

Posted
Posted
9 hours ago, GMequalsPOS said:

Good day,

 

Every time I start my 2017 Sierra 1500, I get a msg on the DIC, Service Trailer Brake System.  Was too costly (repair shops want $180 just to diagnose the issue) to get the integrated one fixed and an aftermarket controller was only $120.

Despite the aftermarket controller being installed and working fine, I still receive the msg on the DIC.

 

How can I disable/remove/disconnect/stop that f'n msg on the DIC, about the brake controller.  I'm hoping there's a way to remove the OEM controller and/or tell the truck it doesn't have a trailer brake system...  I've googled to no avail.

 

Thanks.

 

 

The switch in the dash is probably bad.  Most common part we replace for the integrated trailer brake system.  p/n 84108373 retails for $76.  

 

If you are set on bypassing, here's what you need to do below:

 

PIT5282F: Procedure for Installation of an Aftermarket Trailer Brake Controller or In Lieu of Factory Trailer Brake Controller - (Dec 19, 2019)

 

4.  Perform this step ONLY if equipped with RPO JL1 where the customer is requesting the factory trailer brake system be bypassed to add an aftermarket trailer brake controller.  Locate connector X185 Or X138 (varies with vehicle build; refer to SI), which is near the underhood fuse block, terminal 32. Circuit 47 ends at the body harness side of X185 or X138 terminal 32, which comes from the X61A junction block. Obtain enough Dark Blue 12 gauge wire to run from X185 or X138 to the 7-way trailer connector at the bumper. Attach terminated lead part number 13327155 to one end of the Dark Blue and insert into the chassis harness side of the X185 or X138 connector terminal 32. Run the Dark Blue wire in its own conduit along the frame to the 7-way trailer connector at the bumper. Remove circuit 47 from the 7-way trailer connector terminal “C” and tape the bare terminal and attach to the harness. Attach terminal part number 12110853, located in Delphi Tray 4, to the other end of the Dark Blue wire, with the correct weather pack seal, and insert it into the 7-way trailer connector terminal “C.”

  • Like 1
GMequalsPOS New Member

GMequalsPOS

Posted
  • Author
Posted
12 hours ago, newdude said:

 

 

The switch in the dash is probably bad.  Most common part we replace for the integrated trailer brake system.  p/n 84108373 retails for $76.  

 

If you are set on bypassing, here's what you need to do below:

 

PIT5282F: Procedure for Installation of an Aftermarket Trailer Brake Controller or In Lieu of Factory Trailer Brake Controller - (Dec 19, 2019)

 

4.  Perform this step ONLY if equipped with RPO JL1 where the customer is requesting the factory trailer brake system be bypassed to add an aftermarket trailer brake controller.  Locate connector X185 Or X138 (varies with vehicle build; refer to SI), which is near the underhood fuse block, terminal 32. Circuit 47 ends at the body harness side of X185 or X138 terminal 32, which comes from the X61A junction block. Obtain enough Dark Blue 12 gauge wire to run from X185 or X138 to the 7-way trailer connector at the bumper. Attach terminated lead part number 13327155 to one end of the Dark Blue and insert into the chassis harness side of the X185 or X138 connector terminal 32. Run the Dark Blue wire in its own conduit along the frame to the 7-way trailer connector at the bumper. Remove circuit 47 from the 7-way trailer connector terminal “C” and tape the bare terminal and attach to the harness. Attach terminal part number 12110853, located in Delphi Tray 4, to the other end of the Dark Blue wire, with the correct weather pack seal, and insert it into the 7-way trailer connector terminal “C.”

Thank you for that.  Although I didn't mention it as it wasn't related to my original question, I did try replacing the dash switches.  Didn't resolve the issue, also checked the connectors at the rear of the truck, reseated everything, checked for voltage at the controller by the spare tire, etc.  Anyway, the aftermarket controller is installed and working.

 

After googling that GM bulletin (thanks again) and that step 4, what it appears to me, is using the truck's existing wiring between the cab and under the hood (instead of having to run your own wire through the firewall) from the aftermarket brake controller to the 7-way trailer connector.  As it also indicates that you need to run your own wire from the 7-way connector to that terminal block under the hood.

 

With that GM bulletin number, I found this (https://www.duramaxforum.com/threads/adding-aftermarket-brake-controller-to-2015.1017203/) post where someone basically did the same thing, following that bulletin (plus some extra) and in one of their pictures, I can see in the DIC, that the truck still knows the ITBC is there.

 

So although that bulletin explains the easiest way (not really) to install an aftermarket controller, bypassing the truck's blue brake wire, it doesn't actually disable/remote the ITBC, it just doesn't use it to supply the voltage on the 7-way trailer connector.  Hope that makes sense.

  • 2 weeks later...
0216HD Enthusiast

0216HD

Posted
Posted

2016 2500HD has been telling me to service the trailer brake since new. Dealer attempted many times under warranty but never succeeded. Sometimes it works, sometimes not. Sometimes  after connecting a trailer a shut down and restart will bring it online but not always. Notice comes on with every startup with or without a trailer connected. After I gave up with dealer I personally have replaced the circuit board in dash and the module above the spare tire. Resistance tested all the connections I could find and searched for chafed / broken wires. I've had countless conversations with GM. Best they have ever did was offer me a $100 coupon to get my truck serviced at dealership. I'd be interested to hear from anyone with a working background of the problem that might offer some suggestions as to where to look next.

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

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...