Questions & Answers

Evo All not recognizing request to lock or unlock from aftermarket starter

0 votes
For my 2014 Ford Fusion, looking to use the Evo All FOR3 to receive signals from a module to lock and unlock my doors. I'm using a wire to wire connection, and tested the signal at the 20 pin connector to the evo, and it's receiving the negative pulse from the aftermarket module to lock and unlock, yet nothing is happening.

When using the setup wizard on the updater, I'm advised to use firmware 4.01, and when using pro to adjust locking settings if that's necessary, I'm advised to use firmware 71.57, though I'm unable to complete the programming process with the latter firmware. The blue led does not flash rapidly when I turn the key to on, just stays solid blue. Does anyone think they'd be able to help with this?

Gracefully,
asked Jun 4 in Ford by Sebit Gatluak (130 points)

2 Answers

0 votes
Hello,

Please try the following:

- in pro mode turn off settings protection and save it in the off position

- re turn to the vehicle and perform a master reset: https://fortin.ca/en/download/61931/61931.pdf

- return to the pc and enable options A1 through A10 as well as C1.

- flash fw 4.01 into the evo

- re program the module in the vehicle per page 5: https://fortin.ca/download/96171/EVO-ALL_IG_TSA_BI_FOR3-FUSION-MKZ_2014-2017_C_96171.pdf

 

After you have programmed the module to the car, start the vehicle normally with the key 1 time and also send lock/unlock a couple times from the OEM remote.

From there test the evo for lock/unlock commands.

 

Best regards
answered Jun 4 by Derek J (395,120 points)
Thank you so so so so much! I think it's working now!

Blessings!
Glad that got it going for you!

Best regards
0 votes
Go with what the guide says.

For the Gateway installation with a FOR3, the proper firwmare is correct in wizard mode- 4.01.
71.xx is for another type of installation and since 71 > 4 , 71 is shown as default in Pro mode.

Once programmed to the car, cycle ignition once in order for the vehicle to sync with the module otherwise unlock may not work until you do.
answered Jun 4 by Robert T (310,630 points)
Thank you! I was using 4.01 when it wasn't reacting to the lock/unlock signals. I preformed the steps by Derek J, and something in there, combined with using 4.01 still, must've made it work. I greatly appreciate your guidance!

Blessings!
...