User

I have a 2015 Subaru Legacy that I have install an EVO-ONE (002B07172969) on with the T-Harness and have an issue with the car alarming when the door is opened after unlocking it with the key fob. If I use the smart-phone module to unlock the car, no alarm sounds when the door is opened. If I disable the alarm feature (change from option 14.2 to 14.1) everything works fine. Any ideas? On another note, the troubleshooting app for android does not exist on the Google Play Store.

My EVO-ONE is hardwired into a 2001 Tacoma. I seem to be unable to send two quick unlock pulses with the RFK411 remote to unlock all doors. There has to be a slight pause between presses in order to get two unlock signals. Unfortunately, if you wait too long, you will not unlock all the doors. Consequently, it is hit or miss to get all doors unlocked. Is this a property of the remote to have this refractory period or a property of the EVO-ONE. If it is the remote kit, is there another one you recommend that does not have this refractory period. If it is a property of the EVO-ONE, can new firmware correct this or is there an older firmware that corrects this. I have tapped into the driver side key switch that will open all doors when the key is turned twice. My plan was to put a relay to control the actuator so that the first press opens the driver door and the second press opens all doors. Before I install the relay, I wanted to see if the two press unlock will work.

Is it possible to have the MyCar and the RFK441 coexist? It seems the answer is no. I can have both the MyCar and the RFK441 programmed to the EVO-ONE. And inidivually they will work and operate the EVO-ONE. But if I plug in the RFK441 into the harness of the MyCar to have both of them attached to the EVO-ONE, only the RFK441 controls the EVO-ONE. If it is possible, what steps can be taken to make this happen. Or do I need a different remote kit for this to work? Thank you. Jim

I have installed an Evo-one in a US version of a 2015 Subaru Legacy standard key with the T-Harness. The issue at hand is that the OEM keyfob will no longer open or close the locks if you delay your exit. If you exit immediately, the keyfob functions as normal. If you delay long enough that the interior lights dim to off, the keyfob will not lock or unlock the doors. The only way to make them functional is to put the key in the ignition and turn the car on and off and then immediately lock the car.

Issue: After remote start Evo-one does not lock car. Background: Installed Evo-one in a 2015 Subaru Legacy standard key. Only change from guide 57221 is that the Immobilizer wire was located in an alternate location on connector back of the fuse box as found on wirecolor.com for Subaru Legacy (2015-2017) photo 20. After 3x lock presses, unit will unlock and start car but will not lock after car is started. Pressing the lock button on the remote locks the car but Evo-one does not seem to sense it as there is no flash of blue light. This is also true when the unlock button is pressed. Car unlocks but no flash of the blue light on the Evo-one. Prior to remote starting, the Evo-one blue light flashes with every press of the lock or unlock button. Other options I have tried without success: D2 on and 6.2, D2 off and 6.2. Other things that did not work: 37.2 causes engine shut down all the time. 7.2 does nothing. No lock or unlock. I had double checked all the connections and all the taps are solder joints. Turned D2 off and car remote started with 3x lock and doors stayed locked. Can use keyfob to unlock doors. Insert key, turn to on position, step on brake and key take over successful. No apparent alarm. If I use keyfob to unlock door and step on brake, engine cuts off. So notes: 1) Prior to remote start or key start, Evo-one appears to see keyfob presses as evidence of the Evo-one blue light flashing when doors are unlocked/locked with keyfob press. 2) After remote start, Evo-one does not see keyfob presses as evidence of no blue light flashing when doors are locked/unlocked with keyfob press. 3) If car is key started, keyfob presses are not seen/ignored by the car as evidence of no lock/unlock with keyfob press and are not seen by the Evo-one as evidence by lack of blue light flases with keyfob presses. So do we need to wire it differently, get different programming, or am I just out of luck to enable other desirable features like 37.2 and 7.2.

I am wanting to use the EVO-ALL in a 2001 Toyota Tacoma as an alarm with an external RF Antenna to control the door locks and an Avital 4113 remote starter I plan to integrate with it. The vehicle does not have an alarm or remote natively with it. The Avital remote start will be hard wired to the EVO-ALL since I am using an RF kit. The question is what guide and what firmware should I use for the unit to make this is possible. Thank you.

I am planning to do an install in a 2001 Toyota Tacoma. The Evo-One with the Thar-One-Toy2 harness is what is recommended from your web site but I am unable to find a corresponding install guide. What are your recommendations.

Installed an Evo-All in a 2008 Altima as a stand alone remote start with a FT-D100 RF kit. It is programmed On for "Unlock driver door only." The issue I am having is that when you press the unlock button once, the lights blink but the driver door does not unlock. Press the button again and the lights blink and all the doors unlock.

I need but am unable to find installation help (wires, photos, guide) for Nissan Altima - Push-to-Start (2007-2008) on wirecolor.com. I can find the information for Nissan Altima - Push-to-Start (2009-2012). I think they are the same but not a hundred percent sure. Can anybody confirm that. Thanks.

When the unit was first installed, everything seem to be operating as designed. 3x lock and the car starts. No over past week or so, that car starts with one lock. So when the car is exited and the the lock button is pressed, the car locks and then remote starts.

I have an EVO-ALL installed currently in a 2005 Chrystler 300 using OEM 3X for remote start. I have a DIrected 9474T remote kit and want to use that instead of the OEM remote. Will it work and how would I connect it to the EVO-ALL. (and what programming changes for the EVO-ALL would have to be made.)

I am installing an Evo-All into a 2008 Altima and using the OEM remote as the first choice for the install. I understand from previous Q&A posts that the Evo-All can be used as a stand alone remote start in this model year but because it cannot detect the lock/unlock on the CAN BUS it will need to use a separate RF Kit or an Universal Trigger connected to the external input of the Evo-All. Also The Evo-All needs to detect the unlock pulse to allow key take over. A suggestion was to see if pin 15 on the BCM tests negative with a press of the unlock of the factory remote to connect the unlock input of the Evo-All to that. (Assuming that this pulses not only with the remote but also with a press of the door button) For the questions. If pin 37 on the BCM pulses negative with each remote lock press, could you just connect the Evo-All lock in wire to that pin to allow 3x remote start? One of the optional connections is to have the Evo-All lock out connected to pin 37 on the BCM and the unlock out to pin 15 on the BCM. Is it okay to have the Evo-All lock in and lock out connected to pin 37 and the unlock in and unlock out to pin 15 without causing problems.

When using an EVO-ALL on a 2008 Altima (push to start) with firmware 76.16, the car starts by only pushing lock once (so you can't lock the car without it starting). I can't get any other firmwares to start the car at all (not even light up when the car is locked). I tried the recommended 76.14, 76.09, 4.18, and 4.08 and nothing works. Is there a firmware that will start a 2008 Altima by pushing lock 3 times instead of once?