Janster
Well-Known Member
- First Name
- Jandy
- Joined
- Mar 27, 2024
- Threads
- 40
- Messages
- 1,884
- Reaction score
- 2,937
- Location
- Lancaster, PA
- Vehicle(s)
- 2024 Gladiator Mojave X
- Occupation
- Biller
- Thread starter
- #1
Good Morning Ya’ll…. 2024 Gladiator Mojave X with only 5,700 miles (Gasser). Our first ’inspection’ since we bought it last year in March.
Last night, I removed the Tazer completely using the appropriate Unmarry, Reboot, and 2 sleep cycles. Drove the jeep around for a few miles to confirm things were ‘good’ (aka, start stop was working). All seems as normal…..
Took it to the dealership this morning for our yearly inspection in Pennsylvania - which includes emissions.
The dealership could not perform the emissions test because they were getting an error…… **Not Ready For Testing**
They asked if we removed or disconnected the battery recently….or got any ‘codes’ (that we would’ve reset)…… Nope, none of that.
They weren’t seeing any codes or any issues either on their end this morning.
So, we did tell them we had a Tazer installed and it was removed last night.
They weren’t blaming it on the Tazer….and were puzzled why they were getting this error.
They recommended we drive it for a couple weeks (without the Tazer) and go back on March 1st in hopes something in the system would either reset or update (or whatever).
Has anyone had any issues like this ??
Is it Tazer related or is there something else going on?
*edit* WTF are these ‘drive cycles‘ I’m reading about
Thanks!
Last night, I removed the Tazer completely using the appropriate Unmarry, Reboot, and 2 sleep cycles. Drove the jeep around for a few miles to confirm things were ‘good’ (aka, start stop was working). All seems as normal…..
Took it to the dealership this morning for our yearly inspection in Pennsylvania - which includes emissions.
The dealership could not perform the emissions test because they were getting an error…… **Not Ready For Testing**
They asked if we removed or disconnected the battery recently….or got any ‘codes’ (that we would’ve reset)…… Nope, none of that.
They weren’t seeing any codes or any issues either on their end this morning.
So, we did tell them we had a Tazer installed and it was removed last night.
They weren’t blaming it on the Tazer….and were puzzled why they were getting this error.
They recommended we drive it for a couple weeks (without the Tazer) and go back on March 1st in hopes something in the system would either reset or update (or whatever).
Has anyone had any issues like this ??
Is it Tazer related or is there something else going on?
*edit* WTF are these ‘drive cycles‘ I’m reading about
Thanks!
Sponsored
Last edited: