Votre panier

Votre panier est vide.

Votre panier est vide.

Continuer le magasinage

RECHERCHE RAPIDE DE VÉHICULE

RECHERCHE VÉHICULE

Questions & Réponses

Consultez les questions les plus fréquemment posées et trouvez des réponses pratiques et pertinentes.

recent questions tagged: ...

picto contact

Vous cherchez nos meilleurs participants ?

Voir les utilisateurs
picto contact

Vous n'avez pas trouvé ce que vous cherchiez ?

Posez-nous une question

0

firmware 60.11

Hi. previosly my evo-all was running on 60.11 firmware and remote start worked. I updated to 60.12 and no remote start anymore . where can I find firmware 60.11? vehicle VW touareg 2013 standart key thanks

0

2013 Touareg no crank 3x lock Thar-AUD1/Evo all

2013 Touareg 3.0 TDI, unit programs fine however when 3x lock the vehicle dash lights up but no crank. I triple checked PIN2 of the BCM connector for the brake lights as directly across in PIN18 is the same color wire, also with a test light at the module it lights up with ign on and pressing the brake pedal. I assume its an option in the module that needs changing. Module S/N is 001A07217040 Thanks

0

2013 Touareg no crank 3x lock Thar-AUD1/Evo all

2013 Touareg 3.0 TDI, unit programs fine however when 3x lock the vehicle dash lights up but no crank. I triple checked PIN2 of the BCM connector for the brake lights as directly across in PIN18 is the same color wire, also with a test light at the module it lights up with ign on and pressing the brake pedal. I assume its an option in the module that needs changing. Module S/N is 001A07217040 Thanks

0

2013 Touareg no crank 3x lock Thar-AUD1/Evo all

2013 Touareg 3.0 TDI, unit programs fine however when 3x lock the vehicle dash lights up but no crank. I triple checked PIN2 of the BCM connector for the brake lights as directly across in PIN18 is the same color wire, also with a test light at the module it lights up with ign on and pressing the brake pedal. I assume its an option in the module that needs changing. Module S/N is 001A07217040 Thanks

1

3x Lock not always working to start 2014 VW Touareg Evo-one w/Thar-AUD1

New install on Touareg - working through a few small issues, but biggest is that the 3X lock does not allways start the vehicle - cluster doesn't light up at, parking lights and audible chirp work and confirm 3 presses getting to vehicle. Sometimes the second try works. Seems inconsistent. Is there a required speed (too fast or too slow perhaps) that might be causing the EVO-All to "miss" the command? Is there an error code guide to the LED's on the EVO-one that might help diagnose the issue? Thanks in advance, Jon

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

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

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

0

Touareg, fil de frein ne fait pas partir.

Installer comme à l'habitude E400-C avec Evo-all (001a06177384), sauf qu'il faut que j'appuie manuellement sur la pédale pour que l'auto parte. Pourtant mon fil jaune/rouge du Evo-all envoie bien le signal + sur le fil noir/rouge de l'auto et que la lumière de frein arr. allume (seulement la 3e "brake light"). C'est comme s'il fallait une autre source pour les freins. Vérifier avec le dealer et il ne voit que le fil noir/rouge avec la pédale mais j'en doute, besoin de votre avis, parler avec Anthony mais sans succès.

Ce site Web utilise des cookies pour vous garantir la meilleure expérience utilisateur. En poursuivant votre navigation sur notre site, vous acceptez notre utilisation des cookies. En savoir plus Continuer