Turn off traction control?

[autotragic]

z automotive stuff just seems a bit buggy for my tastes. I just went with ECRI to do some light settings changes and I deal with the rest of the factory stuff.

I don't think it's buggy per se I just think that the manual isn't written very well. I know I use the taser to do all kinds of shit I mean disable my proximity key the blind spot monitoring the backup sensors I used it to disable my drls so I just have the halos when I'm driving I mean all kinds of stuff I couldn't live without it.

Sponsored

 

[Remorseless]

I don't think it's buggy per se I just think that the manual isn't written very well. I know I use the taser to do all kinds of shit I mean disable my proximity key the blind spot monitoring the backup sensors I used it to disable my drls so I just have the halos when I'm driving I mean all kinds of stuff I couldn't live without it.

Well, I do count documentation as being susceptible to bugs. Spent a solid chunk of my career dealing with doc bugs.

 

[Ratbert]

See that's the beauty of the taser if you map a steering wheel control to it you can have the sway bar disconnected all the way to the speed limiter if you want.

Strangely it still alerted the crap out of me at 18+ mph when I used the steering wheel button to disable the sway bar.

The only thing I have on the steering wheel now is turn assist. That comes in incredibly handy at times.

 

[autotragic]

Well, I do count documentation as being susceptible to bugs. Spent a solid chunk of my career dealing with doc bugs.

I can agree with that I definitely can agree with that. Poor documentation is the bane of my existence. Unfortunately it seems to be the norm in the world today or maybe it always has been but it seems to be getting worse and it drives me nuts.

 

[Ratbert]

Well, I do count documentation as being susceptible to bugs. Spent a solid chunk of my career dealing with doc bugs.

Someone rewrote a crapload of those docs for him a while back. Pretty sure that was all ignored.

 

[Remorseless]

Someone rewrote a crapload of those docs for him a while back. Pretty sure that was all ignored.

I can agree with that I definitely can agree with that. Poor documentation is the bane of my existence. Unfortunately it seems to be the norm in the world today or maybe it always has been but it seems to be getting worse and it drives me nuts.

 

[autotragic]

Wait you don't cry into your pillow every night?

 

[Remorseless]

Wait you don't cry into your pillow every night?

Pillow's being used by someone else for other reasons

 

[autotragic]

Pillow's being used by someone else for other reasons

 

[phageghost]

In my experience, the Tazer does two things with the sway bar:

1. Allows it to be disconnected in 2WD (but will still follow the 18 MPH max speed limit)
2. Adds a "SwayKill" function. This aspect is poorly documented and took me some trial and error to figure out.

A. You have to map it to a steering wheel button to activate it.​

B. With "SwayKill" activated, it ignores the 18 MPH max speed.​

C. It doesn't actually "kick in" unless the jeep is at a complete stop, but it will remember that you have it activated and kick in as soon as a stop is made.​

D. Whether intended behavior or a bug, any additional functions mapped to the cruise control buttons still take effect when using cruise control.​

E. As a result of all this, I would find myself using cruise control on the highway, adjusting my speed up and down with the buttons . . . which also turned on SwayKill. But this had no effect until I came to a stoplight, where SwayKill would kick in. So, driving away from the light I'd suddenly get a message that my swaybar was disconnected (and feel it!). But it won't let you reconnect unless below 18 MPH, so I'd have to slow down or pull over to fix it.​

F. Bottom line:​

1. When you want to be able to go faster than 18 MPH with a disconnected sway bar, come to a complete stop and activate "SwayKill" with a mapped button.​

2. When using cruise control, keep the secondary display set to "Audio" so you can see the messages from Tazer about SwayKill and SwayConnect being triggered, and make sure you're in "SwayConnect" when you finish adjusting speed or whatever. Even numbers FTW!​

 

[Heimkehr]

Poor documentation is the bane of my existence. Unfortunately it seems to be the norm in the world today or maybe it always has been but it seems to be getting worse and it drives me nuts.

I hear you.

For a variety of reasons, some of which would invite a vacation (and thus have to go unmentioned), I don't envision the problem getting better any time soon.

 

[Ratbert]

In my experience, the Tazer does two things with the sway bar:

1. Allows it to be disconnected in 2WD (but will still follow the 18 MPH max speed limit)
2. Adds a "SwayKill" function. This aspect is poorly documented and took me some trial and error to figure out.

A. You have to map it to a steering wheel button to activate it.​

B. With "SwayKill" activated, it ignores the 18 MPH max speed.​

C. It doesn't actually "kick in" unless the jeep is at a complete stop, but it will remember that you have it activated and kick in as soon as a stop is made.​

D. Whether intended behavior or a bug, any additional functions mapped to the cruise control buttons still take effect when using cruise control.​

E. As a result of all this, I would find myself using cruise control on the highway, adjusting my speed up and down with the buttons . . . which also turned on SwayKill. But this had no effect until I came to a stoplight, where SwayKill would kick in. So, driving away from the light I'd suddenly get a message that my swaybar was disconnected (and feel it!). But it won't let you reconnect unless below 18 MPH, so I'd have to slow down or pull over to fix it.​

F. Bottom line:​

1. When you want to be able to go faster than 18 MPH with a disconnected sway bar, come to a complete stop and activate "SwayKill" with a mapped button.​

2. When using cruise control, keep the secondary display set to "Audio" so you can see the messages from Tazer about SwayKill and SwayConnect being triggered, and make sure you're in "SwayConnect" when you finish adjusting speed or whatever. Even numbers FTW!​

I worked with the Tazer guy for weeks trying to track that down. He claimed that nobody else had reported the issue. Now it's no longer mapped to a button.

 

[NBB]

Thanks for checking the manual. Unfortunately, that did not help. If I hold the button for 5 - 10 seconds, nothing special happens. If traction control is on or off and I hold the button for an extended time (some amount of time longer than 10 seconds) it chimes turns traction control on, then makes the button useless for about 1 minute.

I have a 2021 Rubicon Unlimited - does the same thing. No idea what year that manual covers.

 

[cosmokenney]

I think you also need to turn of ASC.

 

[THAW]

In my experience, the Tazer does two things with the sway bar:

1. Allows it to be disconnected in 2WD (but will still follow the 18 MPH max speed limit)
2. Adds a "SwayKill" function. This aspect is poorly documented and took me some trial and error to figure out.

A. You have to map it to a steering wheel button to activate it.​

B. With "SwayKill" activated, it ignores the 18 MPH max speed.​

C. It doesn't actually "kick in" unless the jeep is at a complete stop, but it will remember that you have it activated and kick in as soon as a stop is made.​

D. Whether intended behavior or a bug, any additional functions mapped to the cruise control buttons still take effect when using cruise control.​

E. As a result of all this, I would find myself using cruise control on the highway, adjusting my speed up and down with the buttons . . . which also turned on SwayKill. But this had no effect until I came to a stoplight, where SwayKill would kick in. So, driving away from the light I'd suddenly get a message that my swaybar was disconnected (and feel it!). But it won't let you reconnect unless below 18 MPH, so I'd have to slow down or pull over to fix it.​

F. Bottom line:​

1. When you want to be able to go faster than 18 MPH with a disconnected sway bar, come to a complete stop and activate "SwayKill" with a mapped button.​

2. When using cruise control, keep the secondary display set to "Audio" so you can see the messages from Tazer about SwayKill and SwayConnect being triggered, and make sure you're in "SwayConnect" when you finish adjusting speed or whatever. Even numbers FTW!​

The above matches my experience, with the exception that at least some of the time mapped buttons are disabled with cruise control engaged.

I'd also note it's very possible to press the mapped Swaykill button while moving and never initiate it at a stop. The brake pedal must be depressed far enough to trigger it.

Sponsored