Forums › BB Series Discussions › Connection issues
- This topic has 2 replies, 2 voices, and was last updated 7 years, 9 months ago by
abaker.
- AuthorPosts
abakerParticipantI have a Starcom USB3 PCIe card that I had installed in an old Kontron PC under Win7 and Spike ran OK. That machine has moved on and I have since tried two other machines without success.
My current machine is a Dell R160 server running Windows 7 64-bit. The card installed OK and the BB60C has its green LED on, but Spike can’t find the device”No device found”.
I read the FAQ but didn’t really understand which USB libraries might need re-installing. The driver for the Starcom card worked in another machine… My processor is an “Intel(R) Xeon(R) CPU E5620” which didn’t seem to tie up with anything in the FAQ?
All guidance greatly received – except maybe “buy a newer machine!”
Thanks
:0)
AndrewModeratorHello Abaker,
The USB drivers we link in the FAQ are specifically for the various Intel CPUs that support USB 3.0. If you are using an external card, then those drivers won’t be applicable. We recommend a class of Intel CPUs (4th generation or later i5/i7’s) because they implement USB 3.0 support in hardware that has proven to work at the sustained throughput we need (Typically referred to as native USB 3.0 support). We have a poor track record with external cards and third party USB 3.0 vendors such as Renesas and ASMedia.
Since the card has worked for you in the past, it might be that you need to find the latest drivers for the card. Or it might be the card isn’t going to work in combination with this PC. The Xeon processor you linked was made before the Native USB 3.0 push from Intel and widespread USB 3.0 adoption on PC hardware.
Regardless, both the CPU and the external card are outside the minimum recommended PC requirements, and I suspect this is why you are seeing the “Device Not Found” error message.
Let me know if you have additional questions.
Regards,
Andrew
abakerParticipantThanks for your detailed replay :0(
Andrew- AuthorPosts
You must be logged in to reply to this topic.