Your Cart

Your shopping cart is empty.

Your shopping cart is empty.

Continue Shopping

QUICK VEHICLE FINDER

VEHICLE FINDER

Questions & Answers

Browse among the most frequent and popular questions and find accurate answers.

recent questions tagged: ...

picto contact

Looking of our top participants?

See users
picto contact

Couldn’t find what you were looking for?

Ask us a question

0

2017 Golf Alltrack PTS no start

2017 VW Golf Alltrack PTS A/T Installed EVO-VWT1 with r-link stand alone, programed unit to lock-unlock-lock and vehicle started without any problems 4 times. Decided to change the setting to 3x lock start and and turned on reset protection for EVO-ALL, but after pluging evo back vehicle does not start, no blue,yellow or red led flashing when i lock or unlock the doors. Unit recieves power as i tested with programing step one (hold button while pluging 4pin) and all leds alternate. Decided to ask if anyone had same issue before i try master reset.

0

2010 Dodge Caravan No Start Next Day

EVO RS installed in 2010 Dodge Caravan with the CHRT4. I installed last night, seemed to work fine. But noticed when the vehicle was turned back on the radio clock had reset. This morning I have a no start condition. Doors won't unlock/lock with remote, key in ingition does nothing. Interior lights, head lights and brake lights work. Additionally, due to ignition problem can't shift into neurtal to move vehicle. Also could not get the horn to silence as per the Dodge Manual after RS installed

0

EVO-One initially functions, however after a period of time no longer responds to remote operation.

After installing and properly programming my Evo one unit, in factory turn-key option, it appears to operate correctly for a short period of time. If the vehicle sits for any length of time it appears that the unit at some point deactivates and does not respond to the key pressing on the key FOB. All standard factory operations are functioning as they should, however the remote start does not. Disconnecting the car's battery does bring this back online for a period of time, however once more does revert to inoperable status. The car does not have a factory immobilizer, and from what I can determine all correct connections have been made. Thanks in advance!

0

2009 Infinity G37 OEM remote No Start

I just finished installing the EVO-NIST1 (no other components) on my 2009 Infinity G37. After hooking up the wiring harness I completed the bypass programming procedure and everything went good until I tried to start the car using my OEM remote. I pushed my OEM remote 3 times and the car did not start. Each time I pushed the lock button a blue LED light flashes on the EVO unit but nothing else happens. Do I need to order a stand alone remote? Do I need additional components? Not sure what to do here.

0

2011 Nissan Pathfinder - No Start w/o Key - Start then Killed w/ Key in Barrel

Fortin EVO-ONE w/ T-Harness. Regular (non-intel key) Summary: 1) I am trying to determine why I only get cranking & starting when the key is in the barrel 2) I suspect I'm not getting or decoding CAN data in the EVO-ONE. Details: I have installed the unit and, updated both bypass and remote start firmware via flashlink. I've also set the following options in remote start: 32.3, 2.3, 8.2. My first issue appeared when pairing the RF remote kit (RF442W). I had to manually apply +12V to the black (foot pedal brake) wire after 5 button presses in order to enter the "add remote" option. I thought brake status came over CAN bus. After issuing a remote start command, the red light on the Fortin comes on, the dash lights up, and hear relays clicking in the engine bay but no cranking. It fails after two attemps and flashes the 4x light code = no tack feedback. Same result with GWR wire grounded. If I put the key in the ignition barrel and re-attempt the test, this time the vehicle starts, but then shuts down after 3 seconds with the same no tachometer feedback error code. If I change the tachometer setting via flashlink (20.4), the vehicle will stay running. I have tried 20.1, 20.4, 20.5, 20.6 I pulled out my 2CH oscilloscope and probed the CAN pins (6 & 14). There is clearly data on the bus, though the CAN L signal has significantly higher capacitance (signal does not have hard edges like CAN H). According to the install guide, doors/trunk/brake/tach/etc should be coming into the EVO-ONE via CAN bus. I'm worried that I either have a fortin or vehicle CAN bus problem. For what it's worth, I disconnected the CAN bus wires into the EVO-ONE and got the same result. Additionally, I suspect there is another reason as to why I don't get cranking without the key in the barrel. Any additional steps or guidance appreciated.

0

2016 VW Golf Sportwagen Inconsistent starting especially with EVO-START

I Have recently installed an EVO-ALL with EVO-START into a 2016 VW Golf Sportwagen. Regular Key-start.

With factory settings A1-A11, D1, D2(factory alarm) C1 & H2(evo-start) all turned ON. The car seems to start at random with this setup it will work sometimes and then will not start on an immobilizer error. Once I get the error it will not remote start again.. but then if I manually cycle the key on/off in the ignition, get out of the car and remote start it will usually work again. 

If I wrap the key in series from the evo-all to the transponder (D4 white/green wire from evo-all module directly to key wrap and then out of key wrap to transpoder wire) and then turn OFF option A3 the car remote starts perfectly every time. but will also start manually with a NON-CHIP key. (always sending transponder key)


The key wrap has been checked and redone (just to make sure) as has all the wiring and everything is good. Firmware version is up to date as recommended. I even tried another evo all module to make sure and got the same result.


I'm really not sure what else to check at this point,  But with A3 on and white/green wired in parallel with the wrap/transponder I get very random starting results will work several times in a row and then not start on an imoblizer error the evo-start is less consistant than than 3x lock on the oem remote but both are not near consistant enough. 

 

 

Is it possible to wire this set up with a transponder ring/wrap instead of the cut transpnder wire on the car? Not sure if that would help provide more consistant results?

1

2008 Silverado WT not remote starting with EVO-GMT & RF Kit

I Installed a Fortin EVO-GMT in my 2008 Chevrolt Silverado WT. The lock/unlock function works, but attempting to start results in the dash lights and accessories turning on for several seconds, turning off momentarily, turning back on for several seconds, then the red light flashing 3 times before failing to start. (The starter does not crank). I know this unit is capable of starting the truck - I initially misprogrammed the RF (FTX-64-2W) as H1 rather than H2 - which caused the unlock to not work, and a strange combination of buttons on the remote would start the truck. After reprogramming it to H2, the symptoms above became aparent. *Kit is being used as stand-alone, truck does not have factory remote. Any help is appreciated.

0

2012 altima will not start

install all the harness and use a ttab to wire to the brown wire to the pust to start button. Did the aapropiate programing following the instructions, all lights flash accordingly. I try starting the car and it wouldn't do it. The red light turn and yellow biinks and you can hear the module clicking but the car will not start. Any advice so i can get my remote start to work properly.

0

Ford Edge will not start

Evo-all, Service #001A106 607958, hardware version 6, date 01/2016, Firmware 71.35, C1 and D1 ON. Stand Alone with T harness. 2013 Ford Edge, no hood pin or auto lift gate. Wiring installed per guide 34421. Installed all 20 pin connector wires as shown in guide including A17 and A18 with exception of A14, hand brake. I am unclear where or what the relay is, I did find a fuse relay 85 but it is empty and not used. Spoke to tech support and was told that this was not needed. During programming all goes as plan through step 8, first key second time, red and blue lights flash (did not try to count how many times so I am not sure if 10 times, but looked good). The blue light comes on and then turns off before I remove the key (thought this was the issue so I removed key faster before the blue light went out and this did not help solve the problem. 3X remote activates locks, check engine light comes on, car does not start. When I key start the car it will not turn off until I remove the data connector. This seems to get so close to working that I am sure it is a minor fix, loose connection, but I am not sure where to concentrate my fix.

0

EVO-ONE will not remote start on 2015 Nissan Armada

Using EVO-ONE bypass firmware version 72.19, t harness and RF642W 2-way remotes on 2015 Nissan Armada with Intelligent Key. Remotes will lock/unlock and communicate with vehicle, but will not remote start vehicle. Noted during key programming that module does not operate park lights, so no park light flash code to use. Module programming, key programming, and remote programming completed, but vehicle will not start with remotes. Will make two attempts to start (can tell by driver's foot light operating), but dash lights do not come on and vehicle does not start. Occasionally, vehicle alarm will sound after first attempt (of two) to start. Module programming LED will flash after failure to remote start. Does not appear to be a flash code. While attempting to start, various module LEDs will flash on and off briefly. 2 way communication works properly (remote beeps to indicate remote start failure), and lock/unlock function of remote work normally. Query of vehicle status works normally. All wiring double checked using guide #17763. Ignition diode indicated in EVO-ONE box (rev. 20150225) installed.

This website uses cookies to ensure you get the best user experience. By continuing to browse our site, you are agreeing to our use of cookies. Learn More Continue