Print Page | Close Window

2011 audi a4 sedan remote start dies

Printed From: the12volt.com
Forum Name: Car Security and Convenience
Forum Discription: Car Alarms, Keyless Entries, Remote Starters, Immobilizer Bypasses, Sensors, Door Locks, Window Modules, Heated Mirrors, Heated Seats, etc.
URL: https://www.the12volt.com/installbay/forum_posts.asp?tid=128220
Printed Date: May 16, 2024 at 1:55 AM


Topic: 2011 audi a4 sedan remote start dies

Posted By: masterodisaster
Subject: 2011 audi a4 sedan remote start dies
Date Posted: August 11, 2011 at 11:30 PM

I installed a Viper 5901 (Alarm/keyless/remote start) using the Flash Logic FLCAN for the bypass and locks/hood/etc. Everything works except...

The car shuts down when I hit the brake after inserting the key into it's slot. And I'm NOT pushing in on the key...

The full sequence is:
After the car has been locked/armed (then and only then) you remote start, unlock/disarm, then open and close door, then insert key (all has to happen within 45 seconds) - when you hit the brake the car dies, or if you push the key in to activate it's "start" function the car dies.

It is like I have to shut the remote start down FIRST (the car keeps running if I manually shut the remote start down via the remote with the key in it's slot). I called tech support and he told me about putting diodes on the status wire output of the alarm (one to activate the "key loop", and one to the FLCAN module), but that didn't change anything. Another concern is the fact that the "pit stop", and "turbo-timer" modes won't work because in order to get the key out of the slot you have to push in on the key first, which immediately kills the car (I told him I didn't think those functions would EVER be possible).

HELP!??!?

-------------



Replies:

Posted By: masterodisaster
Date Posted: August 11, 2011 at 11:52 PM
Wiring Diagram:

https://www.mediafire.com/?osvcb7mj29swb1c

-------------




Posted By: masterodisaster
Date Posted: August 12, 2011 at 11:37 PM
Found out the starter wires MUST be isolated - that was causing my problem. Took 7 tech support calls to find that out though...

-------------





Print Page | Close Window