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

Will the 4 pin data plug fit compustar cm7000

Can i use evo all in data connection with a compustar cm7000? Also arm disarm with oem key fob option 1-12 says it works with idatalink module, will it work with evo all if protocol is changed to ap/ofa? Will 3xlock work on 2015 f150 with compustar cm7000?

20/01/2016

Jeep AJBrown (320Pts.)

1

False Alarms to Compustar CM7000-AS

Vehicle: 2015 Jeep Wrangler  Alarm: (New-Install) Compustar cm7000as w/2W704r-sh long range 2-way RF transmitter  Bypass Module: Fortin EVO-ALL    The only wiring done outside the CAN-BUS are parking lights, siren, hatch trigger and 12v switched connections.    - Doors triggers are connected through CAN-BUS; hood and hatch triggers are hard-wired into Jeep.  - Compustar DAS Tilt/2-stage shock Sensor is currently DISCONNECTED from the brain.  - DEI Proximity Sensor is currently DISCONNECTED from the brain.    About 20% of the time my Compustar will go into full alarm within 5 seconds of arming the system. I thought the issue might have been the proximity sensor so I disconnected it completely. When that didn't work, I also disconnected the DAS tilt/shock sensor with no change (currently no external sensors are connected).    After going into full alarm, pressing disarm turns off the siren but the parking lights continue to cycle through the full timeout period of 30 secs and the doors do not unlock. If I hit disarm a second time, the trigger cycle stops and the doors unlock but there are NO zone breaches indicated on the 2-way remote, by parking light or LED flashes as if the alarm never went off.    When the alarm triggers, I can disarm the system twice, stopping the cycle, and immediately ARM the system with no repeated full trigger.    Next, I disabled all triggers and unused options within the EVO-ALL with no change.  I finally disconnected the data wire from the EVO-ALL and I had not had a false alarm for one day.  I then reconnected the DAS Tilt/2-stage shock sensor and the DEI 508D Proximity sensor and haven't had any false alarms in two days.  This leaves me thinking the problem is either the EVO-ALL or there is something in the CAN-BUS that the EVO-ALL is picking up and causing the false alarms.  I'm hoping someone out there has a suggestion for me.     Thanks in advance for any help you can provide!

2

How to wire a Compustar CM7000 to the Evo-all (Evo-GMT4) using idatalink

I have a 2007 Chevy Avalanche. i purchased CM7000, Evo-All with T-harness, and a drone Dr-3100.

 I installed the evo-all using the T-harness, hoping for a quick and easy installation. After the Evo was installed and programmed, I am able to use the OEM remote to start/stop the vehicle, it works fine.  I then attempted to connect the CM7000 alarm/remote start to the Evo-all using "connection A", installation with Data-Link. Here is where I might be missing something. The instructions detail how to add a remote start to the Evo, so i assume it would be the same for the CM7000 Remote/alarm combo. 

The instructions state that only the the ignition out wire needs to be connected to the Evo-all From the CM7000, and that some alarm require the 12v Battery wire to be connected directly to the T-harness, so I tried it with the 12v wire both ways.

From the CM7000, I connected the 12V Green ignition wire on the Low current ignition harness (CN3) to the yellow ignition wire (A1) on the Evo. i am using a Compustar 2-way remote (2W704R-SH) with the alarm.  it was my understanding that the instalation with Data-link is suppose to greatly reduce the number of wires that you have to connect. I changed option F2 from "Fortin" to "AP-OFA" then the 2-way remote locks and unlocks the doors.

My problem is that when i try to use the 2-way remote to start the vehicle, nothing happens. Its like the alarm is not communicating with the evo or the vehicle. None of the lights on the dash light up.  However I am able to Lock and Unlock the using the 2-way with no problems.   i took it a step further and attempted to connect the Black status out wire from compustuar's 20-pin harness (CN5) to the Ground while running Dk. Blue wire on the Evo, and also the 12v yellow starter output from the compustar ignition harness, to the red/blue start wire of the Evo.  when trying to remote start

    Are there any other wires from the CM7000 that i need to connect (or connect to the Evo) in order for the remote start to work? the Door locks are working fine. I was under the impression that no other connections were needed since i would be using the Idatalink installation. Will any of the the wires (other than the siren, parking light, and hood pin) need to be wired directly to the vehicle in order for this alarm to work or will it all be handled thru the data-link? Does the horn output work thru the data-link or will it need to be wired directly to the vehicle? What could my issue be?

Thanks in Advance!

20/01/2016

Jeep AJBrown (320Pts.)

1

False Alarms to Compustar CM7000-AS

Vehicle: 2015 Jeep Wrangler  Alarm: (New-Install) Compustar cm7000as w/2W704r-sh long range 2-way RF transmitter  Bypass Module: Fortin EVO-ALL    The only wiring done outside the CAN-BUS are parking lights, siren, hatch trigger and 12v switched connections.    - Doors triggers are connected through CAN-BUS; hood and hatch triggers are hard-wired into Jeep.  - Compustar DAS Tilt/2-stage shock Sensor is currently DISCONNECTED from the brain.  - DEI Proximity Sensor is currently DISCONNECTED from the brain.    About 20% of the time my Compustar will go into full alarm within 5 seconds of arming the system. I thought the issue might have been the proximity sensor so I disconnected it completely. When that didn't work, I also disconnected the DAS tilt/shock sensor with no change (currently no external sensors are connected).    After going into full alarm, pressing disarm turns off the siren but the parking lights continue to cycle through the full timeout period of 30 secs and the doors do not unlock. If I hit disarm a second time, the trigger cycle stops and the doors unlock but there are NO zone breaches indicated on the 2-way remote, by parking light or LED flashes as if the alarm never went off.    When the alarm triggers, I can disarm the system twice, stopping the cycle, and immediately ARM the system with no repeated full trigger.    Next, I disabled all triggers and unused options within the EVO-ALL with no change.  I finally disconnected the data wire from the EVO-ALL and I had not had a false alarm for one day.  I then reconnected the DAS Tilt/2-stage shock sensor and the DEI 508D Proximity sensor and haven't had any false alarms in two days.  This leaves me thinking the problem is either the EVO-ALL or there is something in the CAN-BUS that the EVO-ALL is picking up and causing the false alarms.  I'm hoping someone out there has a suggestion for me.     Thanks in advance for any help you can provide!

19/12/2015

Jeep AJBrown (320Pts.)

1

EVO-ALL with Compustar CM7000

I want to change my current setup from using a Fortin EVO-ALL as stand alone to Compustar CM7200 Remote starter with the EVO-ALL as the bypass and have some questions.  
    Will I be following Fortin instructions "A - INSTALLATION WITH DATA-LINK" from the PDF guide here (http://fortin.ca/download/28831/evo-all_evochrt5_o20150216.pdf)? Will the Fortin control the door lock/unlock with arm/disarm and monitor door triggers through the CAN-BUS with no additional wiring required? CM7200 Pin 15 Black - Is the Status/Ground wile running, typically used to trigger bypass / transponder modules.  Will this wire be required and, if so, where does it connect on the Fortin EVO-ALL (http://techfeed.compustar.com/ft_controllers/manuals/CM7000_Full_Install_3.00_EN.pdf) Will the factory FOB's lock/unlock and arm/disarm the alarm or will I have to exclusively use the aftermarket remotes?   Will I need to follow the EVO-ALL PROGRAMMING (Page 14 http://fortin.ca/download/28831/evo-all_evochrt5_o20150216.pdf) or is that not required since it's only a bypass for the remote starter on the CM7000?

 

0

Data BCM Cable for Subaru 2015 WRX STI Standard Key with EVO ALL

Hello, I am looking at the wirecolor reference document for the 2015 Subaru WRX STI Standard Key using the EVO ALL and the Data BCM cable is not shown in the wire color document. Just want to confirm which cable I have to connect. Picture # 16 shows the BCM correct? Is the Data BCM cable located in that far right plug on the BCM?I know is Pin 11 and red color but just want to confirm that is that plug on the BCM. Thank you for your help.

0

2015 Subaru WRX STI Clutch Bypass Needed? Using EVO ALL and Compustar CM7000AS

The car is a 2015 Subaru WRX STI with 6 speed manual. I am using an EVO ALL with guide # 3034 and Compustar CM7000AS. I was reading the compustar guide and it says that I may need to wire the clutch bypass to remote start but the guide from Fortin doesn't mention this. Do I need to wire the clutch bypass or the EVO ALL should take care of this? If I need to wire it, can you please tell me how? Thank you.

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