1. Autocom Port Devices Driver Updater
2. Autocom Port Devices Drivers
3. Autocom Port Devices Driver
4. Autocom Port Devices Driver Device
5. Autocom Port Devices Driver Tp-link

This little tutorial shows you how to Change Autocom or Delph diagnostic softwares VCIi ComPort settings. We're commited to making this website a starting point for any device driver search. Vci diagnostic tool for winodws 8. Man cats autocom path to your hardware. Free download ism malayalam typing software. Autocom/delphi 2017 crack download, instal activator directly,.autocom/delphi 2017 crack how to install and activate autocom 2013.1 software. Corrupted By Driver Autocom Cdp Usb: Input Devices: Logitech USB Input Device (Logitech Download Assistant) Corrupted By Driver Autocom Cdp Usb: Port Devices: MediaTek MediaTek PreLoader USB VCOM Port (COM51) Up To Date and Functioning: Monitors: Sony Digital Flat Panel (1024x768) Corrupted By Driver Autocom Cdp Usb: Mobile Phones And Portable.

I seem to be using the correct com port OBD11 paired with 1234 Device manager says OBDII exists and is working Device manager says Port (Com & LPT) Standard Serial over Bluetooth link (Com17/Com18) and is upto date. The Multidiag Pro system says that the Com17/18(BT) Unknown device. When I click test connection in the event log I see.

• Active USB-COM Port Driver

Active USB-COM Port Driver

Model：Scanners, CUs, BHT series

File Name	Date of Update
Active USB-COM Port Driver Ver.2.2.0.0 R2 (4,159KB)	01/25/2021

Read me:Features of the Active USB-COM Port Driver

Supporting OS

Supporting OS is as following Microsoft Windows® OS.

• •Microsoft Windows® 7 (32bit version / 64bit version)
• •Microsoft Windows® 8.1 (32bit version / 64bit version)
• •Microsoft Windows® 10 (32bit version / 64bit version)(Only the following Version number)
• •Version 1803 (April 2018 Update, Enterprise or Education edition only)
• •Version 1809 (October 2018 Update, Enterprise or Education edition only)
• •Version 1903 (May 2019 Update)
• •Version 1909 (November 2019 Update)
• •Version 2004 (May 2020 Update)
• •Microsoft Windows® 10 IoT Enterprise 2016 LTSB(64bit version)
• •Microsoft Windows® 10 IoT Enterprise 2019 LTSC(64bit version)

Note of using with Windows® 10 IoT Enterprise

　Windows® 10 IoT Enterprise is a Windows® 10 embedded OS.We tested it with our environment, but it does not guarantee your any operational environment.
Please test in enough to be no trouble with your operational environment, and use it.

Note of using with Windows® 10

　Windows standard driver will be loaded if you inserted the USB device in the USB port of the PC with Windows® 10 which
does not install Active USB-COM Port Driver. The USB device does not support the operation with the Windows standard
driver.
Please use it after installing Active USB-COM Port Driver by all means.

Version	Updated contents	Updated on
2.2.0.0 R2	(1)The installer is changed. [TIP] •The device driver files in this version are the same files in 2.2.0.0.	Jan 25, 2021
2.2.0.0	(1)The following Windows OS is supported. •Windows 10 Version 2004 (May 2020 Update) (32 bit version/ 64 bit version) (2)COM communication from UWP applications is supported. (Note: Not supporting the execution of setup and ancillary tools in the S mode in Windows 10.) (3)The detection of USB device connection/disconnection status using DSR signals from applications is supported.	Dec 01, 2020
2.1.0.6	(1)The following Windows OS is supported. •Windows 10 Version 1909(November 2019 Update) (32 bit version/ 64 bit version)	Apr 03, 2020
2.1.0.5	(1)The following Windows OS is supported. •Windows 10 Version 1903(May 2019 Update) (32 bit version/ 64 bit version) (2)the installer, uninstaller, and log collection tool are improved.	Oct 25, 2019
2.1.0.4	(1)The installer and uninstaller are improved. (2)The uninstaller and the log collection tool to use in case of installation failure are provided. [Tips] •The each device driver file in the new version is the same version as it in the current version. If you have already installed 2.1.0.4 on your PC, you do not need to update. •From this version, the Supporting OS of Windows 10 IoT Enterprise are as follows. [Before] 2015 LTSB 64bit 2016 LTSB 64bit [After] 2016 LTSB 64bit 2019 LTSC 64bit	Jul 30, 2019
2.1.0.4	(1)The following Windows OS is supported. •Windows 10 Version 1809(October 2018 Update) (32 bit version/ 64 bit version) (2)The installer and uninstaller are changed. (3)The support tools for the driver are provided.	May 27, 2019
2.1.0.3	(1)The following Windows OSes have been supported. •Windows 10 Version 1803 (April 2018 Update) (32 bit version/ 64 bit version) (2)Processing when PC power was turned off was improved. [Tip] You can install or uninstall the driver with our USB product inserted. Please be sure to read the notes on use in the included installation guide.	Aug 21, 2018
2.1.0.1	(1)The following Windows® OSes have been supported. •Windows® 10 Version 1703 (Creators Update) (32 bit version/ 64 bit version) •Windows® 10 Version 1709 (Fall Creators Update) (32 bit version/ 64 bit version) •Windows® 10 IoT Enterprise 2016 LTSB (64 bit version)	Jan 10, 2018
2.1.0.0	(1)This driver has been adapted for use on Windows® 10 IoT Enterprise 2015 LTSB (64bit version).	Mar 30, 2017
2.0.1.8	(1)Windows 10 (32-bit/64-bit version) is supported.	Apr 19,2016
2.0.1.5	(1)The disconnection and connection processing of the USB device has been improved.	May 28,2015
2.0.1.3	(1)The disconnection and connection processing of the USB device has been improved. (2)The start processing of the PC that the USB device is connected has been improved. (3)The driver installation processing in the USB device connection has been improved.	Jan 09,2015
2.0.1.0	(1)Windows 8.1 (32-bit/64-bit version) is supported. (2)Improvements have been made through processes when the COM port is open. (3)The process of transferring data to the USB device has been improved.	Feb 17,2014
2.0.0.23	(1) Improved to support the function that can automatically resume COM communication. Note: Users are strongly recommended to use the upgraded version 2.0.0.23.	Aug 23,2013
2.0.0.22	(1)There was a case in the current version that data communication was not started even though the BHT was reconnected if the USB device was determined to be removed from the USB port in the process of data transmission. This is improved and fixed in the new version. (2)There was a case in the current version, though it was very rare, that the USB host controller on the PC did not respond to the request command from the driver, which as a result caused a BSoD. This is improved and fixed in the new version.	Jul 11,2013
2.0.0.20	(1)Windows 8 (32-bit/64-bit version) is supported. (2)The phenomenon in which the application on the PC side was changed to a “No response” state on rare occasions is improved.	Apr 08,2013
2.0.0.18	(1)Improved the process of removing the USB device from the PC. (2)Improved the process of opening the COM port.	Dec 05,2012
2.0.0.16	In configuration that the Active USB-COM Port Driver is used between the BA series and the QR-kbif, when the QR-kbif was activated with the “-d” option and tries to connect the scanner, the processing of the Active USB-COM Port Driver has been improved.	Apr 09,2012
2.0.0.13	(1) The phenomenon, in which the communication application on the PC side became unresponsive during data transfer on rare occasions, is improved in the new version.	Nov 04,2011
2.0.0.12	(1)Supported for Windows7 64bit version. (2)Improved the data reception processing from the USB device. (3)Improved the processing when the USB device is connected.	Sep 01,2010
2.0.0.10	(1)Supported for Windows 7（32bit version) (2)Improved reconnection process in case of losing the connection with USB device.	Jan 20,2010
2.0.0.7	(1)Improved the process of executing opening /closing COM port in application software in disconnecting USB device.	Jan 19,2009
2.0.0.6	(1)Support Windows Vista (32bit). (2)Added the displaying information of the 'safty remove hardware' icon on the task-tray.	Aug 31,2007
2.0.0.4	(1)Released for CU-221/CU-421 to use MS ActiveSync with MS infrared driver.	Aug 25,2006

Note about version up of Windows

　If you want to upgrade your Windows PC that installed the Active USB-COM Port Driver to the new version of Windows,
please implement the following　steps.

• •STEP1:Before you upgrade the Windows PC, please uninstall the Active USB-COM Port Driver.
• •STEP2:Please upgrade the version of Windows.
• •STEP3:Please install the Active USB-COM Port Driver.

How to install Active USB-COM Port Driver

　1. Uninstall the old version's driver

Autocom Port Devices Driver Updater

Please uninstall the old version's Active USB-COM Port Driver by the use of the Windows Control Panel “Programs and
Functions” as the Administrator.

　2. Extract the installation file

Please extract the downloaded file 'ActiveUSBCOM_xxxx_E.ZIP'. (xxxx is its version.)

　3. Install the Active USB-COM Port Driver

Please install the installer program as the Administrator, referring to the installation manual.

Features of the Active USB-COM Port Driver

　1.Features:

• The USB device can be removed from the PC USB Port while the application opens the Serial Port with which the USB
• device is connected.
• (It will be kept opening when the USB device is plugged into the USB Port again.)
• The Virtual Serial Port is always existed on PC even if USB device is removed from the PC USB Port, so that the Serial Port
• can be opened anytime.
• On the task tray or the Device Manager, the COM port is confirmed which port the USB device is connected with.

2.Supported Devices:

Please confirm supported models from our product pages.

　3.Notice:

• •Before installation of this driver, please read the precaution statement written in the user's guide included in the downloaded file.

Autocom Port Devices Drivers

Contact us

QBdirect

If you have not registered

The services on this member site are available only for registered customers.

I have some problems with two different types AUTOCOMS CDP+. PCB was different type and both have a problems with message VCI not found. They both using same procesor STM32F205ZGT6 same shematic but different layout. Autocom with 2 PCB (main pcb + relay pcb) is better quality from autocom with only one double layer PCB. The second one has already printed test points to make connections to upgrade firmware.

To repair your broken Autocom with this kind of processor is really easy only you need:
– wires
– solder iron
– Flash_Loader_Demonstrator
– firmware
– some electronic skiils

Procedures:

1.Install Flash_Loader_Demonstrator

2.make wire connection between VDD (pin1 from J400) and pin138 BOOT0 from STM32F20XXX – for Autocom pcb V 3.0 or between TP102 (VDD) and TP206 – for Autocom class B

3.put a switch between pin9 and pin10 from J400 (this connection is needed to join short time NRST to GND – make resset)

4.connect Autocom to car (or external 12v) and USB to computer

5.start Flash_Loader_Demonstrator and dont change anything in settings just select yout VCI port number

6.connection wire is between VDD and BOOT0 (step2) all time while upgrating firmware

7.After Flash_Loader_Demonstrator window is appear then made short connection between pin 9 and pin 10 from J400 (look at pictures)

8.If everything is OK then next window will be avaliable in Flash Loader Demonstrator

9.When connection with MCU is avaliable, you need choose type of MCU 1024K

Autocom Port Devices Driver

10.Select your firmware ex. 2012.3.bin from download to device option and global erase

11.Click next and wait about 7 min for uploading your firmware to Autocom

12.After uploading firmware finished just disconect Autocom from OBD2 and USB and connect it again and make test and you will be suprised your Autocom is live again

Autocom Port Devices Driver Device

All files and documentation is here
I hope this post was helpfull for all people having problems with Autocom chinese clones.

Autocom Port Devices Driver Tp-link