DTC U0415-00 code after installing Tazer JL Mini

[4a4c55]

I've got a 2020 Sahara Unlimited. Runs great, no problems ... until I installed my Tazer JL Mini for my wife's birthday. She doesn't like the ESS, so I thought we could have the JL remember the last setting for it so it would remain off all the time, effectively. It would be nice to have navigation in motion, and some tire pressure tweaks, too.

After getting the SGW cables hooked up, everything worked as I expected. The instructions are pretty hard to follow. (For example, how do I exit the menu altogether?) But I have a check engine light and the Tazer itself reports a U0415-00 code in the DTC. The Tazer won't clear it.

Tomorrow, I'll try my Autel scanner to read the code and do a reset that way ... until then, anyone know if this is a known issue? Looks like this is an ABS code. Why won't it clear?

Sponsored

 

[Jeffy56]

Everybody must be out partying. I hear you. I started with the lite, then went all in. I found it useful to either print out the instructions or have the laptop right there. Using their extension cable helps as those connects are difficult to axcess. Pulling the lower skirt of the dash helps. Basic troubleshooting, unmarry and remove the Tazer and see if the problem goes away. If not, try to visually check connecter pins to make sure one didn't get tweaked. Reinstall and follow Tazer instructions exactly. Reading them the night before, then rereading helps. I hope this helps. I note having side steps makes it harder to see underdash.

 

[RatZero]

Also, make sure the Tazer is updated to the latest firmware. Depending on where you got it, there’s a good chance it’s at least a version or three behind.

 

[4a4c55]

Also, make sure the Tazer is updated to the latest firmware. Depending on where you got it, there’s a good chance it’s at least a version or three behind.

It's brand-new. The firmware utility said there were no updates available.

I removed the Tazer and started the Jeep -- no CEL. Restarted a couple of times, still no CEL.

And so I reinstalled the Tazer, and my Jeep started without the CEL. Really un-nerving, but I guess it works now.

 

[U EEDIOT]

It might not have been fully connected. I had that problem a couple of times.
I found that the smaller connector on mine is a very tight fit and would sometimes not "click" in.

 

[4a4c55]

It might not have been fully connected. I had that problem a couple of times.
I found that the smaller connector on mine is a very tight fit and would sometimes not "click" in.

Reasonable guess, but definitely not the problem here. The tabs were clicked and I had to release them to remove the Tazer. Certainly a software problem.

 

[U EEDIOT]

Reasonable guess, but definitely not the problem here. The tabs were clicked and I had to release them to remove the Tazer. Certainly a software problem.

A software problem that corrected itself by reconnecting the hardware???

 

[4a4c55]

A software problem that corrected itself by reconnecting the hardware???

Why not? The Tazer has un-switched power from the harness. It might go to sleep after a bit, but it's not truly off until it's unplugged. Removing it from power resets it.

OTOH, how would all functions work, but only one strange DTC code logged persistently because of a hardware problem? Either the device can successfully communicate with the CAN bus, or it can't. It would be very odd to not communicate with just one control module and only cause that module to log one single trouble code.

The device works by yelling commands and status packets onto the CAN bus. It might adequately follow the vendors protocol for those communications, or it might not -- and still usually "seem to work". Super useful product, and neat that it can try to leverage the available standard of the transport layer to play in the proprietary application layer. But it can't possibly be completely tested because that layer is at least partially opaque to any developer.

 

[U EEDIOT]

Sounds like you reconnected it and did the marry/reboot/sleepx2 routine correctly this time.
Glad it works for you now.

 

[Rhinebeck01]

Why not? The Tazer has un-switched power from the harness. It might go to sleep after a bit, but it's not truly off until it's unplugged. Removing it from power resets it.

OTOH, how would all functions work, but only one strange DTC code logged persistently because of a hardware problem? Either the device can successfully communicate with the CAN bus, or it can't. It would be very odd to not communicate with just one control module and only cause that module to log one single trouble code.

The device works by yelling commands and status packets onto the CAN bus. It might adequately follow the vendors protocol for those communications, or it might not -- and still usually "seem to work". Super useful product, and neat that it can try to leverage the available standard of the transport layer to play in the proprietary application layer. But it can't possibly be completely tested because that layer is at least partially opaque to any developer.

This issue was undoubtedly a direct result of a process/procedural error on your part.. 99% percent of the time when you see such Tazer JL related stories posted here on this forum or elsewhere, it is as a result of a process/procedural error on the part of the Tazer JL user himself...

Take it in stride so to speak.

Note: I'm not saying it is never a Tazer JL issue ... yes, it could be but not often at all.

 

[Rhinebeck01]

I've got a 2020 Sahara Unlimited. Runs great, no problems ... until I installed my Tazer JL Mini for my wife's birthday. She doesn't like the ESS, so I thought we could have the JL remember the last setting for it so it would remain off all the time, effectively. It would be nice to have navigation in motion, and some tire pressure tweaks, too.

After getting the SGW cables hooked up, everything worked as I expected. The instructions are pretty hard to follow. (For example, how do I exit the menu altogether?) But I have a check engine light and the Tazer itself reports a U0415-00 code in the DTC. The Tazer won't clear it.

Tomorrow, I'll try my Autel scanner to read the code and do a reset that way ... until then, anyone know if this is a known issue? Looks like this is an ABS code. Why won't it clear?

@4a4c55

I do believe your installing a ZAutomotive Tazer JL Mini on your Wife's JL was probably a bad move on your part..

In your post you mentioned "She doesn't like the ESS" and you went on to say "it would be nice to have navigation in motion, and some tire pressure tweaks, too."

Anyway, you would have been far better off to purchase her an easy to install, known to be non-problematic and the pick of the litter for a JL, sold by a forum sponsor, SmartStopStart unit. Steve from @SmartStopStart.com , if you message him and ask, he will sell you one for $99.00. It's a terrific offering and you will never have any lets say headaches with it. When you eventually sell that JL you will be able to easily sell the well known and highly touted SSS unit for about half of what you paid for it.

https://www.jlwranglerforums.com/fo...s-the-way-it-should-have-been-designed.13946/

As for changing tire pressures and say high beams with fogs, etc. you would be better off going with JSCAN. With JSCAN you make the changes, remove the hardware needed for the deed and then reconnect the security gateway and then give your Wife back her JL. Do this and she will never have any Tazer JL moments and you will not have to unmarry the JL for dealership visits and or deal with the big learning curve associated with the Tazer JL Mini.

Almost forgot to mention... That navigation in motion > Set In-Motion Nav “InMoNav you mentioned.... Well, that Tazer JL Min feature can cause and has caused headaches if a gal or guy forgets to turn it off after each use... (i.e. No start because of 12v depletion)

Mentioned briefly/ in passing in the ZAutomotive instructions:

"Set In-Motion Nav “InMoNav”: Set to ON, this
allows address entry while the vehicle is in motion. This
is for PASSENGER use. It may be illegal for the driver
to manipulate the navigation system while driving. It is
recommended to leave this setting OFF, enabling it only
when you need to use it.

In closing, though I am very pro ZAutomotive and their offerings (see my many many past, positive posts talking Tazer JL) and am very well versed in regard to the Tazer JL.

I encourage you to not have the Tazer JL on your Wife's JL. She does not need it, can get into issues with it... and she/you, will be dealing with all that goes with having a Tazer JL Mini.

 

[Spartywarrior]

Why not? The Tazer has un-switched power from the harness. It might go to sleep after a bit, but it's not truly off until it's unplugged. Removing it from power resets it.

OTOH, how would all functions work, but only one strange DTC code logged persistently because of a hardware problem? Either the device can successfully communicate with the CAN bus, or it can't. It would be very odd to not communicate with just one control module and only cause that module to log one single trouble code.

The device works by yelling commands and status packets onto the CAN bus. It might adequately follow the vendors protocol for those communications, or it might not -- and still usually "seem to work". Super useful product, and neat that it can try to leverage the available standard of the transport layer to play in the proprietary application layer. But it can't possibly be completely tested because that layer is at least partially opaque to any developer.

When in doubt blame it on the Tazer. Ugh.

 

[4a4c55]

Sounds like you reconnected it and did the marry/reboot/sleepx2 routine correctly this time.
Glad it works for you now.

It was married before I disconnected it, and definitely went through at least two reboot/sleep cycles beforehand. But certainly something got reset. I'll be able to drive around today and confirm that it's behaving.

 

[RatZero]

Sounds like you reconnected it and did the marry/reboot/sleepx2 routine correctly this time.
Glad it works for you now.

This. My next suggestion would have been doing a full reboot and/or clear of the Tazer. The problem sometimes is that the Tazer will work with the new settings regardless of whether the owner does a reboot/sleep but iT still should be done regardless.

Sponsored