TAZER DT for 2019 RAM 1500

[Liquid Li0n]

Just installed Tazer DT on my 2023 1500 Longhorn and programmed a PIN. Be aware that PIN Lock Enable is off by default and needs to be toggled on after coding the PIN.

I mistakenly assumed that the Full Reboot + two sleep cycles sequence is only required when changing non-Live Vehicle Settings, but not for Live function settings. Did the reboot sequence after marrying the Tazer. Then proceeded to setting the PIN Lock plus a few other Live options and omitted the reboot sequence afterwards.

The PIN still lock worked as advertised. However, Engine Light came on and stayed on, and a few DTCs were logged.

Luckily, clearing the DTCs followed by a full Reboot cycle cleared the issue completely and all is well, for now.

A side note: I asked zAutomotive earlier today about the Killbyfob feature, and they confirmed that when the vehicle is locked by the keyfob's button, the very same keyfob's unlock button will be needed to bypass the PIN entry. The other keyfob will not do nor a cloned keyfob. Those would require PIN entry, according to them.

Edit: Firmware version used was 18.2.4.

So that means that the thief that steals your car, needs to obtain the key and can easily drive away, or is the PIN still needed to enter when using that 1 key you locked/unlocked the car with?

 

[HSKR R/T]

So that means that the thief that steals your car, needs to obtain the key and can easily drive away, or is the PIN still needed to enter when using that 1 key you locked/unlocked the car with?

If a thief gets hold of your keyfob, you may as well just kiss your truck goodbye. And then figure out how to not lose your keyfob in the future. there's only so much hand holding aftermarket companies can do. They can't fix all the stupid.

 

[barrak]

So that means that the thief that steals your car, needs to obtain the key and can easily drive away, or is the PIN still needed to enter when using that 1 key you locked/unlocked the car with?

The Killbyfob is an optional feature of the PIN Lock which you may or may not enable. When disabled (default) the PIN will always be needed, however you lock and unlock your vehicle. When enabled, then you can bypass entering the PIN, provided you lock and unlock the vehicle using the physical buttons on the same physical key fob.

So the theory goes.

I agree with @HSKR R/T ... Killbyfob should not have been dreamed up in the first place. If you need the PIN, use the PIN.

 

[HSKR R/T]

The Killbyfob is an optional feature of the PIN Lock which you may or may not enable. When disabled (default) the PIN will always be needed, however you lock and unlock your vehicle. When enabled, then you can bypass entering the PIN, provided you lock and unlock the vehicle using the physical buttons on the same physical key fob.

So the theory goes.

I agree with @HSKR R/T ... Killbyfob should not have been dreamed up in the first place. If you need the PIN, use the PIN.

I'd prefer the killfob over having to enter pin every time. More than likely a thief is going to try cloning you fob, or programmable new inez which would allow killfob to prevent them from stealing the truck. Having to enter a pin everytime I want to drive is actually what has kept me from enabling it. Plus, if my wife ever want to drive the truck, she would get frustrated and not remember the pin, then I would get yelled at. And all married men know, happy wife happy life

 

[barrak]

I'd prefer the killfob over having to enter pin every time. More than likely a thief is going to try cloning you fob, or programmable new inez which would allow killfob to prevent them from stealing the truck. Having to enter a pin everytime I want to drive is actually what has kept me from enabling it. Plus, if my wife ever want to drive the truck, she would get frustrated and not remember the pin, then I would get yelled at. And all married men know, happy wife happy life

I guess I'm concerned that cloning the key fob will clone the Killbyfob ability as well, which would be a security breach.

For what its worth, I just confirmed that locking with one key fob and unlocking with the other will not bypass the PIN, as stated to me by z Automotive.

 

[barrak]

Any one having PIN Lock related issues caused by an active Start/Stop feature in their HEMI eTorque 1500 RAM?

Here's what happened twice today with my 2023 Longhorn (Long Post):

First incident:
---------------
Happened this morning after I installed the Tazer DT, set a PIN code, tested it, then drove a few miles for an errand. All was well until I reached a red traffic light where the Start/Stop turned off the engine. Once the green light came on, I pushed the accelerator and the vehicle moved forward until I was in the middle of the intersection where it entered some kind of limb mode... wouldn't accelerate and the dash prompted me for the PIN and engine light came on with error messages involving electronic throttle control and trailer brakes!!

I moved over and slowed down to park safely. Once the vehicle was slow enough, the ABS locked the vehicle. The transmission rotary selector held firm on D and wouldn't turn. I checked and found a DTC P2166 code was thrown, along with a DTC C10D0, relating to throttle position sensor and electronic brake control, respectively. I turned off the vehicle then back on and entered the PIN code and fiddled about a bit, including disabling the Start/Stop button. Vehicle drove normally afterwards to my destination and then back home, except engine light remained on.

Upon arrival at my destination, I cleared the DTC codes and did a Full Reboot + two Sleep cycles. Engine light didn't go away. Upon arrival back home I did the same again and still engine light remained on. An hour later I started the vehicle and engine light did not come on. Did a multi-stop errand before going back home and all was well throughout.

I would note an important detail: Tazer DT maintained the disabled setting of the Start/Stop button.

Second Incident:
-------------------
Earlier this evening I decided to test the Killbyfob feature using both key fobs, as mentioned in Post #1,265 above. Started the vehicle with the same key fob I've been using so far, entered the PIN, turned the engine off, then locked the vehicle using the key fob's button. I then unlocked the vehicle with the second key fob's button. Once I started the vehicle with the other key fob, I was queried for the PIN which I entered, and then the same error messages appeared and the engine light came on again. Looking down, I noticed the Start/Stop button was not disabled! I'm guessing Tazer DT linked the preserved Start/Stop status to the first key fob that was in use at the time of the initial setting.

I'm done for the evening and will look into erasing DTCs and Full Reboots in the morning. I did email z Automotive after the first incident but don't except to hear from them before Monday.

Until then, any advice or shared experiences will be appreciated.

 

[HSKR R/T]

Any one having PIN Lock related issues caused by an active Start/Stop feature in their HEMI eTorque 1500 RAM?

Here's what happened twice today with my 2023 Longhorn (Long Post):

First incident:
---------------
Happened this morning after I installed the Tazer DT, set a PIN code, tested it, then drove a few miles for an errand. All was well until I reached a red traffic light where the Start/Stop turned off the engine. Once the green light came on, I pushed the accelerator and the vehicle moved forward until I was in the middle of the intersection where it entered some kind of limb mode... wouldn't accelerate and the dash prompted me for the PIN and engine light came on with error messages involving electronic throttle control and trailer brakes!!

I moved over and slowed down to park safely. Once the vehicle was slow enough, the ABS locked the vehicle. The transmission rotary selector held firm on D and wouldn't turn. I checked and found a DTC P2166 code was thrown, along with a DTC C10D0, relating to throttle position sensor and electronic brake control, respectively. I turned off the vehicle then back on and entered the PIN code and fiddled about a bit, including disabling the Start/Stop button. Vehicle drove normally afterwards to my destination and then back home, except engine light remained on.

Upon arrival at my destination, I cleared the DTC codes and did a Full Reboot + two Sleep cycles. Engine light didn't go away. Upon arrival back home I did the same again and still engine light remained on. An hour later I started the vehicle and engine light did not come on. Did a multi-stop errand before going back home and all was well throughout.

I would note an important detail: Tazer DT maintained the disabled setting of the Start/Stop button.

Second Incident:
-------------------
Earlier this evening I decided to test the Killbyfob feature using both key fobs, as mentioned in Post #1,265 above. Started the vehicle with the same key fob I've been using so far, entered the PIN, turned the engine off, then locked the vehicle using the key fob's button. I then unlocked the vehicle with the second key fob's button. Once I started the vehicle with the other key fob, I was queried for the PIN which I entered, and then the same error messages appeared and the engine light came on again. Looking down, I noticed the Start/Stop button was not disabled! I'm guessing Tazer DT linked the preserved Start/Stop status to the first key fob that was in use at the time of the initial setting.

I'm done for the evening and will look into erasing DTCs and Full Reboots in the morning. I did email z Automotive after the first incident but don't except to hear from them before Monday.

Until then, any advice or shared experiences will be appreciated.

Contact Z-automotive and let them know

 

[Legal Brief]

Did you update the Tazer to the newest firm ware before you started? There was one released in April

 

[barrak]

Did you update the Tazer to the newest firm ware before you started? There was one released in April

Yes, I did. It seems there were two releases in April. v18.2.3 on April 17th and v18.2.4 on April 19th, if I remember correctly.

 

[HSKR R/T]

Yes, I did. It seems there were two releases in April. v18.2.3 on April 17th and v18.2.4 on April 19th, if I remember correctly.

How did you get 18.2.4? I check on website and it shows that as most current version, but when I try to update my TazerDT, 18.2.3 is the only option it gives for newest version. And the download link on website says it can only be downloaded through ZPU direct.

 

[barrak]

How did you get 18.2.4? I check on website and it shows that as most current version, but when I try to update my TazerDT, 18.2.3 is the only option it gives for newest version. And the download link on website says it can only be downloaded through ZPU direct.

I just downloaded and ran the ZPU, connected the Tazer to my laptop and hit the update button and the latest two versions were there to choose from.

So I guess, yeah... ZPU direct.

 

[HSKR R/T]

I just downloaded and ran the ZPU, connected the Tazer to my laptop and hit the update button and the latest two versions were there to choose from.

So I guess, yeah... ZPU direct.

Wonder if I need a newer version of the update utility on my laptop.

 

[barrak]

Any one having PIN Lock related issues caused by an active Start/Stop feature in their HEMI eTorque 1500 RAM?

Here's what happened twice today with my 2023 Longhorn (Long Post):

First incident:
---------------
Happened this morning after I installed the Tazer DT, set a PIN code, tested it, then drove a few miles for an errand. All was well until I reached a red traffic light where the Start/Stop turned off the engine. Once the green light came on, I pushed the accelerator and the vehicle moved forward until I was in the middle of the intersection where it entered some kind of limb mode... wouldn't accelerate and the dash prompted me for the PIN and engine light came on with error messages involving electronic throttle control and trailer brakes!!

I moved over and slowed down to park safely. Once the vehicle was slow enough, the ABS locked the vehicle. The transmission rotary selector held firm on D and wouldn't turn. I checked and found a DTC P2166 code was thrown, along with a DTC C10D0, relating to throttle position sensor and electronic brake control, respectively. I turned off the vehicle then back on and entered the PIN code and fiddled about a bit, including disabling the Start/Stop button. Vehicle drove normally afterwards to my destination and then back home, except engine light remained on.

Upon arrival at my destination, I cleared the DTC codes and did a Full Reboot + two Sleep cycles. Engine light didn't go away. Upon arrival back home I did the same again and still engine light remained on. An hour later I started the vehicle and engine light did not come on. Did a multi-stop errand before going back home and all was well throughout.

I would note an important detail: Tazer DT maintained the disabled setting of the Start/Stop button.

Second Incident:
-------------------
Earlier this evening I decided to test the Killbyfob feature using both key fobs, as mentioned in Post #1,265 above. Started the vehicle with the same key fob I've been using so far, entered the PIN, turned the engine off, then locked the vehicle using the key fob's button. I then unlocked the vehicle with the second key fob's button. Once I started the vehicle with the other key fob, I was queried for the PIN which I entered, and then the same error messages appeared and the engine light came on again. Looking down, I noticed the Start/Stop button was not disabled! I'm guessing Tazer DT linked the preserved Start/Stop status to the first key fob that was in use at the time of the initial setting.

I'm done for the evening and will look into erasing DTCs and Full Reboots in the morning. I did email z Automotive after the first incident but don't except to hear from them before Monday.

Until then, any advice or shared experiences will be appreciated.

Follow-up:

Did not hear from z Automotive since my late Friday inquiry.

Left the vehicle parked over the weekend.

Yesterday, I did one Reboot-Sleep-Sleep cycle without driving. Error messages (Service AWD, Shifter position, ...etc) and engine light were still present before the Reboot and I did not check afterwards. Decided not to poke the Beast till the following day. This time around, I did leave the vehicle with the key fob on me for a couple of minutes for each sleep interval. I also refrained this time from reviving the vehicle after it went to sleep automatically after the Full Reboot countdown. Previously, I would turn the ignition on then off to start the first Sleep event.

This morning, took the vehicle for a 20 minute drive. Error messages did not show up but engine light remained on solid.
This afternoon, started the vehicle for an errand... engine light did not come on then nor since.

Did not need to unmarry or disconnect the Tazer. I'm guessing the Full Reboot finally did the trick and the drive cycle erased the DTCs automatically.

Reminder: my vehicle is a 2023 1500 Longhorn 5.7 HEMI and the Tazer DT was purchased last week and updated to version 18.2.4 before the vehicle install.

 

[Legal Brief]

I’d guess you didn’t do the Mary and reboot cycle just right, it’s very specific. Then after time it either unmarried or stored the code. You can clear and read codes within the DT

 

[barrak]

I’d guess you didn’t do the Mary and reboot cycle just right, it’s very specific. Then after time it either unmarried or stored the code. You can clear and read codes within the DT

I probably did not perform the Reboot cycle properly as you said.

However, the whole thing started when the auto start/stop turned off my RAM at a prolonged traffic light stop, and when I moved again, the vehicle behaved as if it went into a Hijack mode.

The good news is, a properly executed Reboot cycle seems to remedy the issue, provided it is followed by a 20-minute drive including 50+ mph speed.

For the record, z Automotive responded yesterday to my Friday email. I don't want to quote them verbatim since I didn't get their permission, but here's the summary:

1. Clear PIN
2. Disconnect Tazer DT, without unmarrying it
3. Update it through the ZPU software to the latest firmware
4. Reconnect and set PIN
5. Marry the Tazer DT (Huh!!!).

That last step is odd, and might've been a mental error when it was typed. I would've expected "Perform a Full Reboot" instead.

 

[ya3coub]

Hello everyone, so I’ve updated the tazer, finally got sometime last night and did some upgrades to my truck including unlocked hp tuners PcM and the tazer dt.

Played with some settings last night starting of the marrying the tazer, to updating the tire size, drls, folding mirrors and the brake hold.

Reboted, did 2 sleep cycles.

Teated the light show and went back in happy.

Today I can confirm the tire size is finally exactly calibrated with gps and couple or radar tests, but the awkward thing after driving for about 30 min, the truck went crazy, no bus at the odometer, the car stoped responding I couldn’t even turn the engine off, then it alsot reset everything, it did it three times while I was offroading, it also at a certain point one of the resets changed the driving from 4wd auto to 2rear wheel drive !!!!

I’ve reached my destination did a complete reboot and 2 sleep cycles it was fine on the way back it just did it once, I’ve noticed that I’ve lost the tire pressure screen where it tells me the exact pressure at each tire, also the auto cruise isn’t functional.

Maybe I did something wrong, maybe it has to do with the hp smart cable or newly installed hp unlocked pcm.

“The unlocked PcM came with a small security bypass maybe that is supposed to work at the same place as the tazer !!

I’m sure it might be something I did wrong, but I’m washing the car now and thought of sharing my initial experience, maybe someone faced this before.

 

[HSKR R/T]

Hello everyone, so I’ve updated the tazer, finally got sometime last night and did some upgrades to my truck including unlocked hp tuners PcM and the tazer dt.

Played with some settings last night starting of the marrying the tazer, to updating the tire size, drls, folding mirrors and the brake hold.

Reboted, did 2 sleep cycles.

Teated the light show and went back in happy.

Today I can confirm the tire size is finally exactly calibrated with gps and couple or radar tests, but the awkward thing after driving for about 30 min, the truck went crazy, no bus at the odometer, the car stoped responding I couldn’t even turn the engine off, then it alsot reset everything, it did it three times while I was offroading, it also at a certain point one of the resets changed the driving from 4wd auto to 2rear wheel drive !!!!

I’ve reached my destination did a complete reboot and 2 sleep cycles it was fine on the way back it just did it once, I’ve noticed that I’ve lost the tire pressure screen where it tells me the exact pressure at each tire, also the auto cruise isn’t functional.

Maybe I did something wrong, maybe it has to do with the hp smart cable or newly installed hp unlocked pcm.

“The unlocked PcM came with a small security bypass maybe that is supposed to work at the same place as the tazer !!

I’m sure it might be something I did wrong, but I’m washing the car now and thought of sharing my initial experience, maybe someone faced this before.

The TazerDT acts as a security bypass. I'd lean more towards the PCM than the Tazer. Put your factory PCM back in, leave the TazerDT and see how it drives.

 

[ya3coub]

The TazerDT acts as a security bypass. I'd lean more towards the PCM than the Tazer. Put your factory PCM back in, leave the TazerDT and see how it drives.

Will do,

Thanks for the quick response

 

[HSKR R/T]

So just a follow up, with the current version and the anti-theft pedal lock enabled for keyfob(no pin) when I lock the doors it locks, then a few seconds later the horn honks. I'm assuming this is to let me know the pedal lock is enabled?

 

[barrak]

So just a follow up, with the current version and the anti-theft pedal lock enabled for keyfob(no pin) when I lock the doors it locks, then a few seconds later the horn honks. I'm assuming this is to let me know the pedal lock is enabled?

I have the following settings enabled: PIN Brakes, PIN Lights, PIN Pedal, and KillByFob.

When I lock the vehicle using the key fob, I get a honk, followed by two quick front brakes actuations, then another honk. When I unlock the vehicle using the same key fob, I hear the front brakes releasing. When I unlock it using the door handle instead, front brakes remain locked.

When I lock the vehicle using the door handle, I get only one honk and no audible front brakes locking.

So my best guess is locking with the key fob, in particular (with KillByFob enabled), preemptively triggers pedal lock (it definitely triggers front brakes lock).

The above with Firmware 18.2.4.