can bus programming on 2012 ford fusion

Question

Hello,

I am installing an EVO-ALL in a 2012 ford fusion and using it as the standalone remote starter.   When I go through the first section of the programming I hold the button until the blue light is lit and turn the key on.  Everything looks good and the blue light starts flashing.  then after a couple of seconds the blue light goes out and the yellow light turns on.   At this point I try to do the remote start with the key in the ignition and it appears it is trying (dash lights come on, etc), but the car never tries to start.

Any advise of things to try?   I have the module programmed with the current recommended firmware for the 2012 ford fusion, and I have also tried the beta firmware as well as an older firmware and still get the same results..

Thanks,

  Chris

Answer 1

Hi Chris,

 

For firmwares, you do need the latest Ford 71.[xx].

The blue LED programming and test is only there to confirm proper connections when using a remote starter.
I believe though, that the key should also be upside down in front of the barrel, not in the barrel for that test.

 
I'd recommend skipping straight to the next section of programming once you get the first part done.

Comments

I ended up having to back-rev the firmware to 71.02 to get it to recognice the CAN bus.   I was also not able to program the bypass using 2 keys, so I had to use the decryptor.   After doing these 2 things, the remote start worked as expected.

---

DCrytor with Ford and Mazda is your honest best bet for key programming. Both those makes can be a pain do get a bypass to learn effectively to the vehicle. DCryptor will clone whatever key you used in the programming procedure.

After doing these 2 things, the remote start worked as expected

Excellent!

I ended up having to back-rev the firmware to 71.02 to get it to recognice the CAN bus.

If you still have the service number written on the back of the EVO i'd be able to open up a bug report for engineering so that you don't fall into the same situation again with newer firmwares.