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

8

FAQ: How do I reset my EVO-ALL?

The master reset is very simple on the EVO-ALL, but be warned that a reset will also reset all the options back to default if Settings Protection was not enabled. So if you have any special options enabled (such as the all famous D1 and C1 for 3x lock start), or if the vehicle programming requires the use of the DCryptor, make sure that you have access to the Flash-Link Manager!


So here it is...

    Hold down programming button while plugging in datalink connector. Let go of button when LED is RED. Push and hold button again until all three LEDs start to alternate. Disconnect unit, it is now reset.

6

FAQ: RED LED STUCK ON

When a module is stuck on the RED LED. 

    flash version 0.99 disconnect unit from the flasher and power cycle it in the car (connect/disconnect power connector) connect module back to the flash link and flash whatever firmware you need Turn settings protection OFF if it's on and SAVE the options. Reset the unit following the reset procedure. (this cannot be done while module is connected to the flash link) : https://fortin.ca/en/qa/50193/faq-how-do-i-reset-my-evo-all?show=50193#q50193 Connect module back to the flash link and enable required options. Reprogram module to the vehicle following instructions in the installation guide.

 

Reasons this happened.

    Unit was connected WHILE doing the install. Unit was disconnected during CAN programming before the blue led started to flash. Power was disconnected while all other connectors were still connected.  during an update or save of options, the flash link lost connection to the module or the internet RF protocols not setup correctly, or RF device not paired to unit correctly. Datalink protocols not setup correctly. Bad ground. Loss of power during writing of data to the module.

6

FAQ: How do I know/how to test if my vehicle has an OEM alarm.

Just figured I would post this as I have often been asked...

 

" How do I know/how to test if my vehicle has an OEM alarm?"

 

Really simple to check, perform the following test:.

 

 

1- Put down the drivers window.

 

2- Ensure all doors are closed, including the hood and trunk.

 

3- Lock the vehicle using the OEM remote.

 

4- Wait between 45-60 seconds after you have locked the vehicle to allow the system to arm itself.

 

5- Once you have waited the time period reach inside the drivers door and open the drivers door from the inside handle. (basically replicating someone trying to steal your belongings/vehicle).

 

6- At this point your alarm will either go off or it won't, answering the question if your vehicle is equipped with a factory alarm!

 

Side note: good way to also test to see if your vehicle has a factory hood pin that is part of the alarm system is to do the above test but instead of opening the door first, reach in and pull the hood release latch. (useful on newer Mazda vehicles with factory hood pins that are part of the OEM alarm). If no alarm goes off, then open the drivers door. If the alarm goes off when you open the drivers door and not when you open the hood. Then this answers your question if the factory hood pin is part of the alarm system.

 

6

FAQ: How to program 3x Lock Start on the EVO-ONE

Your best bet here is to follow the step-by-step guide available here : EVO-ONE & OEM Remotes

    That guide covers basic option setting for 3x Lock Start on Automatic vehicles. If your vehicle is Manual/Standard transmission, you will also have to enable option 33.2. Flash-Link Updater REQUIRED

Quick Run down.

The EVO-ONE has two sets of options. There are options for the remote starter portion while there are also options for the bypass portion of the unit. The remote starter options are used mainly for convenience features such as enabling 3x lock start, alarm functions, cold timers etc... while the bypass options are there to set various DATA / Can-Bus features such as the all important OEM Remote Monitoring.

 

To toggle between remote starter and bypass options (and firmware updates) via the Flash-Link Manager, you must press the TOGGLE button in the flash-link manager program while the unit is disconnected. There is a text on the bottom right corner that will tell you if you are in Connection Mode : Bypass or Connection Mode : Remote Starter.

 

While Connection Mode : Remote Starter is active, go to the EVO-ONE Options tab and enable the following option(s).

    Option 38.2 - Enable 3x Lock Start (this tells the remote starter that it will be controlled via the oem remote commands detected and then sent via the integrated bypass module) Option 33.2 - Enable this option only if you have a manual transmission vehicle. While here, if the vehicle specific install guide also mentions other required options, please set them now. Don't forget to SAVE OPTIONS.

 

While Connection Mode : Bypass is active,

    First, make sure you have selected and flashed the unit to the latest firmware for your vehicle. You will find the latest firmware under the EVO-ONE Updates tab. Go to EVO-ONE Options Scroll through the options and enable Option C1 - OEM Remote Monitoring (this option allows the bypass portion to actually monitor the oem remotes so that the previous 38.2 option can actually work). Attention! Please leave all the A1-A11 options untouched unless told otherwise. Don't forget to SAVE OPTIONS

 

5

Do I need the Flash-Link Updater?

Every profession has its tools. The Flash-Link Updater device, and the Flash-Link Manager software, are no exception to this rule.

 

The Flash Link Updater (FLU) allows you to update the firmware on your Fortin bypass modules and remote-starters in a matter of seconds. The FLU will work with modules that have bar codes or QR codes stamped on the label. It's compatible with Windows software, and allows you to upgrade/downgrade the firmware version on any of our supported modules through a USB cable, PC and Internet connection..

 

The Flash-Link Updater device is available through all Fortin authorized distributors.

The Flash-Link Manager software is available for free download here: https://fortin.ca/en/support/flashlinkmanager.html

 

 

5

How to check if my vehicle's key has an immobilizer chip.

Just figured i would post this up as i have been asked a few times on how to test if the vehicles key has an immobilizer chip inside it.

 

Pretty simple, wrap the key in alluminum foil insert it into the ignition and try to start the vehicle. If the vehicle starts then your vehicle does not have an immobilizer.

 

Here is a picture to refrence on how this would be done.

 

14/10/2020

FAQ (Pts.)

4

Volkswagen & Audi programming diagnostics

Trouble programming an Audi or Volkswagen?

 

VW/Audi that use 75.XX and 67.XX firmware (non-RLink programmer)

 

    2x Red LED Flash = CAN2 not connected properly 3x Red LED Flash = Unknown vehicle , cluster unknown, check CAN2 4x Red LED Flash = TB-VW not connected, or not connected properly 5x Red LED Flash = Dcryptor 1 did not work (for vehicles that require 2 Dcryptors') 6x Red LED Flash = Unknown vehicle, cluster unknown, check CAN2. If bcm is not original or has been modded, consider a keywrap.   

VW/Audi using 64.XX / 65.XX (with R-Link programmer)
    Red LED toggle 1sec On/Off = no communication with RLink or it's connection or key placement. If the vehicle is PTS, DO NOT leave the key tapped on the ring. Also if PTS, take battery out of the remote. On all vehicles, be sure to use PIN 2 of the transponder connector, do not go by color. 2x red LED flash = Connection problem with CAN2 3x red LED flash = Not able to access cluster information. Call tech support. 5x red LED flash = Cluster is on protection function, Reconnect TB-VW , keep ING ON and wait 15 minutes

 

4

Informational: Interfacing Compustar T11/T12-style remotes to EVO-ONE

I'm not a Fortin rep but someone might find this useful -- I struggled with making these types of Compustar remotes work with the EVO-ONE. There are a few reports here of success with these remotes, and I had to do alot of experimentation to get satisfactory results, because these reports were somewhat vague and didn't cite which Firmware revisions were used when these observations were made. I can report that Firmware 7.1.24 (latest as of this thread) allows full function of these remotes without any drama, with the exception of a missing "remote start ready" (engine icon) indicator, which to me isn't any type of deal-breaker considering the capabilities of these units. Temperature, voltage, trunk, remote valet, alarm paging, etc. all work. The Fortin documentation states that FW 7.0.96 must be flashed for (supported) Compustar remotes, but this FW level is not sufficient to get full function from the (unsupported) T11/T12 remotes. 7.0.96 - Couldn't program remotes with Mode 1 or Mode 5. 7.1.16 - Remotes programmed immediately on Mode 5 and function, but temperature and voltage status reported erroneous numbers. 7.1.24 - Remotes programmed immediately on Mode 5 and all functions appear to work, with the exception of the "ready" engine icon which indicates a remote start is possible. IMHO, might be an issue for manual-transmission vehicles. Remote start functions regardless. To get this remote to work, flash the EVO-ONE to 7.1.24, and program the remotes with Mode 5. That's it. ** IMPORTANT ** -- There's no LED or valet switch on the antenna, even though the plastic housing looks like these features are there. This seriously confused me. I was trying to press that plastic square over-and-over thinking this was a valet switch, but it's a cosmetic feature, and does nothing, and there's no LED. I had to pop the antenna open to confirm this. Just flash to 7.1.24 and follow the instructions in the Compustar document from Fortin to program the remotes using Mode 5.

4

FAQ - Getting Started - Data-Link FAQ

What is data-link?
Data-link is a high speed data communication link used between more than one after-market electronic device. These devices include remote-starters, alarm systems, GPS and telematics devices, and immobilizer bypass or interface module(s). The data-link protocol uses the EIA (Electronic Industries Association) RS-232 serial connection and communication standard. This is the exact same communication standard used with USB, which allows various electronic devices to communicate with each other. In our case, it allows the remote-starter or alarm-system and the immobilizer bypass or interface module(s) to share a variety of different information.

 

What benefits are there when using data-link?
Using the data-link port to link communication between the after-market remote-starter or alarm-system and an immobilizer bypass or interface module reduces the amount of wiring required in 2 ways. First it reduces the amount of redundant wiring required for both devices. Instead of having to manually connect an ignition wire to both devices, using the data-link port will only require you to connect the ignition wire to one device, which will share the ignition status (ON/OFF) through the data-link port to the other connected device(s). Secondly it reduces the amount of wiring by not requiring analog connections in a networked vehicle. Many of the vehicles functions can be read by receiving and controlled by sending data on the vehicles data-bus (eg J1850, CAN, etc.). Our immobilizer bypass and interface modules offer control over a variety of different functions on thousands of different vehicles and can send and receive data on the vehicles data-bus through instructions from the data-link port. This normalizes the communication and allows an after-market remote-starter or alarm-system to send and receive data from the vehicle without having to manually connect an analog wire to the vehicle for every possible function.

 

Reducing the amount of wiring required for the installation not only simplifies the installation and saves time, but it also reduces the chances of installation error and fewer possible points of failure due to cold solder joints and corrosion.

 

What is the difference between 1-way and 2-way data-link?
The 1-way data-link port allows a remote-starter or alarm-system to send commands to an immobilizer bypass or interface module. This includes such commands as GWR status, door-lock, door-unlock and much more. The 2-way data-link is an extension to the 1-way data-link protocol by allowing the module to send numerous different statuses from the vehicle back to the remote-starter or alarm-system. This includes such statuses as door-pin, hood-pin, tachometer RPM and much more.

 

What Fortin products support data-link?
All of our data modules support data-link. All of these modules are listed in the "Affected Products" list at the top of this page. You can also manually check the features section of any of our products to determine if the module supports the 1-way protocol, 2-way protocol, or both.

 

Does data-link work with DEI's D2D or DBI?
Data-Link is the protocol that works all after market remote starters and alarm systems. Moreover, we include all necessary conexions to these products. Therefore, Data-Link is compatible with D2D, DEI and DBI protocols.


What remote-starter and alarm-systems support data-link?                                                                                   More brands of remote-starters and alarm-systems currently support our data-link protocol than any other similar protocol. Click here to view a current list of compatible brands.

 

Is data-link extensible?
Absolutely. The protocol has been extended numerous times to include various new features and functionality and there is still plenty of room for future enhancements as we continue to release new products and firmware with features that simplify after-market installation.

 

Why does my module have more than one data-link port?
Some of our immobilizer bypass and interface modules have more than one data-link port in order to allow you to use more than one module on the data-link bus by daisy-chaining them together. Although chaining together multiple devices in this manner appears to be in series, the data-link bus is in fact a parallel network, so you can achieve the same result by splicing into a data-link cable and create a T-harness with more than one cable.

 

What if my remote-starter or alarm-system does not support data-link?
All of our data-link modules can still be wired manually if the remote-starter or alarm-system you are installing it with does not support data-link. Every immobilizer bypass and interface module can be wired manually so it remains compatible with all brands of after-market remote-starters and alarm systems. However, since some of modules support more functions than there are wires available on its plugs, some of the less common features may only be available through data-link. When this is the case we try to make the most common features available on the plug as a wired input or output to offer the broadest range of support.

 

How do I troubleshoot a problem with data-link?
Since the data-link port handles most of the signals that a wired input or output would traditionally handle, it becomes difficult to troubleshoot the communication between the devices when a problem occurs. Because of this we provide the TEST-LINK 2-way data-link tester. It has 2 data-link ports and connects between the remote-starter or alarm-system and the immobilizer bypass or interface module. It allows the installer to verify 7 different input commands (Foot Brake, Tach, Overrev, Hood, Door, Trunk, Hand Brake) and has a button which sends a LOCK output.

3

Informational: Interfacing a flashing LED to EVO-ONE

I'm not a Fortin rep but someone might find this useful -- I wanted to interface a flashing LED to an EVO-ONE, and didn't want to use something like a "dummy" flashing 12V LED as this doesn't properly convey the status of the unit (arming/armed/valet) and my antenna doesn't contain it's own LED. I ended up aquiring the following -- 1- RFAXL202 kit, which is a pair of harnesses used to interface DEI anetnnas to the EVO-ONE with an XL-202. 2- A DEI 2v "super-bright" LED (either the red or blue ones. The blue LED is several orders of magnitude brighter than the red at the same 2v, if that's what you want). 3- A 220ohm resistor. The RFAXL202 kit contains a four-pin blue plug with a single orange wire. I de-pinned the orange wire on the Fortin plug and inserted the pin from the DEI LED connected to the blue wire on the DEI LED in its place. I insertered the pin on the DEI LED connected to the red wire into the Fortin plug directly adjascent to the blue DEI wire that replaced the orange wire. I put a 220ohm resistor in series on the red wire on the DEI LED. The resistor is necessary because the EVO-ONE is outputting 5V on the pin used by the red wire and the DEI LED operates at 2V. This new plug will go into the larger of the two blue 4-wire plugs. This will give a functional status LED that mimicks what would be found on an antenna or a conventional car alarm. You can use a 12V, non flashing LED and simply connect the (-) to the orange wire on the blue plug from the RFAXL202, but I think this method of interfacing the LED is cleaner, and I find the appearance of the DEI LED housings to be aesthetically superior to a generic 12V LED when installed into a blank panel, etc. in a vehicle.

3

EVO-ONE and Drone DR-5400

I just wanted to come and say that the Drone DR-5400 does work with the EVO-ONE when following the DR-3x00 instructions. I've successfully installed one and got the remote start, lock/unlock/truck/vehicle status working.

3

What is the correct way to connect wires?

T-Taps, Butt connectors 2 pounds of solder I've seen and heard it all...most of the time resulting in a headache and lost time. So i thought i would break it down and show the 5 easy steps to make a good quality and secure connection in a vehicle.

The 5 Steps are as follows:

1- Strip back the inulation of the wire you wish to connect to.

2- Seperate the braid to create an opening in the wire.

3- Insert the wire that is to be connected into the opening.

4- Close the wire.

5- Finally twist the wire around securing them togehter and finish it off with some electrical tape.

3

2016 Chevrolet Cruz FYI

Just to make some customers aware the new style of flip key for the Chevrolet Cruz is not supported at this time. Check the site periodically for the new solution to be released.

Here are some pictures for refrence.

3

Troubleshooting guides based on the FORTIN product you are installing.

Just thought I would post this up maybe some people will find it useful!

Troubleshooting guides based on the FORTIN product you are installing.

 

Here you will find the following:

 

1: Useful information on programming your module to the vehicle.

2: Installation guides for your vehicle.

3: Common issues when the module will not program.

4: Vehicle specific information for your module/installation.

 

Here is the link:

 

http://fortin.ca/en/support/troubleshooting.html

3

Why can't I seem to download the PDF files anymore?

I used to be able to download the PDF format for each of the tokens I used on unlocking vehicles. Every time I try now I get an "ERROR" saying that it can't download the file.

3

Which protocol and connections to use

Hey Nick, Just want to clarify.  I primarily use Autostart remote starters (ex: as-1780) with and EVO-ALL.  Lately I have been having similar issues on installations where certain things will not work. I have always used the "BLACK" D2D (ADS/FORTIN) connection on the back of the autostart and left the bypass option (mode 4, func 4, opt 2) on "Xpresskit 2 way D2D" as instructed by tech support, recently It was shown to me that I should be using the "RED D2D" (Xpresskit), so i have been using it this way.  Now, should I be trying "Fortin 1 way D2D" protocol on the Autostart? (mode4, func 4, opt 3) Thanks, Mike.

3

Lock and brake status not working through datalink

I've already solved this problem, but found this to be an excellent forum for remote start questions so I'm writing this in order to help others that may run into the same problem I did.

Installed a Crimestopper RS7-G5 with an EVO-ALL.  Remote start, unlock, even the tailgate open worked fine, but there were two problems:

Pressing lock on the Crimestopper remote would lock and immediately unlock the doors; brake status wasn't being received by the Crimestopper (so the remote start couldn't be cancelled by pressing the froot brake).

Tested grouding the purple wire on the EVO-ALL to confirm that it properly controlled the locks.  That worked as expected so the problem was in the Crimestopper.

After a bunch of messing around and reading other questions here, I set the option on the Crimestopper to use the Fortin DataLink protocol.  The default option is supposed to already be set to the Fortin protocol, but for some reason, this Crimstopper unit was incorrect from the factory.

(This might be the same problem as posted in this question, but that question was never fully resolved.)

16/12/2018

FAQ HAI TRAN (210Pts.)

2

LINKR-LT2 (VS-4LU) 4G won't work with EVO ONE

I just got a Linkr-LT2. It came with the Linkr-LT1 quick install guide. I followed the steps in the quick install guide but the unit does not work.
The Linkr LT app only shows my car battery voltage and connection signal. The GPS tracking is working fine. The START/STOP/LOCK/UNLOCK
don't work. I searched the internet and found the "mycar installation guide". I followed the steps to learn the Linkr-lt2 to the Evo one. I turned on the "Fortin 2" function on the EVE ONe.  I pressed and held the valet button for 5 seconds but the RED led light on the Evo One did not turn on.

 

Problem SOLVED. .Linkr LT2 is working fine now...

I found the video on youtube 12voltsolution.  The guy pressed the UNLOCK button on car key several times to neutralize the EVO ONE before he did the following steps.

 

STEP 6. LEARN THE MYCAR TELEMATICS DEVICE TO THE EVO-ONE
In order to communicate with the remote starter, the telematic system must be learned to the EVO-ONE.
1 - Cycle the ignition to the ON position.
2 - The YELLOW LED on top of the EVO-ONE should come ON.
3 - Press & Hold the EVO-ONE programming Valet button for 5 seconds.
4 - The RED LED on the side of the EVO-ONE will Flash rapidly.
5 - Release the push button.
6 - Press & Release the push button 5x times. Everytime the push button is pressed the parking lights
& the RED LED on the side of the EVO-ONE will blink.
7 - Then Press & Release the Brake pedal.
8 - At that same moment the RED LED on the side of the EVO-ONE will blink once to confirm that the
Telematic device ID has been learned to the EVO-ONE.
9 - Cycle the vehicle’s ignition to the OFF position to Exit the EVO-ONE programming.

 

 

 

 

2

Flash-Link Updater is only detected by FlashLink Manager in FLU mode?

Software: FlashLink Manager 4.36; Windows 10 Pro x64 version 1809 Hardware: Flash-Link Updater Ver.4, firmware 4.03 FlashLink Manager will not detect my Updater, unless I attempt to initiate a firmware update. Following that process, the firmware update gets stuck at 1%, so nothing happens. Canceling the update just puts me back to square one, with FL Manager stating that it is unable to detect the FL Updater. The red power light is on, indicating proper power, and I have tried multiple USB ports and cables, even different computers. The Updater driver was installed correctly, and "FES FlashLink Device" appears in my Device Manager with no warnings. The fact that the unit is detected when I try to update the firmware gives me hope that it is not defective, so can someone show me what I'm missing? Thanks!

2

Compustar T11 Pro abnormalities

This isnt a question. This is meant as a tool for anyone who experienced the same problems as myself with no real correct answers to be found online. I recently installled and had issues with using the compustar t11 pro rf kit with my evo-one. When using the valet switch and RF remote to program functions and options the following button mapping is correct: Lock: 1 unlock: 2 start: 3 trunk: 4 Also when I orginally purchased the T11 pro the two-way remote that came with the kit did not function correctly, which Compustar quickly remedied. However when programming the new remotes(2wt11r-ss, 1wg8r-ss) to the evo-one with the newest firmware installed I had to press the trunk button on both remotes w/ a 2.5 second hold to get them to register with the evo-one. All the strange button mapping aside. Lock/Unlock/remote start/etc, two-way functions, and vehicle temperature reading on the remote all function normally.

2

How to check if my module is properly configured

Ever wonder how your module has been set up? If you have the correct firmware and options for your vehicle?

Did you know you can check all of these things simply by entering the service number on the back of the module in the search bar located on fortin.ca!

Give it a shot the next time you are unsure of how the module has been configured!

 

2

Why won't Evo Start App accept service number for the registration code?

Whe I type yhe sevice number into the Evo Start app, it tells me it is an invalid code. What number should I be using?

2

How to jump a car with a remote start installed?

Is it advised to disconnect some harnesses from the EVO unit in case your car needs to be jumped/boosted to avoid damage? Maybe the 6 pin for the EVO-ONE? Bypass connector for the EVO-ALL? Also, would it matter if you were the booster or boostee? Thanks!

2

How to trim the extra wires?

Wondering what other people do with the extra unused wires from the harnesses. I've been trimming them different lengths, taping the ends, and then taping them all together. Is there a different, possibly better way people think is better? Thanks

2

Can you use the Flash-Link with an AX-ONE?

Wondering if you can flash an AX-ONE with EVO-ONE firmware if you hooked it up to a FLASH-LINK? 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