Forum Replies Created
- Posts
Somehow my previous post got lost. Using a separate power supply didn’t help, so it seemed clearly a software issue.
I just installed Spike with accompanied driver on a laptop to see how that behaves. That setup works as expected 🙂
Probably there is still something on the desktop PC interfering with the FTDI drivers. Anyway the fact it works on the desktop at least shows there is no driver/software/SA incompatibility.
I will do some more investigation trying to find out why the same configuration does not work on the desktop PC.
Thanks for your reply.
The VCP I was aware of, it is disabled. I tried it both on an external powered USB HUB as well as direct on a desktop PC (behavior the same)
To exclude any power issues I just slightly modified my USB cable (Didn’t have a Y cable) and powered it by a R&S PSU (set to 5.2V/1A) (cable length to SA approx. 40cm so it is very unlikely to drop be below 5V at the unit (or is the inrush current that high ?)
Removed all the FTDI stuff from the PC, installed the driver included with Spike (“CDM v2.12.00 WHQL Certified.exe”)
Only “USB serial converter A” showed up under “Universal serial bus controllers”
(this is consistently: connect/reconnect as well as power cycle several times)Next installed the very old FTDI driver (without disconnecting the unit and power) and “USB serial converter B” appeared. (after which the old Signal hound software detects the device, but Spike doesn’t)
Therefore it really seems to be software related.
