Average Oregonian
Well-Known Member
- Thread starter
- #1
TL;DR OEMs causing hyperflash for front turn signals. Tazer fixes it, JScan doesn't. What do I do?
SIA for the long thread and TIA for any help you can provide.
Background: I have an OEM halogen truck that has been converted to full OEM LED, including front turn signals / DRLs. Many Gladiator owners have reported that they have an unfixable hyperflash with this setup despite the dealership adding the appropriate sales codes. It has become a big issue in a few cases where the dealership promised an LED upgrade as a part of the vehicle sale and then encountered this issue without resolution. I am included in this group, as I have had the sales codes added but still experience the hyperflash and turn signal out errors. This problem IS addressed with a Tazer, however, and they do work fine with the Tazer fix installed, so that was my initial solution:
I'd like to move these types of changes over to JScan to make them more permanent and get rid of the need to unmarry the Tazer prior to dealership service. The LED setting for the lights themselves is already set by the sales code that was added. I've tried to enable the same hyperflash solution with JScan (and with the Tazer unmarried but acting as my SGW bypass), by setting the Front Turn Lamp Diagnostics to Deactived (as it is when the Tazer is married), but the hyperflash errors are back after using each signal for a bit. I've tried a full reboot and 5 minute sleep cycles, but no change.
How scan I fix this with JScan? What is the Tazer doing differently to bypass this? Out of all of the things that are easily upgraded and programmed on a Jeep, the front turn signals weren't the ones I expected to be a hassle :D
SIA for the long thread and TIA for any help you can provide.
Background: I have an OEM halogen truck that has been converted to full OEM LED, including front turn signals / DRLs. Many Gladiator owners have reported that they have an unfixable hyperflash with this setup despite the dealership adding the appropriate sales codes. It has become a big issue in a few cases where the dealership promised an LED upgrade as a part of the vehicle sale and then encountered this issue without resolution. I am included in this group, as I have had the sales codes added but still experience the hyperflash and turn signal out errors. This problem IS addressed with a Tazer, however, and they do work fine with the Tazer fix installed, so that was my initial solution:
I'd like to move these types of changes over to JScan to make them more permanent and get rid of the need to unmarry the Tazer prior to dealership service. The LED setting for the lights themselves is already set by the sales code that was added. I've tried to enable the same hyperflash solution with JScan (and with the Tazer unmarried but acting as my SGW bypass), by setting the Front Turn Lamp Diagnostics to Deactived (as it is when the Tazer is married), but the hyperflash errors are back after using each signal for a bit. I've tried a full reboot and 5 minute sleep cycles, but no change.
How scan I fix this with JScan? What is the Tazer doing differently to bypass this? Out of all of the things that are easily upgraded and programmed on a Jeep, the front turn signals weren't the ones I expected to be a hassle :D
Sponsored