JeepOfTheseus
Well-Known Member
This happened to me, and I'm fairly certain it was due to the cables becoming ever so slightly loose. Even if you think it's secure/snug, the only thing that has worked for me is a purpose-specific bracket that holds it in place.thank you! I’ll try these tonight. I did do this before but the jeep didn’t read the Tazer. Like I couldn’t get to the control menu via the radio. Does that make sense?
As far as updating and this error goes, yea...I ran into the same issue. This was supposedly a bug in one of their firmware versions (I think .7 or something?). I went back and forth with Tazer...and while they were helpful, I can't even tell you what the actual "fix" was. It basically just "started working": https://www.jeepgladiatorforum.com/forum/threads/tazer-mini-firmware-borked.101534/#post-1629286
I can say it was a combination of:
* Having the right cable
* Using a Windows PC (and I think there's some setting to make sure USB connections don't get restricted?)
* Using the right port (you never know...the ports on your case going to headers on the motherboard could cause issues)
It really just came down to being very patient, and sometimes letting it sit for 10-20 minutes (e.g. when writing the firmware) even if it doesn't seem like there's any activity.
tl;dr this error sucks, and I initially lost a little confidence, but Tazer was responsive and I can't imagine how equally frustrating it must be trying to own and manage firmware that gets written remotely on devices.
Sponsored