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

19/10/2016

 Volkswagen Justin Chang (690Pts.)

0

OEM remote does not work while remote started

2008 VW GTI W/ DSG Transmission. Installed EVO-ALL w/ CrimeStopper Revo 1.1 external RF kit. I am also using Flash Link Updater 2 w/ Flash Link Manager v3.61 (which I do not see anymore on the fortin website). On the Fortin website for my vehicle, it says on Installation Notes "OEM REMOTES NOW FUNCTIONAL WHILE REMOTE STARTED" but when I remote start the vehicle with my Revo 1.1, my OEM remote does not unlock the vehicle. This forces me to turn off the remote start with the Revo 1.1 key then switch over to my OEM remote and unlock. Are there specific options I have to choose in Flash Link Manager?
Login to reply View 4 answer(s)

19/10/2016

 Volkswagen Justin Chang (690Pts.)

0

OEM remote does not work while remote started

2008 VW GTI W/ DSG Transmission. Installed EVO-ALL w/ CrimeStopper Revo 1.1 external RF kit. I am also using Flash Link Updater 2 w/ Flash Link Manager v3.61 (which I do not see anymore on the fortin website). On the Fortin website for my vehicle, it says on Installation Notes "OEM REMOTES NOW FUNCTIONAL WHILE REMOTE STARTED" but when I remote start the vehicle with my Revo 1.1, my OEM remote does not unlock the vehicle. This forces me to turn off the remote start with the Revo 1.1 key then switch over to my OEM remote and unlock. Are there specific options I have to choose in Flash Link Manager?
Login to reply View 4 answer(s)

19/10/2016

 Volkswagen Justin Chang (690Pts.)

0

OEM remote does not work while remote started

2008 VW GTI W/ DSG Transmission. Installed EVO-ALL w/ CrimeStopper Revo 1.1 external RF kit. I am also using Flash Link Updater 2 w/ Flash Link Manager v3.61 (which I do not see anymore on the fortin website). On the Fortin website for my vehicle, it says on Installation Notes "OEM REMOTES NOW FUNCTIONAL WHILE REMOTE STARTED" but when I remote start the vehicle with my Revo 1.1, my OEM remote does not unlock the vehicle. This forces me to turn off the remote start with the Revo 1.1 key then switch over to my OEM remote and unlock. Are there specific options I have to choose in Flash Link Manager?
Login to reply View 4 answer(s)

19/10/2016

 Volkswagen Justin Chang (690Pts.)

0

OEM remote does not work while remote started

2008 VW GTI W/ DSG Transmission. Installed EVO-ALL w/ CrimeStopper Revo 1.1 external RF kit. I am also using Flash Link Updater 2 w/ Flash Link Manager v3.61 (which I do not see anymore on the fortin website). On the Fortin website for my vehicle, it says on Installation Notes "OEM REMOTES NOW FUNCTIONAL WHILE REMOTE STARTED" but when I remote start the vehicle with my Revo 1.1, my OEM remote does not unlock the vehicle. This forces me to turn off the remote start with the Revo 1.1 key then switch over to my OEM remote and unlock. Are there specific options I have to choose in Flash Link Manager?
Login to reply View 4 answer(s)

07/12/2021

 Volkswagen Sean (750Pts.)

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
Login to reply View 3 answer(s)

07/12/2021

 Volkswagen Sean (750Pts.)

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
Login to reply View 3 answer(s)

07/12/2021

 Volkswagen Sean (750Pts.)

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
Login to reply View 3 answer(s)

07/11/2021

 Volkswagen Jerry Martin2 (310Pts.)

0

2013 vw touareg no start except with brake pedal

sn: 002b04174651 version 60.11 first install was with thar-aud1 that didnt work ignition didnt come on and it was asking to remove key from ignition second install was wire to wire installation worked fine could program the key ect. tried remote start ignition comes on but no start at first ign on if i touch the brake it would stall soon after at second ign on (on same remote start attempt) it keeps running. verified yellow/red wire to black/red wire all seems ok. i got 12v at black/red if i touch the brake. at one time while trying car start even if yellow/red was connected. car is a diesel if that matters.
Login to reply View 3 answer(s)

07/11/2021

 Volkswagen Jerry Martin2 (310Pts.)

0

2013 vw touareg no start except with brake pedal

sn: 002b04174651 version 60.11 first install was with thar-aud1 that didnt work ignition didnt come on and it was asking to remove key from ignition second install was wire to wire installation worked fine could program the key ect. tried remote start ignition comes on but no start at first ign on if i touch the brake it would stall soon after at second ign on (on same remote start attempt) it keeps running. verified yellow/red wire to black/red wire all seems ok. i got 12v at black/red if i touch the brake. at one time while trying car start even if yellow/red was connected. car is a diesel if that matters.
Login to reply View 3 answer(s)

07/11/2021

 Volkswagen Jerry Martin2 (310Pts.)

0

2013 vw touareg no start except with brake pedal

sn: 002b04174651 version 60.11 first install was with thar-aud1 that didnt work ignition didnt come on and it was asking to remove key from ignition second install was wire to wire installation worked fine could program the key ect. tried remote start ignition comes on but no start at first ign on if i touch the brake it would stall soon after at second ign on (on same remote start attempt) it keeps running. verified yellow/red wire to black/red wire all seems ok. i got 12v at black/red if i touch the brake. at one time while trying car start even if yellow/red was connected. car is a diesel if that matters.
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)

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)

26/01/2025

 Volkswagen Andrew Thompson (470Pts.)

0

2012 Beetle says depress clutch when trying to remote start

BCM wire color is different from guide for clutch bypass - I wired to pin 51 and when it tries to remote start it says depress clutch on dash. If i press clutch in the remote starter works. Trying to understand if this is the correct pin on bcm used .
Login to reply View 2 answer(s)

26/01/2025

 Volkswagen Andrew Thompson (470Pts.)

0

2012 Beetle says depress clutch when trying to remote start

BCM wire color is different from guide for clutch bypass - I wired to pin 51 and when it tries to remote start it says depress clutch on dash. If i press clutch in the remote starter works. Trying to understand if this is the correct pin on bcm used .
Login to reply View 2 answer(s)

08/12/2024

 Volkswagen ranran971 (190Pts.)

0

Can i get by evo bypass key reset resched my vehicles lemit

S/N:001A07304629
Login to reply View 2 answer(s)

08/12/2024

 Volkswagen ranran971 (190Pts.)

0

Can i get by evo bypass key reset resched my vehicles lemit

S/N:001A07304629
Login to reply View 2 answer(s)

02/12/2024

 Volkswagen Bradv (350Pts.)

0

solid orange and red light after 1st decryptor

Trying to get my remote start in my 12 Passat TDI working. When I get to the decryptor stage 2 it just has solid orange and red light on when you reinstall and turn on the key, it stops there, just those 2 lights.

its t harness VW_T6 so there isn't really much to hook up, all plug an play except i had to wire in the key reader.  car doesn't need the brake pressed, and i didn't wire in the hazzard wire as it was listed as optional.  seams like it read the key fine, and the app seemed to program the unit after. 

any ideas what i can try, i have all ready hit the flash/decryptor limit. the last thing i was trying was to use the firmware in the instructions instead of the recommended in the app. however i could not do the decryptor step as i hit the limit. 

Login to reply View 2 answer(s)

02/12/2024

 Volkswagen Bradv (350Pts.)

0

solid orange and red light after 1st decryptor

Trying to get my remote start in my 12 Passat TDI working. When I get to the decryptor stage 2 it just has solid orange and red light on when you reinstall and turn on the key, it stops there, just those 2 lights.

its t harness VW_T6 so there isn't really much to hook up, all plug an play except i had to wire in the key reader.  car doesn't need the brake pressed, and i didn't wire in the hazzard wire as it was listed as optional.  seams like it read the key fine, and the app seemed to program the unit after. 

any ideas what i can try, i have all ready hit the flash/decryptor limit. the last thing i was trying was to use the firmware in the instructions instead of the recommended in the app. however i could not do the decryptor step as i hit the limit. 

Login to reply View 2 answer(s)

30/11/2024

 Volkswagen Bradv (350Pts.)

-1

Decryptor limit, Decryptor issue, 2012 Passat tdi

Trying to get my remote start in my 12 Passat TDI working. When I get to the decryptor stage 2 it just has solid orange and red light on when you turn on the key, and stops there, After multiple attempts I am locked out. Sn 001A07 071025
Login to reply View 2 answer(s)

30/11/2024

 Volkswagen Bradv (350Pts.)

-1

Decryptor limit, Decryptor issue, 2012 Passat tdi

Trying to get my remote start in my 12 Passat TDI working. When I get to the decryptor stage 2 it just has solid orange and red light on when you turn on the key, and stops there, After multiple attempts I am locked out. Sn 001A07 071025
Login to reply View 2 answer(s)

13/11/2024

 Volkswagen Dennis.daraphone (310Pts.)

0

2018 Tiguan will not start

2018 VW Tiguan, STD-Key, Not digital cluster, AT EVO-ALL firmware 64.06 THAR-VW6 Decrypted and programmed successfully, but when trying to remote start via lock lock lock from oem key, car turns on, but doesn't crank. Tested while in the car and the depress break light (shift lock) was still illuminated. I wired in the Yellow/Red Break Out to Black/Red VESCM (+)Foot Break correctly. Tested command start while in the car and depressing the break, works. Please assist.
Login to reply View 2 answer(s)

13/11/2024

 Volkswagen Dennis.daraphone (310Pts.)

0

2018 Tiguan will not start

2018 VW Tiguan, STD-Key, Not digital cluster, AT EVO-ALL firmware 64.06 THAR-VW6 Decrypted and programmed successfully, but when trying to remote start via lock lock lock from oem key, car turns on, but doesn't crank. Tested while in the car and the depress break light (shift lock) was still illuminated. I wired in the Yellow/Red Break Out to Black/Red VESCM (+)Foot Break correctly. Tested command start while in the car and depressing the break, works. Please assist.
Login to reply View 2 answer(s)

15/10/2023

 Volkswagen RemoteStartNoob (180Pts.)

0

2014 VW Jetta Hybrid - Does not always start, sets CEL and EPC light on dash

Greetings all, 2014 VW Jetta Hybrid Push to start, buried key, used THAR - VW1 w/EVO-ALL. Checked connections 4 times over, no issues with wiring, I can affirm this vehemently. Vehicle attempts to start, fails randomly. EPC and CEL lights will illuminate on dashboard, DTC P0703 will set for a circuit malfunction. Correct pin and wire color are tapped, as I have checked this vehemently. If you push your foot on the brake and remote start, the DTC will still set. If you start the vehicle normally, the DTC will NOT set, even with everything connected the same. The vehicle will also NOT retry starting once the ignition is on, I'm not sure why this is. It will just sit there for 15 minutes with the ignition on, but no engine on. When this concern initially appeared, I rolled the firmware back a version and this fixed the issue temporarily. I let the vehicle rest overnight and the issue returned next day. Does anyone have any info on this? Please let me know, thank you.
Login to reply View 2 answer(s)

15/10/2023

 Volkswagen RemoteStartNoob (180Pts.)

0

2014 VW Jetta Hybrid - Does not always start, sets CEL and EPC light on dash

Greetings all, 2014 VW Jetta Hybrid Push to start, buried key, used THAR - VW1 w/EVO-ALL. Checked connections 4 times over, no issues with wiring, I can affirm this vehemently. Vehicle attempts to start, fails randomly. EPC and CEL lights will illuminate on dashboard, DTC P0703 will set for a circuit malfunction. Correct pin and wire color are tapped, as I have checked this vehemently. If you push your foot on the brake and remote start, the DTC will still set. If you start the vehicle normally, the DTC will NOT set, even with everything connected the same. The vehicle will also NOT retry starting once the ignition is on, I'm not sure why this is. It will just sit there for 15 minutes with the ignition on, but no engine on. When this concern initially appeared, I rolled the firmware back a version and this fixed the issue temporarily. I let the vehicle rest overnight and the issue returned next day. Does anyone have any info on this? Please let me know, thank you.
Login to reply View 2 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