Jump to content

Service trailer brake

HeliMark
 Share

Recommended Posts

RickertsRed New Member

RickertsRed

Posted
Posted
On 2019-06-12 at 10:11 PM, RickertsRed said:

So I’m reviving this thread because I had a very similar issue just recently and the fix was simple so hopefully it’ll help you guys.

 

My ‘17 Sierra 3500 started with the quite common door ajar issue, I tried slamming it, playing with the accordion wire harness in the door frame, I even took the door panel off and pulled apart all the connectors to see if there were loose or frayed wires or possible corrosion. Pulled out a multimeter and checked everything; all good. None of the above fixed my problem.

 

Then I started getting the “service trailer brake” and “trailer disconnected” randomly. Sometimes with a trailer attached, sometimes without. Seemed odd to me, but I didn’t even bother troubleshooting.

 

Next I started getting “Service Stabilitrak” randomly and sporadically.

 

Ok ok now I’m thinking WTF is going on here. So I disconnected both batteries and pulled every single fuse and reset it (checked to see if it was popped in the process). I didn’t even check to see which fuse I pulled, just pull, inspect, replace.

 

The length of the whole battery and fuse process took me about 2 beer, throwing a ball for the dog periodically, playing referee for two toddlers who love to fight and VIOLLA... the door ajar, trailer brake, and stabiltrak all fixed in one swoop.

 

Hope this helps the next guy.

UPDATE

 

I did my fuse/battery trick and all was well for 2 weeks... until it rained, heavily. Service Stabilitrak and Service Trailer Brake were back, so now I know 100% it’s a broken wire or loose connection that water is getting into.

 

So I broke down and went to the dealer to have the codes read and there were a few codes. One for a Chassis Control Module (CCM), one for Body Control Module (BCM), and the last was right rear ABS wheel speed sensor.

 

Back home I go and crawl under the truck by the right rear wheel and track the wheel speed sensor harness back to where it connects to the truck side via a connector attached to the frame. Ended up finding one of the wires on the truck side about 1” back from the connector with a pin hole in the coating with clear evidence of corrosion in and around the hole.

 

I could have just re-spliced the wire back together but I’m an avionics technician and we’re not allowed to splice a wire that close to a connector, so my OCD spilled over into this repair and I ordered a whole new connector. ABS wheel speed sensor connector (truck side) info: 

part number: S-1895 Pigtail

brand: Standard Motor Products

 

Spliced on the new connector and presto... fixed again! Luck had it that it was raining the day I did the repair so I went for a drive afterwards, no issues at all. All good!

 

hope this helps

  • Like 2
  • Thanks 2
  • Replies 35
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

RickertsRed
RickertsRed

UPDATE   I did my fuse/battery trick and all was well for 2 weeks... until it rained, heavily. Service Stabilitrak and Service Trailer Brake were back, so now I know 100% it’s a broken wire

Dirtbiker
Dirtbiker

I pulled the abs fuse in my truck as I don't want stabilicrap and it can't be shut off anymore. I get a service stabilitrac and service trailer brakes message everytime I start my truck. But my traile

Dirtbiker
Dirtbiker

Not sure what the issue could be. My manual switch still works too. I know they tied stabilitrac to the trailer brakes now too so I am guessing that is why I am getting the trailer brake message. Good

  • 7 months later...
Tyler95 New Member

Tyler95

Posted
Posted

So i have a '16 GMC Sierra and just out of the blue driving along the service stability light goes on and then the service trailer brakes light and ABS light comes on and continually keeps coming on! Any help would be greatly appreciated! TIA

  • 3 years later...
Jminter6001 Enthusiast

Jminter6001

Posted
Posted
On 10/14/2016 at 8:57 PM, HeliMark said:

I have a '16 2500 DMax. Been pulling a 10K pound toyhauler ('16 Forest River Stealth), but the every so often, I get a "service stabilitrac/trailer brakes/abs" warnings. First time was after towing for about 600 miles, was able to get it to reset, than again after towing 3K miles, 800 miles, and so on. No real rhythm. Of course when the "service trailer brakes" comes on, I lose the trailer brakes, which has not been a big problem getting it off the road after that, but lucky I have not had an emergency while they were inop. Everything will reset after pulling the trailer plug, doing a dance, plugging and pulling the plug again and another dance and drive about 50'.

 

So far on the first one, the dealer replaced half of the trailer plug on the truck saying they found water in it. The other times, one dealer (mid trip) said I had a bad ABS module, but could not repair it at the time, and that the truck had codes for all the wheel sensors/abs/tranny and a couple of others. When I got home, the dealer here found one of the front calipers sticking, which had caused a warped disc. They ended up replacing the caliper and disc, regrind the other front disc and all new brake pads. They also found some unusual readings in the trailer plug, and ended up replacing the whole plug this time. They said the ABS was good.

 

After all that, I had to tow my trailer to a dealer for a warranty repair on the refer. After driving about 10 miles, all the warnings went off, losing the trailer brakes again. The refer had a bad thermo disc and thermo wire (both 12v), and when I pulled it home after the repair, no warnings.

 

So, here is my question. Could the bad thermo wire in the trailer cause some wonky voltage to backfeed to the truck, and cause the truck to go nuts? With all the new electronics, I know any abnormality can cause issue's.

 

Now that I have the trailer repaired, I have an appointment set up to see the dealer with the trailer hooked up and see if the computers can find anything.

 

Mark

 

Did you ever pin point the problem? Im having a very similar issue.

davester Senior Enthusiast

davester

Posted
Posted (edited)

....just fyi, that is a 7 year old post (when this thread started), and that user hasn't logged into the site in 4 years.  You aren't going to get a response from that user.

 

And did you read through the thread for how other people fixed their similar problems?

Edited by davester

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

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined

  • Who's Online   6 Members, 0 Anonymous, 1,706 Guests (See full list)

  • Latest Articles

  • Posts

    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • 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 agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
    • Grumpy Bear
      OCI, not when but why?

      By Grumpy Bear · Posted

      I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
    • revmanii
      Looking at ordering a '26 WT because I want a std cab, std bed

      By revmanii · Posted

      Trust me I appreciate the comments and concerns. It's what I was looking for to help me evaluate the situation and what I want to do. I have decided to move forward with the BORA hubcentric slip on 3/8" (.375") with the extended lugs nuts. Fedex says they should be here Monday :). Meanwhile, the dealer got the remote start and Patriot spray in bed liner done over the last couple of days. Also, I installed an inline stop/start eliminator today. Starts back up in what whatever mode you shut it off in, so you don't have to hit the button every time you fire up.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...