Factory alarm soonds after remote starting by RF KIT

Question

Installed evo-chr4 into 2010 Chrysler 300, standalone with 3x lock works perfect every time. When adding Autoconnect ACS200 commander as an Rf Kit to it, the factory alarm goes off after sitting a few minutes tand starting via cell phone app. The door locks do not unlock before starting as they do when 3x lock starting with factory fob. Verified that autoconnect is set to “protocol 2 fortin” In installer settings and have reversed the blue and white data wires. Tried following program procedures again, programmed ok, still won’t unlock before start With autoconnect but will work normally with 3 x lock. Thanks, mike.

Answer 1

that's kind of odd issue honestly.

I see D2 on so no matter how it's started the car should disarm .

 

Does it disarm properly if you trigger start by grounding the yellow/black wire?

Comments

Worked with Autoconnect tech support and determined some sort of protocol change on the Fortin side that AutoConnect wasn`t aware of. Had to install a remote start module in between evo-all and autoconnect to unlock before and lock after start. The autoconnect app would say wierd things like `alarm sounding` even though that isn`t supposed to be on there, even when the actual horn and lights were not flashing.