Questions & Réponses

I have a Cruze 2017 standard Key and I bought an Evo-All, followed all the steps of the guide,  the blue light flash slowly, after decryption complete, I installed the Evo-All again in the car, without pressing the programming button, when I press the lock buttom  three times the car does not start, every time I press the lock buttom the blue light comes on, but not nothing happens. The same is when i press, lock-unlock-lock.

I have a Cruze 2017 standard Key and I bought an Evo-All, followed all the steps of the guide,  the blue light flash slowly, after decryption complete, I installed the Evo-All again in the car, without pressing the programming button, when I press the lock buttom  three times the car does not start, every time I press the lock buttom the blue light comes on, but not nothing happens. The same is when i press, lock-unlock-lock.

In Late 2015 or 2016 I did an install of a Fortin EVO-ALL unit in a 2016 Fusion Push-to-Start. I believe I followed this guide when I performed that install, and it requires a minimum firmware version of 71.35. It required the yellow wire on the 20 pin connector to be connected to Ignition+ of the vehicle.

I am currently attempting to install the same (not physically the same unit, but one that was previously working, and meets the minimum hardware requirements [it is version 6] in a 2017 Fusion Push-to-Start, and the current guide listed by Fortin is this one, revised last month (April). This newer revison of the guide is listed for 2014-2017 Fusions, while the older guide was listed for 2014-2016. This guide requires ONLY firmware version 4.01, and makes no mention of connecting the yellow wire in the 20 pin connector to the vehicle for remote start, only power and CAN connections.

When connected in this manner, with the Fortin unit in programming mode (Blue LED only), turning the ignition of the vehicle on by pressing the Start button in the vehicle does not have any affect on the unit, the LED remains blue instead of flashing like it should. I verified connections a few times, and everything does appear connected as it should be according to this latest guide. I've tried reflashing the firmware on the unit a couple of times, and verifying all options, but to no effect.

The troubleshooting guide, as well as a few posts on here in regards to the light just staying blue, mention the yellow wire not being connected properly as a possible cause. So my biggest conecern/question at the moment is: Is the yellow wire supposed to be connected and was omitted in this latest revision of the installation manual? Or is my issue somewhere else? Hopefully someone here will be able to help me resolve my issue, and I would be very grateful. Thanks!

In Late 2015 or 2016 I did an install of a Fortin EVO-ALL unit in a 2016 Fusion Push-to-Start. I believe I followed this guide when I performed that install, and it requires a minimum firmware version of 71.35. It required the yellow wire on the 20 pin connector to be connected to Ignition+ of the vehicle.

I am currently attempting to install the same (not physically the same unit, but one that was previously working, and meets the minimum hardware requirements [it is version 6] in a 2017 Fusion Push-to-Start, and the current guide listed by Fortin is this one, revised last month (April). This newer revison of the guide is listed for 2014-2017 Fusions, while the older guide was listed for 2014-2016. This guide requires ONLY firmware version 4.01, and makes no mention of connecting the yellow wire in the 20 pin connector to the vehicle for remote start, only power and CAN connections.

When connected in this manner, with the Fortin unit in programming mode (Blue LED only), turning the ignition of the vehicle on by pressing the Start button in the vehicle does not have any affect on the unit, the LED remains blue instead of flashing like it should. I verified connections a few times, and everything does appear connected as it should be according to this latest guide. I've tried reflashing the firmware on the unit a couple of times, and verifying all options, but to no effect.

The troubleshooting guide, as well as a few posts on here in regards to the light just staying blue, mention the yellow wire not being connected properly as a possible cause. So my biggest conecern/question at the moment is: Is the yellow wire supposed to be connected and was omitted in this latest revision of the installation manual? Or is my issue somewhere else? Hopefully someone here will be able to help me resolve my issue, and I would be very grateful. Thanks!

I just installed the EVO-NIST1 standalone with the Fortin RF642W RF Kit on a 2008 Infiniti G35x according to Guide 24031 and have a couple comments & questions after playing around with it:

1) LOCK x3 works with the OEM fob, however it cannot remote stop the car with LOCK x3 again. This is known, so it is not a problem.

2) After remote starting the car and unlocking it (either with door button or with either of the fobs), I can open the door, step on the brake, and I am able drive away. That works as intended, but the problem is I can drive away without having the OEM key fob around. The instrument cluster screen does not say NO KEY like it normally would if the key has left the car. In other words, one would be able to drive off without having any remote on them as long as the car gets remote started followed by an UNLOCK signal. Are remote starts intended to bypass the need to have the OEM Intelligent keyfob for the take-over?

3) While the engine is off, the LOCK signal from either the RF fob or OEM fob will lock the doors and prompt the RF antenna's LED to start flashing (blue) and will not stop unless I press the UNLOCK botton on either remote. What is this flashing for? Can this be disabled? I do not need or want any alarms or extra security features. I am more concerned about it draining the car battery. Please advise.

4) After remote starting, the first press of UNLOCK with the RF fob ONLY turns off the Antenna's flashing. I have to press unlock a second time to unlock the car, however it would unlock all four doors at once. I had configured it through Flash Link (B1 on) to unlock driver door on first press, and lock all on second press but that isn't the case. What exactly happens on the first UNLOCK that stops the antenna's LED flashes? Can I get the unlock button to unlock the doors on first press?

5) How does IDLE mode pertain to push-to-starts where the key does not need to be in the ignition? I'm guessing it is not needed but just want to be sure.

6) I had to use the RL2 connector to get remote starter to work, although the guide says RL1 for G35. This might be the issue with folks who cannot get their '07 - '08's  to remote start.

Hello there 

After properly installing the EVO-ALL standalone remote starter on a RAV4 Hybrid (2016, PTS) I have recently noticed that the cabin dome lights are not being lit when any door is opened. I have checked the fuses (OK), and the lights themselves are working just fine when toggled on/off manually for both front/rear in the cabin.

What do you recommend that should be done to the EVO-ALL installation for the dome lights to function again for this vehicle without removing the remote starter of course?

The days are getting darker up north and the dome lights become indispensable as we progress into winter.

Thanks!