Questions & Answers

Which protocol and connections to use

+3 votes

Hey Nick, Just want to clarify.  I primarily use Autostart remote starters (ex: as-1780) with and EVO-ALL.  Lately I have been having similar issues on installations where certain things will not work. I have always used the "BLACK" D2D (ADS/FORTIN) connection on the back of the autostart and left the bypass option (mode 4, func 4, opt 2) on "Xpresskit 2 way D2D" as instructed by tech support, recently It was shown to me that I should be using the "RED D2D" (Xpresskit), so i have been using it this way.  Now, should I be trying "Fortin 1 way D2D" protocol on the Autostart? (mode4, func 4, opt 3) Thanks, Mike.

asked Nov 17, 2015 in FAQ by Micheal Unger (2,680 points)

1 Answer

+1 vote

With Autostart or any DEI product, use the D2D option in the EVO-ALL (option F3) and leave the remote starter in Expresskit datalink.

 

The autostart will only allow 1-way datalink for both Fortin and ADS datalink protocols. You can use this protocol, but the bypass would not be able to "talk" to the remote starter. Meaning no statuses such as brake and tach would work through datalink and would need to be wired (although brake usually needs to wired anyway even if using the D2D protocol).

 

Either the "Black" (ADS/Fortin) or "Red" (D2D/Expresskit) can be used.

answered Nov 17, 2015 by Robert T (301,890 points)
Ok, thank you for clarifying this for me.  With the INT-SL bypass, I have found that only the fortin protocol seems to work, is this an exception?

Good point.

The INT-SL can only function in Fortin datalink protocol. So the remote starter needs to have the option for Fortin datalink or you would need to hardwire.

The EVO-ALL and EVO-KEY are the only modules we have options to change the datalink protocols (although datalink is really not required for the EVO-KEY).

...