Your Cart

Your shopping cart is empty.

Your shopping cart is empty.

Continue Shopping

QUICK VEHICLE FINDER

VEHICLE FINDER

Questions & Answers

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

recent questions tagged: ...

picto contact

Looking of our top participants?

See users
picto contact

Couldn’t find what you were looking for?

Ask us a question

0

Issues with lock/disarm unlock 2011 jetta standard key manual transmission

When following install guide #61521 for manual transmission on 2011 jetta it shows the blue/red connection off of BCM plug A connected to the green/red of the evo-all module, this function is not working all other parts of the install are functioning except for unlock/disarm. Is there a solution to this issue?

0

Car tries to start when I unlock doors from rf kit

Hello, I’ve recently installed evo-vwt1, on Passat 2018. Everything worked well, than I added rfk942, was able to program it with no problem. Now, the problem when I try to unlock the car from rf kit it tries to start the car, other than that all functions, lock, trunk and remote start, work well. Any idea of what I’ve done wrong?

1

2011 Golf EVO-ONE w/Drone DR-5400 Lock/Unlock issue

Hello! Finally got my EVO-ONE and Drone working on my 2011 Golf manual TDI. I can get the Drone to start and stop the vehicle. I even got it to open the hatch. However it wont lock or unlock the doors. If I hit unlock it seems to engage the ingition for a split second(gauge cluster and radio lights up) then turns off, and then the yellow light comes on. If I hit unlock again it does the same thing and then the yellow light will turn off.(The blue light does not flash at all.) If I hit lock the blue light will flash extremly quickly once but nothing else happens. I don't want to have to keep flashing the unit and hit the flash limit because I can't change options when loaded on 0.50 RS firmware.

0

jetta 2012 no lock unlock on can wire?

hi installed evo-one in jetta 2012 puch start. everything programmed good but lock unlock does not work. blue led flash Slightly (not strong blue flash but faint )on evo one but does not lock unlock. version 75.38 installed should i back down to different software?

0

2013 VW GTI - Lock/Unlock via CAN does not work on EVO-ALL

I have an EVO-ALL installed in a 2013 VW GTI Automatic as a standard installation with a Compustar CM7200 remote start module. I wired up the module as shown in the installation guide, but the lock/unlock functions do not operate correctly. Nothing happens with a lock command. With an unlock command, the ignition pulses on, but the doors do not unlock. Any help would be appreciated.

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?

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?

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?

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?

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

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