Weblink Usb Driver


There's really not much to say about this item except that it does what it's supposed to do. Basically, one end of the cable has a 4-pin connector and connects to your iDataLink or FlashLogic module and the other end of the cable is a standard USB male that connects to your PC/laptop for flashing or upgrading your vehicles applicable firmware. Wavlink with rich experience in wireless network,our router series include high power router、gigabit WiFi router、smart WiFi router with management APP,dual band and tri band WiFi router.The mesh network router with Touchlink function. What's new with Weblink 5.0? New user-friendly interface; Install type selection by starter and/or alarm make and model; Save your favorite configurations for one-click flashing.

What is the ADS-USB / Weblink?

Weblink is the programming system used to program remote starters and interface modules manufactured by iDatalink, iDatastart, and Compustar.

iDatalink, iDatastart, and Compustar data enabled controllers require firmware flashing before installation. Many times we (Lockdown Security) will complete this for you BEFORE we ship the item to you, however there are certain circumstances where we do NOT do this before we ship (vehicles that require KLON).

The ADS-USB is the physical tool used to connect your computer, to the interface module or remote starter. It is essentially a USB bridge tool, it acts as the bridge between the computer and the device being programmed. See the image below for what the ADS-USB looks like:

ADS-USB and ADS-USB ECO What's The Difference


The ADS-USB is the legacy full sized tool, it is capable of flashing (programming) all iDatalink, iDatastart, and Compustar product. It is also capable of programming iDatastart antennas


The ADS-USB-ECO is the new smaller sized alternative (with a lower price) that can program:
iDatastart HC Series Modules (HCX)

iDatastart CHX, GMX, MIX, VWX, BMX Modules

Compustar DC3 modules

We have discovered it cannot program:

iDatastart Antennas

Internet Explorer Windows PC

First and foremost, in order to use the ADS-USB you must have a Windows PC (personal computer). You cannot use the ADS-USB on an Apple Mac computer. If you are using Windows 10 and your default browser is Microsoft Edge, see the link below for how to launch Internet Explorer in Windows 10.
Internet Explorer How to Launch in Windows 10

How to Flash (Program) Firmware

Weblink Usb Driver

*Note* We recommend you always flash your controller or interface OUT of the vehicle, at the very least if you decide to do the firmware flash or option change from within the vehicle, your controller or interface must be completely unplugged from all vehicle connections*

The simplest breakdown on how to flash the firmware would be:

STEP 1: Create/Register a Weblink user ID via www.idatalink.com
STEP 2: Plug the ADS-USB Weblink Updater into your Windows PC *MUST USE Windows PC*
STEP 3: Visit www.idatalink.com using INTERNET EXPLORER * MUST USE INTERNET EXPLORER, not Edge, not Google Chrome, ONLY Internet Explorer
STEP 4: Plug the remote start controller or interface module into the ADS-USB via the black 4 pin RS232 port (on the controller or interface)
NOTE: The controller or interface must be UNPLUGGED completely from the vehicle, no power from the vehicle can be going to the controller or interface

STEP 5: Use the Flash Your Module button on www.idatalink.com , log-in, then flash your module according to your vehicle make/model/year.

KLON (pronounced CLONE) What is it?

KLON is an iDatalink/iDatastart programming procedure that eliminates the need to sacrifice an expensive key or key-fob for your vehicle, when installing a remote starter.


Learn more about it HERE

Lockdown Security Refund Policy (on Weblink ADS-USB Device)

If the product you have ordered requires a 2 step programming (flash) process (1 before we ship and a 2nd after install is completed) OR if options need to be enabled/disabled to get the product to work, you MUST buy a Weblink/ADS-USB tool.

Lockdown Security will sell you the tool and ship with your order, and offer you the option within 90 days of purchase to send the tool back to us, for a full refund. You can use the tool for your requirements, get your product working, then feel free to ship the tool back to us for a refund of the tool cost. Or you may feel free to keep the tool, it is your choice.
Shipping costs to get the tool back to Lockdown Security are your (the buyer) responsibility and are non-refundable.

Have you had difficulty using a USB to RS-232 adapter to connect your RS-232 device to a computer? If so, you are not alone. Our customers frequently encounter issues with these adapters. In this article, I’ll briefly discuss the origin of these issues and provide you with some suggestions for successfully handling them.

The Evolution from RS-232 to USB

In the old days of personal computers, one of the primary connections available was the RS-232 serial port. Apart from the parallel port, it was the primary means to connect an external device. The connector was reduced from a 25-pin connector to a 9-pin connector, but RS-232 ports remained present on every computer for many years. Built-in RS-232 ports featured direct mapping to memory and worked at a high priority. Data practically flowed directly to and from the software that was accessing the serial port.

In 1996, the Universal Serial Bus (USB) standard was introduced as a replacement for the serial connector and other connector types that were typically found on the back of computers. The USB provided smaller connectors and more data throughput than the serial and parallel interfaces it replaced.

USB devices have high throughput, but they use a shared data bus. Data is wrapped up and transferred in packets. To handle the packets and move data in and out of the program accessing the USB device, a software driver is needed. The software driver sits between the hardware and the computer program you are using, and it must be installed and working correctly.

The Necessity of an Adapter

With the widespread adoption of USB, most computers sold now do not have an RS-232 port. Therefore, to connect an RS-232 device (such as a CR1000) to a computer, you need to use a USB to RS-232 adapter, such as the 17394 converter.

While USB to RS-232 adapters perform a necessary function, they do have some limitations. For example, there are three types of problems that you may encounter when using a USB to RS-232 adapter:

  • Driver issues
  • Hardware issues
  • Performance issues

Issue #1: Driver

The most common problem that our customers encounter with a USB to RS-232 adapter is getting the proper driver installed. The driver must correspond to the chip inside the cable—not to the manufacturer of the cable.

For USB to RS-232 chips, there are two primary manufacturers: Prolific and FTDI. Because off-brand chips with poor drivers are unreliable, Campbell Scientific recommends and currently sells a cable using an FTDI chip (part number 17394). We chose this cable because it uses a chip that has a certified driver available on Windows Update. (The older cables were silver in color and did not have a driver available for Windows beyond version 7.)

Tip: Test your USB adapters in the office with your field computer. When you are in the field, your computer won’t have an Internet connection to automatically download and install the driver.

If the driver for your adapter is not automatically installed or cannot be installed from a CD, you will need to identify the chip in your cable and locate the driver on the Internet. Some manufacturers identify on their packaging which chip is used inside their cable. You can also identify a cable’s chip from the Windows Device Manager by following these steps:

  1. In the Windows Device Manager, right-click your device from the list.
  2. In the drop-down menu that opens, select Properties.
  3. In the Properties dialog box, select the Details tab.
  4. In the Property field, select Hardware Ids from the drop-down menu.
  5. In the Value field, there is both a VID (Vendor ID) and a PID (Product ID). These IDs respectively indicate the manufacturer and the model number of the chip.
  6. In the example above, I did a quick Internet search for VID 0403 PID 6011, which revealed to me that the chip is an FT4232 manufactured by FTDI.
  7. After you know your chip type and manufacturer, you can locate and download the correct driver for your version of Windows.

Issue #2: Hardware

USB to RS-232 adapters are commodity pieces of computer equipment. As much as we all wish that everything was as reliable as the CR1000, all adapter cables eventually fail.

Although there are two primary companies that manufacture USB to RS-232 adapter chips, there are many cable manufacturers who offer varying levels of cable quality.

  • Higher-quality, industrial models should last longer, but they wear out over time—just like any field tool.
  • A poorly constructed cable could have components that fail in a short period of time—perhaps even by the time you receive the cable.

I have seen several cases where old cables could no longer handle 115200 baud, but the cables still worked on low baud rates. There have been many more cases where a USB cable stopped working half-way through a day in the field.

Tip: If your field site is far from your office, take two USB to RS-232 cables with you. Lost time in the field can be a lot more costly than the purchase price of a second cable.

Issue #3: Performance

As mentioned previously, USB uses a shared data bus with packetized communication. The packetized communication introduced some latency (data transfer time) that wasn’t present with built-in RS-232 ports. Unfortunately, latency makes a noticeable difference when you download large amounts of data or upload a new operating system.

The driver for FTDI chips allows you to lower the latency time on packets. To do this, you can use the Latency Timer field, which is accessed through the Windows Device Manager. Follow these steps:

  1. From the Windows Device Manager, right-click your device from the list.
  2. In the drop-down menu that opens, select Properties.
  3. Click the Port Settings tab.
  4. Click the Advanced… button.
  5. In the Advanced Settings window, navigate to the Latency Timer field, and reduce the setting to 1 for best performance.

In addition to lowering your latency time, I also recommend disabling the Selective Suspend option for your cable. The Selective Suspend option allows Windows to put your hardware to sleep, which can result in corrupt data packets. To disable the Selective Suspend option, clear the checkbox for the Enable Selective Suspend field on the Advanced Settings window for your device.

Note: The Selective Suspend option is already disabled by default in the FTDI driver.


Newer data logger designs, such as the CR6, feature a native USB connection. Many devices, however, will feature RS-232 connections for years to come, and we’ll need to continue using USB to RS-232 adapter cables. I hope the suggestions I’ve provided help. Feel free to share any USB to RS-232 issues that you have encountered by posting a comment below.