Français
My account Register
Français
EVO-START Wirecolor

Your Cart

Your shopping cart is empty.

Your shopping cart is empty.

Continue Shopping

ESTIMATED TOTAL:

Checkout

QUICK VEHICLE FINDER

VEHICLE FINDER

Questions & Answers

Browse among the most frequent and popular questions and find accurate answers.

recent questions tagged: ...

Clear All
Collapse All
Expand All
Clear All
Collapse All
Expand All
picto contact

Looking of our top participants?

See users
picto contact

Couldn’t find what you were looking for?

Ask us a question
RÉCENT HOT! MOST VOTES MOST ANSWERS MOST VIEWS

06/02/2016

 Volkswagen Mitchell Cardno (130Pts.)

0

VW Touareg EVO-ALL Not Communicating Fully after a few minutes of Vehicle S/D

EVO-ALL with Firmware VW 75.18. Compustar CM7000AS with Pro T11 Remote on a 2013 VW Toaureg TDI Push to Start. Linked to black data port on the CM7000AS and EVO-ALL programmed with F2 Datalink protocol. Installation went well and the EVO-ALL was programmed successfully. The vehicle remote starts fine and all functions appear to be working. 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't communicating with the canbus. An unlock button press on the Pro T11 fob will disarm the CM7000AS, but the vehicle doors will not unlock. Same issue with the trunk open command from the Pro T11. The vehicle / EVO-ALL will still respond to lock and remote start commands fine. 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. This only happens when the vehicle has been turned off and has sat for a few minutes. Immediately after turning the vehicle off, the EVO-ALL responds to all commands from the Pro T11 just fine. 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. The vehicle still didn't unlock the doors after a few minutes of sitting idle. 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't write it down. All exhibiting the same issues. Options enabled on the Evo All: Bypass Mode - A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, C1, D6, F2, G1, G2 Another potential bug in the firmware is the OEM Remote Monitoring. 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's theft. 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. Again, this issue only occurs within a few seconds of lock / arming the system with the Pro T11 remote. If after ~5 seconds the customer opens the door, the system disarms just fine. 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 & horn output over the canbus). Isn't the EVO-ALL supposed to be activating the lights / alarm? No big deal if it doesn't have that functionality as I'll wire it from the CM7000AS instead, but I would like to know if it's a firmware issue or a limation of the EVO-ALL. Thanks
Login to reply View 3 answer(s)

06/02/2016

 Volkswagen Mitchell Cardno (130Pts.)

0

VW Touareg EVO-ALL Not Communicating Fully after a few minutes of Vehicle S/D

EVO-ALL with Firmware VW 75.18. Compustar CM7000AS with Pro T11 Remote on a 2013 VW Toaureg TDI Push to Start. Linked to black data port on the CM7000AS and EVO-ALL programmed with F2 Datalink protocol. Installation went well and the EVO-ALL was programmed successfully. The vehicle remote starts fine and all functions appear to be working. 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't communicating with the canbus. An unlock button press on the Pro T11 fob will disarm the CM7000AS, but the vehicle doors will not unlock. Same issue with the trunk open command from the Pro T11. The vehicle / EVO-ALL will still respond to lock and remote start commands fine. 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. This only happens when the vehicle has been turned off and has sat for a few minutes. Immediately after turning the vehicle off, the EVO-ALL responds to all commands from the Pro T11 just fine. 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. The vehicle still didn't unlock the doors after a few minutes of sitting idle. 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't write it down. All exhibiting the same issues. Options enabled on the Evo All: Bypass Mode - A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, C1, D6, F2, G1, G2 Another potential bug in the firmware is the OEM Remote Monitoring. 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's theft. 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. Again, this issue only occurs within a few seconds of lock / arming the system with the Pro T11 remote. If after ~5 seconds the customer opens the door, the system disarms just fine. 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 & horn output over the canbus). Isn't the EVO-ALL supposed to be activating the lights / alarm? No big deal if it doesn't have that functionality as I'll wire it from the CM7000AS instead, but I would like to know if it's a firmware issue or a limation of the EVO-ALL. Thanks
Login to reply View 3 answer(s)

06/02/2016

 Volkswagen Mitchell Cardno (130Pts.)

0

VW Touareg EVO-ALL Not Communicating Fully after a few minutes of Vehicle S/D

EVO-ALL with Firmware VW 75.18. Compustar CM7000AS with Pro T11 Remote on a 2013 VW Toaureg TDI Push to Start. Linked to black data port on the CM7000AS and EVO-ALL programmed with F2 Datalink protocol. Installation went well and the EVO-ALL was programmed successfully. The vehicle remote starts fine and all functions appear to be working. 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't communicating with the canbus. An unlock button press on the Pro T11 fob will disarm the CM7000AS, but the vehicle doors will not unlock. Same issue with the trunk open command from the Pro T11. The vehicle / EVO-ALL will still respond to lock and remote start commands fine. 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. This only happens when the vehicle has been turned off and has sat for a few minutes. Immediately after turning the vehicle off, the EVO-ALL responds to all commands from the Pro T11 just fine. 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. The vehicle still didn't unlock the doors after a few minutes of sitting idle. 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't write it down. All exhibiting the same issues. Options enabled on the Evo All: Bypass Mode - A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, C1, D6, F2, G1, G2 Another potential bug in the firmware is the OEM Remote Monitoring. 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's theft. 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. Again, this issue only occurs within a few seconds of lock / arming the system with the Pro T11 remote. If after ~5 seconds the customer opens the door, the system disarms just fine. 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 & horn output over the canbus). Isn't the EVO-ALL supposed to be activating the lights / alarm? No big deal if it doesn't have that functionality as I'll wire it from the CM7000AS instead, but I would like to know if it's a firmware issue or a limation of the EVO-ALL. Thanks
Login to reply View 3 answer(s)

This website uses cookies to ensure you get the best user experience. By continuing to browse our site, you are agreeing to our use of cookies. Learn More Continue