Service traction control & stop/start unavailable

[D60]

Twice now after somewhat extended low range climbs in Colo I simultaneously get both warnings that stop/start is unavailable and to service traction control.

Actually both times have been shortly after starting the descent. Time #1 was bone stock, time #2 was lifted on 38s

It doesn't affect driveability and both times I was in low range - when both TC and ESS should be automatically disabled. I really feel like 4lo being engaged is just fighting with the nannies that try to come back, and the vehicle basically has split personalities LOL

If I shut down and restart it clears

Anyone else get these two errors together, simultaneously?

And JeepCares thank you you if you're tempted to reply but I won't be able to recreate for my dealer, unless a tech wants to spend a full day on the trail with me

Sponsored

 

[Headbarcode]

In related posts its been speculated that the nanny systems aren't completely shut off in 4lo, but just desensitized to a certain point that they don't interfere. I'm no techy and this is just more speculation, but it could lead to a possible margin of error in the systems programming by shifting these thresholds, rather than completely shutting them down. Again, just thoughts.

The one thing that makes me lean towards thinking it may be true is the addition of a specific "Trac Kill" feature when using the Tazer. Why offer that as an additional perk of using that unit, when the factory added a button that supposedly does that?

 

[D60]

In related posts its been speculated that the nanny systems aren't completely shut off in 4lo, but just desensitized to a certain point that they don't interfere. I'm no techy and this is just more speculation, but it could lead to a possible margin of error in the systems programming by shifting these thresholds, rather than completely shutting them down. Again, just thoughts.

The one thing that makes me lean towards thinking it may be true is the addition of a specific "Trac Kill" feature when using the Tazer. Why offer that as an additional perk of using that unit, when the factory added a button that supposedly does that?

I appreciate the reply! Makes sense. I can tell you when my steering wheel wasn't centered after the lift supposedly killing TC did nothing to stop the vehicle's panic attack for what I might consider yaw control but others might say is VDC - vehicle dynamic control

 

[Headbarcode]

I appreciate the reply! Makes sense. I can tell you when my steering wheel wasn't centered after the lift supposedly killing TC did nothing to stop the vehicle's panic attack for what I might consider yaw control but others might say is VDC - vehicle dynamic control

With the Tazer, I unlocked the ability of full trac kill and also being able to use both lockers in 4h and rear in 2h, as needed of coarse. Amongst other things, I plan on exploring if there's any noticeable difference with or without trac kill. It requires pressing and holding the traction control button for 5 seconds and only resets by restarting the engine.

 

[D60]

With the Tazer, I unlocked the ability of full trac kill and also being able to use both lockers in 4h and rear in 2h, as needed of coarse. Amongst other things, I plan on exploring if there's any noticeable difference with or without trac kill. It requires pressing and holding the traction control button for 5 seconds and only resets by restarting the engine.

Ok good to know! I have the Tazer in now (and it was for event #2 but not #1) but still need to figure out all the features.

I also need to update as I think mine has *0.9

 

[COSJL]

@D60 I got "Service Start Stop" and "Service ESC system" messages together while in 4low going up the mountain. Went away after I restarted. Another time I got "shift to park then gear" and lost power . All messages cleared after restart and I never get these in city/highway driving so far. Only in 4Low.

 

[D60]

@D60 I got "Service Start Stop" and "Service ESC system" messages together while in 4low going up the mountain. Went away after I restarted. Another time I got "shift to park then gear" and lost power . All messages cleared after restart and I never get these in city/highway driving so far. Only in 4Low.

It's nice to know I'm not alone! Thank you!

Although both times we were alone (on the trail) and pretty deep in, so I erred on the side of caution and didn't turn the vehicle off since there was an alleged issue w ESS even though I knew it was likely a false alarm.

But yeah it's only been 4lo which still makes me think the nannies and 4lo are fighting an "inner battle"

 

[COSJL]

It's nice to know I'm not alone! Thank you!

Although both times we were alone (on the trail) and pretty deep in, so I erred on the side of caution and didn't turn the vehicle off since there was an alleged issue w ESS even though I knew it was likely a false alarm.

But yeah it's only been 4lo which still makes me think the nannies and 4lo are fighting an "inner battle"

I waited till I reached the flat area near the summit before I turned off the Jeep. Like you said, I didn't want to be troubleshooting on a narrow rocky section with 1000 feet drop off

 

[COSJL]

Also, both the times I got the error after I switched off the Jeep and started it back again while still in 4Low. Not sure if it is a coincidence or if we are not supposed to turn off and restart the vehicle while it is in 4Low.

 

[Headbarcode]

Also, both the times I got the error after I switched off the Jeep and started it back again while still in 4Low. Not sure if it is a coincidence or if we are not supposed to turn off and restart the vehicle while it is in 4Low.

Perfectly fine to on/off the engine in any drive mode. I fully concur with D60, that the nanny programming is trying to fight the other set of 4lo programming that desensitizes them.

I'm very curious if using the trac kill feature on the Tazer would stop these false alarms from happening.

 

[Greg H]

I was in Estes Park, CO last week. Every time we went in the park (4 different days) and drove up over 11,000' I would get the Service start stop system, traction control light, and a blind spot alert Unavailable do to sensors blocked message. I could pull over and shut off and restart and they would clear. But if we were still over 11,000' The messages would come back after several miles. If we descend below 11,000' and I restarted they wouldn't come back. We drove 700 miles home and I've driven all this week back in MO and haven't had a single issue. Not sure how the altitude can cause an issue with the electronics or sensors. But it appears it does.

 

[D60]

I was in Estes Park, CO last week. Every time we went in the park and drove up over 11,000' I would get the Service start stop system, traction control light, and a blind spot alert Unavailable do to sensors blocked message. I could pull over and shut off and restart and they would clear. But if we were still over 11,000' The messages would come back after several miles. If we descend below 11,000' and I restarted they wouldn't come back. We drove 700 miles home and I've driven all this week back in MO and haven't had a single issue. Not sure how the altitude can cause an issue with the electronics or sensors. But it appears it does.

See it's funny you say that 'cause both times it happened to me was after I had crested Hayden Pass (10,700) and Taylor Pass (11,948)

I was also wondering if altitude had anything to do with it although it makes NO sense and I was just bashing TFLcar for thinking their BSG problems on Mt Evans might be altitude related (although in their case they had legit charging issues, not "ghosts in the machine")

 

[D60]

Also I wouldn't care a single bit if it were only nannies, but once the vehicle thinks something is wrong w ESS I get just a bit concerned when we're out alone in remote areas only 'cause it's been well documented legit ESS issues can mean one battery has shit the bed or something isn't charging correctly, etc etc and on and on

Even then it's not usually a dead-in-the-water situation but if one of my batts is dead I want to know.

I do carry a fused jumper for N1/N2, etc and a lithium jumper pack (which should work if the batteries are manually isolated), but still it's no fun to be troubleshooting no-start issues alone on the trail -- NOT that I've had any such actual issues from this

 

[COSJL]

@D60 @Greg H I was just under 11K ft the first time and near 13K ft the second time this happened. Mine has the 3.6 engine, do you guys have the 2.0?

 

[COSJL]

Another note - I have driven upto 12k feet without any issues when I was in 2H most of the time and 4H for maybe a few minutes. This is why I think my problem has more to do with 4L than just altitude.

Sponsored