What's new
By:
Ram Heavy Duty Forum

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Tazer DT on 4.5 Gen (2023)?

T

tacticalcucumber

New Member
Messages
24
Reaction score
5
Points
3
This is probably a question for @Jimmy07 or @Brutal_HO. I'm switching from a 2020 1500. Loved my Tazer DT, but they say their Tazer Ram won't work. That's fine. But, I do wonder, having looked up the PNs for the SGWs... while they are different PNs, they look the same and have the same connectors from what I can tell. Anyone tried plugging it in? What would be the consequences of doing it? Just wondering.
 
Last edited:
the SGW module is not an ideal component to use in the HD trucks as the connector is behind the cluster. Kaodech security bypass is the ideal security bypass for the HDs and takes 2 seconds to install
 
H3LZSN1P3R said:
the SGW module is not an ideal component to use in the HD trucks as the connector is behind the cluster. Kaodech security bypass is the ideal security bypass for the HDs and takes 2 seconds to install
Click to expand...
Yeah certainly not an ideal location but since you leave the Tazer in there I figured it might be worth it... just didn't want to brick my truck. I wondered if anyone's tried plugging it in.

Also tracking the Kaodtech. I'll probably do that. But I have a suspicion that whatever makes the Tazer Ram NOT work with 2023s is what made the Tazer DT not work with 2022 and under HDs. I know enough to break things so I wanted some more expert heads to think it over. I apprecicate the input for sure
 
tacticalcucumber said:
Yeah certainly not an ideal location but since you leave the Tazer in there I figured it might be worth it... just didn't want to brick my truck. I wondered if anyone's tried plugging it in.

Also tracking the Kaodtech. I'll probably do that. But I have a suspicion that whatever makes the Tazer Ram NOT work with 2023s is what made the Tazer DT not work with 2022 and under HDs. I know enough to break things so I wanted some more expert heads to think it over. I apprecicate the input for sure
Click to expand...
First thing I would want to know is, what non-menu live functions are automatically implemented when the tazer DT is plugged into a 1500?
 
Jimmy07 said:
First thing I would want to know is, what non-menu live functions are automatically implemented when the tazer DT is plugged into a 1500?
Click to expand...
That's exactly the kind of stuff I'm talking about that I wouldn't think of lol. Fair point that I can't answer in depth. I'm sure the marrying process does something... but not entirely sure. It has to mimic the SGW though so I would assume it couldn't be anything crazy (for a 1500)... but these trucks are such a frankenstein who knows.

I guess maybe I should reach out to Tazer?
 
tacticalcucumber said:
That's exactly the kind of stuff I'm talking about that I wouldn't think of lol. Fair point that I can't answer in depth. I'm sure the marrying process does something... but not entirely sure. It has to mimic the SGW though so I would assume it couldn't be anything crazy (for a 1500)... but these trucks are such a frankenstein who knows.

I guess maybe I should reach out to Tazer?
Click to expand...
The marrying process is actually a non issue because it’s the same basic thing that alfaobd does- creates a backup file to restore to when unmarried (except it locks the VIN to the device), and the settings change write process is the same.
If a tazer owner already has alfaobd or JScan, there’s really no reason to even marry the tazer. Do the settings changes with alfaobd, and use the tazer for live functions only.
I’m not sure if the cruise control button messages are different for the HDs than the 1500’s, and maybe that could be a reason it wouldn’t work. But if there’s some live non-menu settings in place just by being plugged in, there might be some messages it’s injecting onto the bus that the HD might not know what they are, and freak out.
There’s no harm in trying it out. Plug it in and see if you can navigate the menus with the cruise buttons. Worst thing that can happen is the cluster will freak out and throw all of its errors, but it’ll be rectified once the tazer is removed.
The one thing I would absolutely not do with the tazer DT on an HD (if it does work), is set up anything that has to do with the PIN security or “kill by fob”.
 
Jimmy07 said:
The marrying process is actually a non issue because it’s the same basic thing that alfaobd does- creates a backup file to restore to when unmarried (except it locks the VIN to the device), and the settings change write process is the same.
If a tazer owner already has alfaobd or JScan, there’s really no reason to even marry the tazer. Do the settings changes with alfaobd, and use the tazer for live functions only.
I’m not sure if the cruise control button messages are different for the HDs than the 1500’s, and maybe that could be a reason it wouldn’t work. But if there’s some live non-menu settings in place just by being plugged in, there might be some messages it’s injecting onto the bus that the HD might not know what they are, and freak out.
There’s no harm in trying it out. Plug it in and see if you can navigate the menus with the cruise buttons. Worst thing that can happen is the cluster will freak out and throw all of its errors, but it’ll be rectified once the tazer is removed.
The one thing I would absolutely not do with the tazer DT on an HD (if it does work), is set up anything that has to do with the PIN security or “kill by fob”.
Click to expand...
Awesome. Thank you for that. I don't think I'd use those functions anyway thankfully. I think it's worth trying since I have the thing. If it doesn't work I'll sell it. I'll post back when I see what happens.
 
Just in case anyone was wondering - I tried it. Nothing happened. No codes, no lights... nothing. Steering wheel controls did not activate the tazer. I realized that it could be possible probably...but the "audio" screen required to access the tazer on DTs doesn't really exist in the same way on the new cluster so it'd have to be reprogrammed on tazer's side (which I'm sure they're working on).

Anyone wanna buy a Tazer DT? Lol
 
You must log in or register to reply here.
Back
Top