Problem solved!
Basically using wrong drivers... I found another link that provided a set of drivers for a 64 bit PC.
I followed the same instructions as in afore mentioned video and it worked!
I can't post URL as is, but this might work:-
http COLON // www DOT ja DOT axxs DOT net/ftdi_driver_install DOT htm
If not search for some of this:-
KMX1 and KMX2 use an FTDI USB chip for the USB connection to your PC.
Usually Windows automatically installs FTDI VCP [Virtual COM Port] drivers however with some batches of FTDI chips the default windows drivers do NOT work. The latest version of FTDI VCP drivers also do NOT work and FTDI seem oblivious of that fact.
The previous version of FTDI VCP drivers does appear to work with all batches of FTDI chips.
When the FTDI drivers do not work with a particular batch of FTDI chips the Virtual Com Port will appear in Windows Device Manager however serial communications will not work
To rectify this situation
You need to download the;
FTDI software driver for Windows x86 CDM 202.08.28 WHQL 20Certified
FTDI software driver for Windows x64 CDM 202.08.28 20WHQL 20Certified
Basically using wrong drivers... I found another link that provided a set of drivers for a 64 bit PC.
I followed the same instructions as in afore mentioned video and it worked!
I can't post URL as is, but this might work:-
http COLON // www DOT ja DOT axxs DOT net/ftdi_driver_install DOT htm
If not search for some of this:-
KMX1 and KMX2 use an FTDI USB chip for the USB connection to your PC.
Usually Windows automatically installs FTDI VCP [Virtual COM Port] drivers however with some batches of FTDI chips the default windows drivers do NOT work. The latest version of FTDI VCP drivers also do NOT work and FTDI seem oblivious of that fact.
The previous version of FTDI VCP drivers does appear to work with all batches of FTDI chips.
When the FTDI drivers do not work with a particular batch of FTDI chips the Virtual Com Port will appear in Windows Device Manager however serial communications will not work
To rectify this situation
You need to download the;
FTDI software driver for Windows x86 CDM 202.08.28 WHQL 20Certified
FTDI software driver for Windows x64 CDM 202.08.28 20WHQL 20Certified
ASIX High-Speed USB Serial Port Driver 3.18.1.0 for Windows 10 Creators Update 64-bit 509 downloads. Other Drivers & Tools ASIX. Windows 10 64 bit. Jun 8th 2017, 19. The problem I have is our hardware is a usb to serial board and it has several serial port and using usbser.sys as the driver. It shows up in device manager as com9, com10, com11, com12. When power for the board disconnect or the usb connection from the host computer disconnects the com port will disappear from device manager. HP USB to Serial Port Adapter Choose a different product Warranty status: Unspecified - Check warranty status Manufacturer warranty has expired - See details Covered under Manufacturer warranty Covered under Extended warranty, months remaining month remaining days remaining day remaining. Drivers Library To find the latest driver for your computer we recommend running our Free Driver Scan. Prolific USB-to-Serial Comm Port (COM4) - Driver Download.
![Octopus Octopus](/uploads/1/1/9/8/119877699/735393495.jpg)
![Octopus Usb Serial Port Driver Octopus Usb Serial Port Driver](/uploads/1/1/9/8/119877699/531806309.jpg)
Octopus Usb Serial Port Driver Windows 10 X64
Problem solved!
Basically using wrong drivers... I found another link that provided a set of drivers for a 64 bit PC.
I followed the same instructions as in afore mentioned video and it worked!
I can't post URL as is, but this might work:-
http COLON // www DOT ja DOT axxs DOT net/ftdi_driver_install DOT htm
If not search for some of this:-
KMX1 and KMX2 use an FTDI USB chip for the USB connection to your PC.
Usually Windows automatically installs FTDI VCP [Virtual COM Port] drivers however with some batches of FTDI chips the default windows drivers do NOT work. The latest version of FTDI VCP drivers also do NOT work and FTDI seem oblivious of that fact.
The previous version of FTDI VCP drivers does appear to work with all batches of FTDI chips.
When the FTDI drivers do not work with a particular batch of FTDI chips the Virtual Com Port will appear in Windows Device Manager however serial communications will not work
To rectify this situation
You need to download the;
FTDI software driver for Windows x86 CDM 202.08.28 WHQL 20Certified
FTDI software driver for Windows x64 CDM 202.08.28 20WHQL 20Certified
Basically using wrong drivers... I found another link that provided a set of drivers for a 64 bit PC.
I followed the same instructions as in afore mentioned video and it worked!
I can't post URL as is, but this might work:-
http COLON // www DOT ja DOT axxs DOT net/ftdi_driver_install DOT htm
If not search for some of this:-
KMX1 and KMX2 use an FTDI USB chip for the USB connection to your PC.
Usually Windows automatically installs FTDI VCP [Virtual COM Port] drivers however with some batches of FTDI chips the default windows drivers do NOT work. The latest version of FTDI VCP drivers also do NOT work and FTDI seem oblivious of that fact.
The previous version of FTDI VCP drivers does appear to work with all batches of FTDI chips.
When the FTDI drivers do not work with a particular batch of FTDI chips the Virtual Com Port will appear in Windows Device Manager however serial communications will not work
To rectify this situation
You need to download the;
FTDI software driver for Windows x86 CDM 202.08.28 WHQL 20Certified
FTDI software driver for Windows x64 CDM 202.08.28 20WHQL 20Certified