Also, Ross-Tech states that the HEX-CAN-USB only works with VCDS because it does not support COM ports. The NefMoto software communicates with the USB chip via the FTDI SDK and does not require COM port support, and so it works great with the HEX-CAN-USB.
Does this also mean that you do not need to install the virtual COM port drivers? I am having similar problems to other users with my genuine HEX-CAN-USB cable, there is no echo from the FTDI chip:
LOG: Opened NefMoto VW Audi ME7 ECU Flasher BETA 1.9.1.2
LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
LOG: Opened FTDI device.
LOG: FTDI device info - Description: Ross-Tech HEX-USB Serial Number: RT000001 Device Type: FT_DEVICE_232R ID: 0x403FA30 Device Flags: 0x0
LOG: FTDI ChipID DLL is loaded, checking chip ID...
LOG: FTDI device chip ID: 0xD4FFC445
USER: Failed to read test echo from FTDI device.
LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
LOG: Closing FTDI device.
LOG: Could not open FTDI device
Incidentally, I have also tried installing the VCP drivers to see if that was the problem. My lead was still able to communicate with the ECM via VCDS but I still had no joy with NefMoto. Same error as above.