<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Questions &amp; Answers - Questions récentes tagguées rogue-select</title>
<link>/en/qa/tag/rogue-select</link>
<description>Powered by Question2Answer</description>
<item>
<title>EVO One and MyCar LinkrLT successfully start then immediately stop</title>
<link>/en/qa/90783/evo-one-and-mycar-linkrlt-successfully-start-then-immediately-stop</link>
<description>Hi, all. I installed a Fortin EVO One about a year ago in my 2015 Nissan Rogue Select, with the applicable t-harness kit. Just to give a bit of background, I ordered my Evo pre-programmed from a reputable seller on eBay along with a DroneMobile. The Drone device was always buggy and unreliable, so I replaced it not long after with the RF642W remotes and a MyCar (Yes, I did buy the flashlink and reprogram the EVO one). When I originally installed them I was unaware I needed a diode for them both to work, so I just got around to doing that recently.&lt;br /&gt;
&lt;br /&gt;
My remotes have worked flawlessly from the get go, I just installed the diode today and the MyCar now paritally works. It can lock and unlock the doors, and when I send a remote start command the vehicle will lock and start, however it shuts off in about 5 seconds or less. The remotes however still work flawlessly, which perplexes me a bit. From what I&amp;#039;ve seen this normally indicates the remote start doesn&amp;#039;t have proper engine RPM data, but I&amp;#039;m curious as to why the remotes would work normally and the MyCar doesn&amp;#039;t</description>
<category>Nissan</category>
<guid isPermaLink="true">/en/qa/90783/evo-one-and-mycar-linkrlt-successfully-start-then-immediately-stop</guid>
<pubDate>Sun, 20 Oct 2019 15:52:45 +0000</pubDate>
</item>
</channel>
</rss>