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

EVO-ALL or EVO-ONE

I am preparing to do a remote start installation on a 2018 Infiniti Q60 (3.0L). The remote start module (with T-Harness) will be paired with the RFK-942 RF kit. I've installed the EVO-ALL on a 2016 Q50 and a 2017 Q60 (both 3.0L, both with T-Harness and both with RFK-942) and they are functioning well. My question to you is what would be the benefit of choosing the EVO-ONE over the EVO-ALL? For example, would I gain any additional functions (such as, trunk release via RFK-942 remote, parking lights control, etc.) if I went with the EVO-ONE instead of the EVO-ALL?

0

G37/Q60 did not start once recently, sometimes takes long time to initialize

I have a 2014 Q60 (G37 coupe) that I installed a Fortin EVO-ALL and NIST1 harness into. Using OEM fobs 3x to remote start. Has been installed for over a month. Install went well, but from beginning there was one persistent problem: when remote starting, 25% of time car remote starts right away as expected, 75% of the time seems to be delayed, vehicle lights come on, go off, come back on again and after 15 seconds or so the car would finally start. Seems to be a firmware issue, as others on the help forum have mentioned it is a common issue with no solution. But, today the car failed to start. 42f/5c temperature outside, running lights and brake lights flashing strangely, did that twice and did NOT start. Car seemed to go dark, so I did 3x lock again and car did start. Why does the car sometimes not start? I have lots of experience installing remote starters, and this one was the easiest, most well thought out system I have ever installed, there seems to be almost no room for install error with the NIST1 harness, so I can only surmise this is a firmware issue. Please help solve the persistent starting delays and this new no start condition.

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