Tazer JL issue, anyone else having?- RESOLVED

[justjoez]

I still don't know what happened to your Jeep, but I'm starting to gather that you unmarried the Tazer and then the radio no longer worked?
Is it possible that you unmarried and THEN removed the tazer and THEN the screen went black? That would point to the smaller of the two connectors not being fully pugged back into the SGW.
Did you try to reboot the radio? Did you do the full reboot and 2 sleep cycles after unmarrying?
It's really not that hard to figure out what happened... if I just had some more info.

And no, paying the $50 isn't for unmarrying, it wouldn't solve anything.

 

[justjoez]

I just found your glitch report - was in spam folder for some reason -

Same questions apply, is this as SOON as you unmarry and it finishes counting down or after you remove the tazer?
If its after you remove the Tazer, are you plugging the SGW back in? Are you connecting direct or using one of our SGW extensions?

 

[Smess]

I updated firmware, myself and now my vendor that has sold thousand of them agrees something changed.

I need to go to dealer so I unmarried, cleared DTC’s, rebooted, did sleeps slow as you taught me in past even opening and closing door. Removed tazer, plugged back in to extension cable, radio black screen and usb ports no power.

only thing I have not done is check to make sure extension cable is seated all the way in.

I have a Recon, a Gladaitor, and a JL with a 6.4 conversion I can try to unmarry the JL conversion and see if same happens. Glad is way too modified to unmarry but it firmware is .4 still and that seems to be where the issue started. Screens are different during the unmarry process than I and my vendor recall.

I dont remember how to do a hard reboot on radio.

Thanks

 

[Smess]

I just found your glitch report - was in spam folder for some reason -

Same questions apply, is this as SOON as you unmarry and it finishes counting down or after you remove the tazer?
If its after you remove the Tazer, are you plugging the SGW back in? Are you connecting direct or using one of our SGW extensions?

After I remove, yes after, yes extension but have no checked for seating on extension

 

[justjoez]

And now I found your last email - And saw you listed a couple DTC's.

It appears your radio is offline due to not being connected physically to the bus. That points at onw thing - that smaller connector isn't making contact. Check that the plugs are fully seating, and check to see if there's a bent pin. If you find nothing, remove the extension and plug directly into the SGW - it could be that the extension is damaged (a wire pulled loose or something).

There's no setting possible or command that I could send to keep the radio off after the Tazer is physically removed, so it's definitely not some programming gone wrong. I'm thinking that the bent pin/pulled wire happened one of the times you pulled the Tazer, and probably updated it while it was out.

 

[Smess]

My DTC’s I sent in that email were when I went to dealer.

Normally I remove tazer and go in and clear cods with reader.

It all started I went to get lost key programmed. Got to dealer and thought who knows what they gonna do. I unmarried. Gave to tech, he cane back and said he cant program he cant contact all modules.

He said u have another issue and radio was coming on and flickering and then coming back on like it was trying to reboot every 5 or 7 seconds.

Came home and said interesting plugged in reader and got those codes.

In tazer mode went to pc to check and 04/22 firmware was not done. Also noticed a guy complaining of new firmware and black screen.

Updated, installed, drove couple days and then went to unmarry to prepare for dealer re-visit.

Black screen ever since

 

[Smess]

Cant promise I cleared codes when i unmarried or if necessary the DTC’s and + and - etc is very ambiguos and no instructions I have seen

 

[Smess]

And now I found your last email - And saw you listed a couple DTC's.

It appears your radio is offline due to not being connected physically to the bus. That points at onw thing - that smaller connector isn't making contact. Check that the plugs are fully seating, and check to see if there's a bent pin. If you find nothing, remove the extension and plug directly into the SGW - it could be that the extension is damaged (a wire pulled loose or something).

There's no setting possible or command that I could send to keep the radio off after the Tazer is physically removed, so it's definitely not some programming gone wrong. I'm thinking that the bent pin/pulled wire happened one of the times you pulled the Tazer, and probably updated it while it was out.

When you say updated it while it was out? What do you mean?

 

[justjoez]

When you say updated it while it was out? What do you mean?

I figured you may have taken the opportunity to do a firmware update while the Tazer was removed from the Jeep, which would lead you to think that the firmware was to blame.

From all above it sounds like the connection to the SGW is the issue; loose or damaged SGW extension most likely..

Please check them asap, remove the extension if you don't see any obvious issue.

 

[Smess]

I figured you may have taken the opportunity to do a firmware update while the Tazer was removed from the Jeep, which would lead you to think that the firmware was to blame.

From all above it sounds like the connection to the SGW is the issue; loose or damaged SGW extension most likely..

Please check them asap, remove the extension if you don't see any obvious issue.

thanks Joe, you are baseing that on the codes that I sent you?

Remember those codes are from when I quickly unmarried and the tech came back and said the thing about the modules.

I am leaving house now will report bacl shortly.

Thanks for stopping in, its amazing how a thread can take a turn like that )). reminds me of my old forum management days. I bet the admins here dont take what you are doing as soliciting and they are probably honored you posted on their site.

the tazer is a remarkable product, I hope my emails dont end up in spam folder as with the 3 Jeeps I have that is a good covering of a lot of scenarios the tazer is in and the things it is faced with. when you, as a implementer and trouble shooter, get an email from me about a Glitch we are either going to find a glitch or a scenario that more than likely someone else is going to face as I do everything I can to troubleshoot and make sure its not me but I am nowhere near perfect.

Not sure what came of it but I reported the glitch to you last year that when a 392 is in force 2wd and the first thing you do when you start it is put it in reverse and I swear it is no longer in 2wd but I have a Recon now and a new tazer and dont experience that anymore

thanks, will report back before 5

 

[Smess]

I am happy to report that as Joe thought the connection on the extension where it seats back in to the original location under the dash was in but with a little push the radio screen went from black back to life like normal.

My apologies to Joe and ZAutomotive but happy to see him involved on the Forum as his product and knowledge are remarkable.

I also to say that Joe has presonally taught me when working with the tazer always go slow and make sure connections are right and give software a chance to load and on and on.

Those of you that own a tazer know that the initial installation pretty aggravating but not always. This particular install was done under my supervision but by a young man that has no knowledge in the tazer and perhaps I should have gone behind him and double checked his work.

Everyone have a great weekend.

Thanks Joe!!

 

[Guest862]

I am happy to report that as Joe thought the connection on the extension where it seats back in to the original location under the dash was in but with a little push the radio screen went from black back to life like normal.

My apologies to Joe and ZAutomotive but happy to see him involved on the Forum as his product and knowledge are remarkable.

I also to say that Joe has presonally taught me when working with the tazer always go slow and make sure connections are right and give software a chance to load and on and on.

Those of you that own a tazer know that the initial installation pretty aggravating but not always. This particular install was done under my supervision but by a young man that has no knowledge in the tazer and perhaps I should have gone behind him and double checked his work.

Everyone have a great weekend.

Thanks Joe!!

Well this is a nice report. Have a nice weekend, all.

 

[thexr6]

Well this is a nice report. Have a nice weekend, all.

All’s well that ends well.
Just installed my 2nd JL mini, but on the 392. All good!

 

[justjoez]

Glad we found the culprit. As soon as you said dead radio on removal, I knew it had to be something with that connection.

 

[dog]

Glad we found the culprit. As soon as you said dead radio on removal, I knew it had to be something with that connection.

I've never owned a Tazer, but I have done more than a decade of remote troubleshooting with (often, very unhappy) customers in the field. If they're calling me, the stakes are high and they're blaming my product for a *big* failure.

I just want to chime in on this thread and say I am absolutely blown away by the sheer professionalism demonstrated by @justjoez here. What a (pardon my french) fucking BADASS he is for how he handled this situation.

Hats off from one nerd to another. This guy here knows his product (and the systems with which it integrates). It just needed to be said out loud.

Not gonna lie, I'll probably buy a Tazer based off this interaction alone. Cheers Joe!

 

[dblplay1212]

I've never owned a Tazer, but I have done more than a decade of remote troubleshooting with (often, very unhappy) customers in the field. If they're calling me, the stakes are high and they're blaming my product for a *big* failure.

I just want to chime in on this thread and say I am absolutely blown away by the sheer professionalism demonstrated by @justjoez here. What a (pardon my french) fucking BADASS he is for how he handled this situation.

Hats off from one nerd to another. This guy here knows his product (and the systems with which it integrates). It just needed to be said out loud.

Not gonna lie, I'll probably buy a Tazer based off this interaction alone. Cheers Joe!


View attachment 6418

Well said. He handled it way better than I would have lol

 

[dog]

@Smess - finally catching up on all the 392 threads this evening and I've come across many, many posts by you regarding this issue. I totally understand your frustration, and it's clear that making noise about the issue you were having did, in fact, get Joe's attention and got your issue resolved.

But, it's important to acknowledge, publicly, the problem was NOT Tazer's/Joe's fault. They also certainly weren't ransoming anyone's vehicle, and there aren't any known issues with the firmware update.

Considering the degree to which you put Tazer (and Joe personally) on blast (especially in regards to the "$50 ransom" accusations), I think it'd be only fair to for you to go back and either remove the inaccurate/inflammatory parts of those posts, or add an edit to the top of the those posts describing that the issue was NOT with the Tazer.

One easy way to do that would be to put a link to the post of the solution (like this) into the TOP of those posts for posterity.

People use (and will continue to use in the future) the search on this forum for issues when they have problems, and you want to point people towards a solution, not lead them down an angry rabbit hole. I frequently find 10+ year old posts on forums when I'm looking for troubleshooting solutions, so save future generations the pain/trouble, and do right by @justjoez !

Again, it's totally understandable to be upset about support not getting back to you, and to be upset that your emails were found in joe's spam folder. That would frustrate me endlessly too. But here's the man himself coming into the forums to fix an issue that he didn't cause, and doing it with class, so I think it'd be the least you could do to put things square.

All the best to everyone and super glad that the issue was resolved!

 

[Smess]

I've never owned a Tazer, but I have done more than a decade of remote troubleshooting with (often, very unhappy) customers in the field. If they're calling me, the stakes are high and they're blaming my product for a *big* failure.

I just want to chime in on this thread and say I am absolutely blown away by the sheer professionalism demonstrated by @justjoez here. What a (pardon my french) fucking BADASS he is for how he handled this situation.

Hats off from one nerd to another. This guy here knows his product (and the systems with which it integrates). It just needed to be said out loud.

Not gonna lie, I'll probably buy a Tazer based off this interaction alone. Cheers Joe!


View attachment 6418

When I first got my tazer I was having problems as the instructions, and Joe agrees, need to be modified. I spoke to him and he loves his product and I could tell he cares more about the product and it working than about making money. It was obvious.

I also was facinated at how knowledable he was and I gotta tell you as much as I love Jeeps I would love to have an afternoon or even a lunch to learn more and pick his brain.

He taught me so much that I was able to help many others on several differnet forums and kept all our emails as he explaioned why this does not work with that etc.

I also can tell you that I dont believe it is possible for him to train or teach anyone even close to everything he know because he has so much knowledge and there are too many variables to make it as clear cut as we expect it. I dont think it is possible for him to re-write the instructios either for the same reason. All I suggested was that he changes the verbage so the instructions match the display in our vehicles and if we say yes or no to a feature to clearly spell out what that means. Thats about the best you can do with the instructions and the way they are now is sufficient less the verbage issue.

I bought the tazer originally because I had a Gladiator with 60's that a friend who owns a dealership built for himself and the lockers were engaged by the aux switch and zauto didnt have that feature in the tazer yet. In addition I had a 392 on order and I knew the force 2wd feature was coming and the Recon was not out yet.

I got so frustrated and I had sent two emails and a message that end up in the spam folder and I couldnt go to the dealership until the issue was solved so it was a blessing that Joe came on and helped and hopefully he visits on a regular basis.

If you ever get the chance to talk to him I can assure you that you will have the same experince that I did, how he knows and learned all this is mind boggling but he told me how and there are not many people like him. He carries a very good reputation throughout the industry I have come to learn.

 

[Jeepstin392]

One suggestion
Change the thread title to include “resolved”

I’d hate for others to read the first few and base their decisions on what was operator error.

 

[dog]

@willy @YukonCornelius - mod team!

Do you gentlemen have any opinion one way or the other on the last few posts in this thread (and the associated posts by @Smess )? Maybe mod intervention in some capacity is warranted, maybe not, just want to bring it to your attention.

Personally I'd make the case that for the reputation of the forum, for posterity, and for how we'd like to set an example for how to treat our participating vendors, it'd be in the forum's best interest to edit/remove the more defamatory/incendiary posts by @Smess , as they turned out to be entirely baseless. That is, if he doesn't sufficiently address those posts himself.