Questions & Answers

Evo-all and Santa FE

0 votes
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.
posté Nov 28, 2014 dans la catégorie Hyundai par Adam Pepin (10,150 points)

1 Réponse

+1 vote
What year Santa Fe and what firmware did you use ?

 

2 red flashes doesn't mean anything we need more details
répondu Nov 28, 2014 par Adam Pepin (85,210 points)
My apologies, The santa FE's in question were both 2008 ( i have had another 2008 work) i believe the firmware was 76.15 and i tried 76.10 - 76.16 with the same result.

Connection 13 Program 3, during programming step 1 and 2 are normal, at step 3 when i turn ignition on i get 2 red flashes per second

Use 4.18 and forget about Can-Bus. After turning ignition on, wait a bit, the red and yellow will come on, turn key off and back on (without taking the key out of the barrel), all LEDs will turn on and start the learning cycle. Wait until the yellow flashes (can take up to 5-7 minutes).

 

Only reason I am saying forget about Can-Bus is that I got a Santa Fe yesterday that the Can wire color didn't match to anything, even the Hyundai wiring chart. Can-Bus on this vehicle only does foot brake and tach anyway.

 

Dont forget to master reset the module. Probably not required but most certainly helps.

  1. Hold down programming button while plugging in datalink connector.
  2. Let go of button when LED is RED.
  3. Push and hold button again until all three LEDs start to alternate.
  4. Disconnect unit, she is now reset.
     
So is the issue with it not learning due to the can-bus or key data? And will taking the key out of the barrell affect the learning cycle?
We need the VIN when programming Can, so if the VIN's not there, it may cause programming problems.
ok, now if i take the key out after the red and yellow led come on will this cause a problem?
ya, take the key out when the red and yellow are on, then turn it back on to start the auto key learning procesure.
I'm asking if i turn the key off when the red and yellow are on then take the key out, re-insert and turn on will this cause a problem learning?
Won't cause a problem. If i remeber right, that's actually how the programming says to do it. First part we try to learn Can. Turn key off, turn back on, and unit is now trying to learn key.
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.
...