<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Questions &amp; Answers - Recent questions tagged evo-all-d2d-datalink-protocol</title>
<link>/en/qa/tag/evo-all-d2d-datalink-protocol</link>
<description>Powered by Question2Answer</description>
<item>
<title>Which protocol and connections to use</title>
<link>/en/qa/64203/which-protocol-and-connections-to-use</link>
<description>

&lt;p&gt;
	&lt;span style=&quot;color: rgb(41, 41, 41); font-family: Fortin, Arial, Helvetica, sans-serif; font-size: 13px; line-height: 14px; -webkit-text-size-adjust: auto; background-color: rgb(230, 255, 233);&quot;&gt;Hey Nick, Just want to clarify. &amp;nbsp;I primarily use Autostart remote starters (ex: as-1780) with and EVO-ALL. &amp;nbsp;Lately I have been having similar issues on installations where certain things will not work. I have always used the &quot;BLACK&quot; D2D (ADS/FORTIN) connection on the back of the autostart and left the bypass option (mode 4, func 4, opt 2) on &quot;Xpresskit 2 way D2D&quot; as instructed by tech support, recently It was shown to me that I should be using the &quot;RED D2D&quot; (Xpresskit), so i have been using it this way. &amp;nbsp;Now, should I be trying &quot;Fortin 1 way D2D&quot; protocol on the Autostart? (mode4, func 4, opt 3) Thanks, Mike.&lt;/span&gt;&lt;/p&gt;</description>
<category>FAQ</category>
<guid isPermaLink="true">/en/qa/64203/which-protocol-and-connections-to-use</guid>
<pubDate>Tue, 17 Nov 2015 11:33:11 +0000</pubDate>
</item>
</channel>
</rss>