-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add FCD support #6
Comments
The reason fcd source isnt supported yet is that the fcd and fcdplus are sort of outliers here. The fcd source in gr-osmosdr is just an empty block that is calling out to two external projects: They arent very complicated blocks. It might be worth it for the manufacturer to make a dedicated fcd wrapper. Thats a best case, but short of that I might be able to copy in those two source trees and cobble something together. But I would need help testing as I dont have a fcd. |
Thank you very much! I am willingly to support you with testing the fcd stuff. |
So this also pulls in all of gr-audio which is yet another even larger project. I was thinking, there is actually a soapy sdr project for audio devices, and it has hamlib support. So it might be better suited, though perhaps it might need some hooks to call the right things in hamlib.
@cjcliffe what do you think? Soapy audio for funcube w/ hamlib support. |
I tried today the SoapyAudio part. Long explanation: Audio works, but the hamblib part does not support the FCD correctly, it requires but rigctl does not require rate or port when using rigctl -m 2513 because the FCD is working as a USB sound card and hid interface @cjcliffe The audio part works, but I need to do an I/Q calibration, any pointers how this goes into the SoapyAudioblock? I think basically we could close this issue here and I can make a new one for the hamlib stuff in SoapyAudio |
@LongnoseRob not sure; I assumed hamlib would ignore those parameters if the device didn't use them; is it failing to open the device like that? Also are you using the latest hamlib from GitHub? There are many recent devices in there that weren't in the port supplied OSX version. Feel free to open up some issues at SoapyAudio; I think I'm going to get the sample offset thing fixed this weekend at least so I'll be in there tinkering. |
@cjcliffe |
I'm try to use four FCD pro on remote PC via CubicSDR/SoapyRemote/SoapyAudio:
|
@bdn76 There are some keyword arguments for SoapyAudio like rig, rig_port, rig_rate. I believe that these can be used to select the correct device and its parameters (not totally sure I dont have an FCD to test with). And you should be able to pass these same arguments through SoapyRemote.
|
Ok, thank you. [https://github.com/pothosware/SoapyAudio/issues/9] issue. |
I think you can close this one: |
Would be nice ot have funcube dongle also supported by SoapyOsmo.
I am trying to use SoapyOsmo&Remote for having a small ARM system running with the FCD attached at a good RF location and streaming the data over the netowrk to my main computer.
But unfortunately the fcd is not yet supported by SoapyOsmo/
The text was updated successfully, but these errors were encountered: