[Robert Bowmaker]

Just wanted to make a note that I’ve got this working, very rough code is available here:

https://github.com/Hueburtsonly/doppler

On my computer, I had absolutely no luck with libftd2xx, which is the official FTDI library, the one included with the Signal Hound drivers (it simply couldn’t find the virtual COM port, even though lsusb was listing it). However libftdi, the alternate version of the same library, worked flawlessly straight away. So for Linux I’d recommend libftdi to other customers, as well as the dev staff at Signal Hound.

• This reply was modified 8 years, 5 months ago by Robert Bowmaker.

Justin,

One might have been doing a bit of snooping last night after sending your message, and figured out a couple of those details! I very much appreciate the hints, that completes the picture nicely.

To answer your question, my particular use case requires CW (so one might say I have everything I need), but of course it would be wonderful if scalar sweeps worked as well.

Thank you so much!

I’m also having no luck calling bbAttachTg; it returns -14 [bbDeviceConnectionErr] whether the TG is plugged in or not. For reference, lsusb has this listed for the TG:

Bus 003 Device 036: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC

Any suggestions would be greatly appreciated.

I’d love to help out in any way possible, having written both USB firmware and software in the past — although of course I’m slightly limited in my ability to debug binary libraries! I’ve attached the dmesg output while the TG is plugged in, in case it helps.

Attachments:

You must be logged in to view attached files.

[Author]

Posts