Reply To: Cannot connect SA44B with Spike

Forums SA Series Discussions Cannot connect SA44B with Spike Reply To: Cannot connect SA44B with Spike

#156689
AttilaTheHun
Participant

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