<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Questions &amp; Answers - Recent questions tagged sleep</title>
<link>/en/qa/tag/sleep</link>
<description>Powered by Question2Answer</description>
<item>
<title>VW Touareg EVO-ALL Not Communicating Fully after a few minutes of Vehicle S/D</title>
<link>/en/qa/68662/vw-touareg-evo-all-not-communicating-fully-after-a-few-minutes-of-vehicle-s-d</link>
<description>EVO-ALL with Firmware VW 75.18. &amp;nbsp;Compustar CM7000AS with Pro T11 Remote on a 2013 VW Toaureg TDI Push to Start. &amp;nbsp;Linked to black data port on the CM7000AS and EVO-ALL programmed with F2 Datalink protocol.&lt;br /&gt;
&lt;br /&gt;
Installation went well and the EVO-ALL was programmed successfully. &amp;nbsp;The vehicle remote starts fine and all functions appear to be working. &amp;nbsp;However, after the vehicle has turned off and the vehicle is locked, there are issues after a few minutes as if the EVO-ALL isn&amp;#039;t communicating with the canbus. &amp;nbsp;An unlock button press on the Pro T11 fob will disarm the CM7000AS, but the vehicle doors will not unlock. &amp;nbsp;Same issue with the trunk open command from the Pro T11. &amp;nbsp;The vehicle / EVO-ALL will still respond to lock and remote start commands fine. &amp;nbsp;For example, an unlock command from the Pro T11 will not unlock the doors, however, a lock command will trigger the vehicle confirmation lights, activate the door locks, and sound the factory audible chirp.&lt;br /&gt;
&lt;br /&gt;
This only happens when the vehicle has been turned off and has sat for a few minutes. &amp;nbsp;Immediately after turning the vehicle off, the EVO-ALL responds to all commands from the Pro T11 just fine.&lt;br /&gt;
&lt;br /&gt;
In addition, to rule out a potential low voltage issue, I put a battery charger on the vehicle and performed the same steps with a constant 12.3V being fed to the system. &amp;nbsp;The vehicle still didn&amp;#039;t unlock the doors after a few minutes of sitting idle.&lt;br /&gt;
&lt;br /&gt;
I have tried firmware versions 75.17 (beta), 75.18, along with the one right before 75.17 - I think it was 75.14 but I didn&amp;#039;t write it down. &amp;nbsp;All exhibiting the same issues.&lt;br /&gt;
&lt;br /&gt;
Options enabled on the Evo All: Bypass Mode - A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, C1, D6, F2, G1, G2&lt;br /&gt;
&lt;br /&gt;
Another potential bug in the firmware is the OEM Remote Monitoring. &amp;nbsp;If a user locks the vehicle with the Pro T11 and within a few seconds opens the door (handle sensor) with the OEM proximity key in pocket, no deactivation signal is communicated to the CM7000AS and the brains thinks it&amp;#039;s theft. &amp;nbsp;Might be a small bug in the firmware but I have come across this before when locking the vehicle and grabbing the door to open it as something was left inside. &amp;nbsp;Again, this issue only occurs within a few seconds of lock / arming the system with the Pro T11 remote. &amp;nbsp;If after ~5 seconds the customer opens the door, the system disarms just fine.&lt;br /&gt;
&lt;br /&gt;
I was also expecting the vehicles lights and OEM horn to be activated during a theft output from the CM7000AS (figured G1 / G2 options would enable lights &amp;amp; horn output over the canbus). &amp;nbsp;Isn&amp;#039;t the EVO-ALL supposed to be activating the lights / alarm? &amp;nbsp;No big deal if it doesn&amp;#039;t have that functionality as I&amp;#039;ll wire it from the CM7000AS instead, but I would like to know if it&amp;#039;s a firmware issue or a limation of the EVO-ALL.&lt;br /&gt;
&lt;br /&gt;
Thanks</description>
<category>Volkswagen</category>
<guid isPermaLink="true">/en/qa/68662/vw-touareg-evo-all-not-communicating-fully-after-a-few-minutes-of-vehicle-s-d</guid>
<pubDate>Sat, 06 Feb 2016 01:36:36 +0000</pubDate>
</item>
</channel>
</rss>