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

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

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

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