Evo-all and Santa FE

Question

On a couple occasions now i have used an Evo-all on a santa fe only to have it fail during programming (2 red flashes) is there a reason why the evo wont program? or a way to tell if it's incompatible? on both occasions i used a competitors module and it programed fine.

Answer 1

What year Santa Fe and what firmware did you use ?

 

2 red flashes doesn't mean anything we need more details

Comments

ok, so this morning i had a 2007 veracruz that did the same thing upon key programming, i called tech support and was told to use 4.18 and it worked, a few questions:

why will 4.18 work when 76.xx wont?

when using 4.18 should it always attempt to still learn can? (this one did)

if using 4.18 what data protocol is it using (i'm guessing the fortin protocol)?

---

Does anyone have any insight? sorry for the long thread, this is my first year using fortin and i just want to become as familiar with the product as i can

---

why will 4.18 work when 76.xx wont?

A change in the firmware to make one vehicle functional may cause an older vehicle to become unfunctional. We cannot know this, especially on older vehicles, until someone calls us so that we can open a bug report.

when using 4.18 should it always attempt to still learn can? (this one did)

4.18 has a whole bunch of compatible vehicles up to 2012ish. After 4.18 we split the firmwares up depending on the makes; 70.XX is GM, 76.XX is Hyundai, 79.XX is Lexus/Toyota etc.... These updates include new vehicle compatibilities (new cars), and also a lot more options such as selecting different datalink protocols.

 

if using 4.18 what data protocol is it using (i'm guessing the fortin protocol)?

This one is tricky! Check on the sticker on the back. Tecnically, yes, 4.18 is Fortin protocol ONLY. We have modules that some distributors asked for the 4.18 firmware but in different protocols. So on the sticker it would actually say  4.19 AP-OFA Datalink; i believe the same goes for the D2D protocol, it would actually 0.61 D2D. Once you update the firmware on these modules, the protocol switches back to Fortin but since it's updated, you can just go in the options and enable the appropriate option.

 

As for this Vercruz (and any vehicle). If the recommended firmware does not work, update to the latest BETA. If even with the BETA nothing seems to program, double check connections then call tech support.  The master reset mentionned in the above comments can also be a life saver when switching firmwares after failed attemptts at programming.

FYI, for these older hyundais you have been doing, you don't even really need to update the EVO-ALL unless you want to change the datalink protocol.

---

I use compustar and viper/autostart so i usually change it to ap-ofa or d2d, im guessing after the unit is programmed in 4.18 i can then update the firmware to change options on data protocol?

---

Correct, if you want to change the datalink protocol, you would need to update the unit since 4.18 does not have the options to change it.