TAZER DT for 2019 RAM 1500

[Jimmy07]

Whoa. Just to make sure I understand this correctly…

When you install the Tazer, you unplug the SGW and plug in the Tazer as shown below. I assume this shield will cover the area. Are you saying that there’s a simple set of wires that can be snipped to disable all of that? If so, that would certainly make for a quick defeat.

I’ve got the Ravelco installed already, so this was just icing on the cake. Or not.

View attachment 143854

So, for the live features, the tazer has to stay plugged in because it’s modifying messages on the bus. It gets access to the bus through the security gateway connectors, while bypassing the SGW at the same time. Ultimately, that bus access point is via the 2 canbus junction blocks that all the modules are plugged into to communicate with each other, including the gateway. Disconnect the gateway from the bus, and tazer no longer has access to it for live features.


Most of the the attempted thefts where people have caught them and posted pictures paint the picture of what they are usually doing:
1) Smash the rear window so they don’t have to open a door setting off the VTA, and so they are not sitting in broken glass while they work.


2) Pop out the headlight switch to gain access to the canbus block.


3) plug their device into the bus and OBD port to pull the RFH PIN and program the fob (someone had a pic of a programmer left behind, but can’t find it right now). (The OBD port is not absolutely necessary as the device can be set up with its own small 12v power supply.)

 

[HSKR R/T]

So, for the live features, the tazer has to stay plugged in because it’s modifying messages on the bus. It gets access to the bus through the security gateway, while bypassing it at the same time. Ultimately, that bus access point is via the 2 canbus junction blocks that all the modules are plugged into to communicate with each other, including the gateway. Disconnect the gateway from the bus, and tazer no longer has access to it for live features.
View attachment 143856

Most of the the attempted thefts where people have caught them and posted pictures paint the picture of what they are usually doing:
1) Smash the rear window so they don’t have to open a door setting off the VTA, and so they are not sitting in broken glass while they work.
View attachment 143857

2) Pop out the headlight switch to gain access to the canbus block.
View attachment 143855

3) plug their device into the bus and OBD port to pull the RFH PIN and program the fob (someone had a pic of a programmer left behind, but can’t find it right now). (The OBD port is not absolutely necessary as the device can be set up with its own small 12v power supply.)
View attachment 143858

So could someone add something behind headlight switch to make it harder to access the canvus block? One of those things that at the very least slows them down

 

[Jimmy07]

So could someone add something behind headlight switch to make it harder to access the canvus block? One of those things that at the very least slows them down

I can’t think of anything clever off hand, aside from diverting the security gateway module canbus connector over to the other, harder to access junction block on the passenger side footwell area.

But, rather than buying any of the anti-theft devices out there, I have a simple method that requires about $20-30 in connector parts.
No factory wiring is cut.
No fuses, relays, etc removed.
No aftermarket switch involved.
It’s the same “concept” as a ravelco, but the truck can be remote started.
You can give your truck and factory service manual schematics to someone for a week, and they won’t get it started no matter how many fobs they program to it.

I know it’s hard to keep stuff from circulating online, but I’ll give anybody details how to go about it via PM.

 

[HSKR R/T]

Depending on how much time you want to spend to prevent drive away theft, could always make a dummy fuel pump relay an swap it out when you park. Not something most thieves would check for, and even if they do look in fuse/relay oanelz they will see a relay installed

 

[Dewey]

Just to confirm: have you updated yet, or are you talking about the previous firmware? And is your radio turned off when you use the menu?

Previous. I haven’t updated to the latest released today. I’ll let you guys be the testers.

 

[HemiDude]

So could someone add something behind headlight switch to make it harder to access the canvus block? One of those things that at the very least slows them down

Like a metal shield, perhaps?

 

[HemiDude]

Seems like a couple of useful updates there. I am interested in the "Added APKill function to override AutoPark" listed on the site, though I don't see it referenced in the updated guide. I assume that removes the trucks propensity to lock the brakes when backing up with the door open.

 

[Eighty]

Seems like a couple of useful updates there. I am interested in the "Added APKill function to override AutoPark" listed on the site, though I don't see it referenced in the updated guide. I assume that removes the trucks propensity to lock the brakes when backing up with the door open.

I think that kills the auto parking brake when you put it in park.

 

[HemiDude]

I think that kills the auto parking brake when you put it in park.

Hmm, that can be controlled from UC. I don't ever that enabled, so I'm thinking that isn't it

 

[HSKR R/T]

I think that kills the auto parking brake when you put it in park.

You can control that in the UC settings, no need for Tazer on that one

 

[Dewey]

In the process of updating to the new firmware the download locked up at 41%. Now my Tazer disconnected and cannot get it to be recognized again when connected. Seems to be corrupted.



I was afraid of something like this happening.

Now what? Any ideas?

I contacted ZAutomotive but haven’t heard back from them yet.

Can I just plug the cables back into the stock factory positions and will everything operate properly till this is figured out? I’m guessing everything except the LIVE functions will still work since it’s still Married…..correct?

 

[HSKR R/T]

In the process of updating to the new firmware the download locked up at 41%. Now my Tazer disconnected and cannot get it to be recognized again when connected. Seems to be corrupted.

View attachment 143902

I was afraid of something like this happening.

Now what? Any ideas?

I contacted ZAutomotive but haven’t heard back from them yet.

Can I just plug the cables back into the stock factory positions and will everything operate properly till this is figured out? I’m guessing everything except the LIVE functions will still work since it’s still Married…..correct?

Did you try using manual update, or the recovery option mentioned?

And yes, you can just plug the SGW cables back in to factory location, and the truck will work just fine. The TazerDT is actually designed so it doesn't have to stay connected all the time. You just lose the live functions. Any other changes you have made, such as fog light drop out, tire size, or DRL location will still be however you set them

 

[Dewey]

Did you try using manual update, or the recovery option mentioned?

And yes, you can just plug the SGW cables back in to factory location, and the truck will work just fine. The TazerDT is actually designed so it doesn't have to stay connected all the time. You just lose the live functions. Any other changes you have made, such as fog light drop out, tire size, or DRL location will still be however you set them

I tried manual and recovery but it just sends me to files on my computer that do not apply to the Tazer in any way. Just sends me to a dead end with no function.

I reconnected the cables in my truck to stock and everything is fine. Just no LIVE settings as I expected.

 

[Dewey]

I tried manual and recovery but it just sends me to files on my computer that do not apply to the Tazer in any way. Just sends me to a dead end with no function.

I reconnected the cables in my truck to stock and everything is fine. Just no LIVE settings as I expected.

ZAutomotive got me squared away. All is good now and downloading fine.

I’ll post this reply in case anybody else runs into the same problem with a Mac.

 

[Dewey]

Menu display is much improved. Doubt I’ll use the new PIN feature but nice to have everything integrating better with Uconnect 5. I’m very happy with the upgrade after a few minor issues that were quickly resolved with direct contact to ZAutomotive.

The standard automated help function leaves something to be desired though. A computer trying to help you gets very frustrating. Just kept looping back around with zero help. Talking with live people is the only way to go.

 

[Dewey]

Anybody else notice Start/Stop reverting back to the auto on position as is from the factory?

Seems like my Tazer doesn’t always remember I had it turned off last ignition cycle like it should. I even caught the light blinking the other day like it was confused. Doesn’t always work like my AutoStop Eliminator did.

 

[Marxvp1]

Menu display is much improved. Doubt I’ll use the new PIN feature but nice to have everything integrating better with Uconnect 5. I’m very happy with the upgrade after a few minor issues that were quickly resolved with direct contact to ZAutomotive.

The standard automated help function leaves something to be desired though. A computer trying to help you gets very frustrating. Just kept looping back around with zero help. Talking with live people is the only way to go.

I just updated to 18.1.7. from 18.1.6. When you updated yours, did it take a long time to update once plugged back into the truck? I can't access any menus because it says "updating". How long should this process take? I have a 2022 Bighorn with 8.4 inch Uconnect 5 (2022+) system. This is the 3rd firmware update I've done and I didn't have this issue prior to this latest version.

 

[Dewey]

I just updated to 18.1.7. from 18.1.6. When you updated yours, did it take a long time to update once plugged back into the truck? I can't access any menus because it says "updating". How long should this process take? I have a 2022 Bighorn with 8.4 inch Uconnect 5 (2022+) system. This is the 3rd firmware update I've done and I didn't have this issue prior to this latest version.

Didn’t notice any difference with mine. Seemed fine with no long updating.

 

[HemiDude]

Anybody else notice Start/Stop reverting back to the auto on position as is from the factory?

Seems like my Tazer doesn’t always remember I had it turned off last ignition cycle like it should. I even caught the light blinking the other day like it was confused. Doesn’t always work like my AutoStop Eliminator did.

I encountered the AS/S issue even with my last update. I let Za know about it, was hoping it would be corrected with this update. Sometimes mine will work fine for weeks, and then go for a few days switching between On and Off for no reason. Then it will be fine again. I haven't done the new update yet, and I haven't had any issues with UC5, so I'm hoping it will be better afterwards.

 

[Dewey]

I encountered the AS/S issue even with my last update. I let Za know about it, was hoping it would be corrected with this update. Sometimes mine will work fine for weeks, and then go for a few days switching between On and Off for no reason. Then it will be fine again. I haven't done the new update yet, and I haven't had any issues with UC5, so I'm hoping it will be better afterwards.

It’s not. My Start/Stop memory worked fine with the earlier update but now with the new update on Monday it’s not remembering the last position it was set on.