Any likelihood Of DSDPlus adding support for HydraSDR that has the updated firmware? SDRTrunk has that in the pipeline --
View attachment 197649
...
Removing the serial # and running -i0 in FMPA-CC.bat (instead of -i1) works for me. I'm able to use the Hydras in DSDPlus. I imagine down the road that'll be "fixed". But for now they are certainly usable if you are willing to play by a different set of rules![]()
I had tried that before after removing the ser # from the cfg but received the -I0 invalid message upon startup. I removed the -I all together from the cc bat and it works fine.
Does this still allow for CC following and tracking a voice call in one dongle (i.e. just like the Airspy with FMPA)?So when the Airspy DLL is asked to open a specific device (by serial
number), the DLL fails to open the HydraSDR One.
When the Airspy DLL is asked to just open whatever it can find, it works
fine.
Removing the serial # and running -i0 in FMPA-CC.bat (instead of -i1) works for me. I'm able to use the Hydras in DSDPlus. I imagine down the road that'll be "fixed". But for now they are certainly usable if you are willing to play by a different set of rules![]()
Yes. Operates just the same.Does this still allow for CC following and tracking a voice call in one dongle (i.e. just like the Airspy with FMPA)?
My Airspy recently died after several years (no idea why); if the Hydra works with DSD Plus I would love to try it out.
I haven't tried the official release versions of gr-osmosdr recently, but back in the early days of HydraSDR you definitely needed to use my patched version (GitHub - boatbod/gr-osmosdr: Mirrored from https://gitea.osmocom.org/sdr/gr-osmosdr) for the Hydra to work similar to an Airspy under linux. I'd suggest trying the official versions first, and if no luck with those, flip over to mine. With mine you can run multiple hydras and identify by serial number etc.I'm hoping it also works good with OP25 and SDR++ in Linux.