Andrew,

I followed the steps. I’m now seeing Device Manager continually rescanning for hardware and not finding anything.

Earlier I saw the message “Unknown USB Device (Device Descriptor Request Failed).

I also installed the same hardware/software on my wife’s computer (new Windows 10 machine) and everything worked flawlessly.

It might be possible to hook a scope across the data lines. Would that be worth anything?

Thanks again for your help.

Bruce

Andrew and Justin,

Thanks for your help. I upgraded the driver from 2.12.24 to 2.12.26 in accordance with FTDI’s instructions and verified that I’m using a good USB cable. Windows is in High Performance mode.

When I connect the SA44B to the USB port I get a Windows message “USB Device Not Recognized – The last device you connected to the computer malfunctioned, and Windows does not recognize it” The LED on the front of the SA44B flashes orange every once in a while and is off the rest of the time. I have tried this with multiple USB ports on the computer with the same results. I’m now seeing a problem before even opening Spike.

Now here is where it gets strange. If I connect the SA44B to my computer through a cheap USB hub the SA44B LED is solid green and USB Serial Converter A/B show up in the Device Manager. No complaints from Windows. Spike attempts to connect with the SA44B (Connecting to Device, wait 6 sec message along with installation bar). That ends without any error messages. About 6 sec after the Connecting to Device message disappears Spike announces that there is no device connected. I can see my SA44B listed in the File/Connect menu.

It would seem that my computer is unable to keep up with the SA44B (I’m assuming that the USB hub is slowing everything down). The computer is about two years old (newer than the computer that the SA44B does run on). I don’t believe that I’ve ever had the SA44B running on this machine.

Thanks for your help,
Bruce

I’ve got a similar problem. I have two Windows 10 machines. My SA44B works just fine on one, but I can’t run it on the other. I’m getting a “Device Connection Issues Detected, Ensure the device is connected before opening again via File Menu” message from Spike. Interestingly, the File/Connect menu lists my device SA44/124: 3000329.

————————–
Spike 3.1.7
BB API Version 3.0.19
SA API Version 3.0.18

Windows 10 Home Version 1703 (KB4025376)
i7-4790K CPU

CDM v2.12.00 WHQL Certified.exe
————————–

Device Manager lists
USB Serial Converter A
USB Serial Converter B

Load VCP unchecked
Driver => FTDI 2.12.24.0

————————–
and here’s some output from the Windows EventViewer

Device USB\VID_0403&PID_6010&MI_00\7&21d6526d&0&0000 requires further installation.

Device USB\VID_0403&PID_6010&MI_01\7&21d6526d&0&0001 was started.

Driver Name: oem8.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Service: FTDIBUS
Lower Filters:
Upper Filters:

Device USB\VID_0403&PID_6010&MI_01\7&21d6526d&0&0001 was configured.

Driver Name: oem8.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Driver Date: 09/28/2016
Driver Version: 2.12.24.0
Driver Provider: FTDI
Driver Section: FtdiBus.NTamd64
Driver Rank: 0xFF0001
Matching Device Id: USB\VID_0403&PID_6010&MI_01
Outranked Drivers: oem17.inf:USB\VID_0403&PID_6010&MI_01:00FF0001 oem19.inf:USB\VID_0403&PID_6010&MI_01:00FF0001 oem23.inf:USB\VID_0403&PID_6010&MI_01:00FF0001
Device Updated: false
Parent Device: USB\VID_0403&PID_6010\03000329

Device USB\VID_0403&PID_6010&MI_01\7&21d6526d&0&0001 was migrated.

Last Device Instance Id: USB\VID_0403&PID_6010&MI_01\7&21d6526d&0&0001
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path:
Migration Rank: 0x0
Present: false

Device USB\VID_0403&PID_6010&MI_01\7&21d6526d&0&0001 requires further installation.

————————–
The Device Manager data looks the same on both computers, so I’m suspicious of Windows settings, especially any related to the virtual com port.

I’ve also shutdown any antivirus software.

Any thoughts or suggestions will be greatly appreciated.

tia,
Bruce Raymond

[Author]

Posts