Closed antigraviton closed 8 years ago
update: issues fixed with:
The firmware issue will be solved (eventually) in SoapyOsmo I expect (bit packing added to firmware)
Absence of gain controls (we have 3 for the airspy), makes it unusable unfortunately: [-v vga_gain]: Set VGA/IF gain, 0-15 (default 5) [-m mixer_gain]: Set Mixer gain, 0-15 (default 5) [-l lna_gain]: Set LNA gain, 0-14 (default 1)
Setting other defaults in SoapyOsmo (gr-osmosdr/lib/airspy/airspy_source_c.cc) did the trick! it works, much better than gqrx at 10MSPS on under powered hardware.
Fantastic.
Aye, I should have some basic gain controls in this week for testing, just working out some other things and then I'll have a test dialog that can adjust whatever gain parameters SoapySDR exposes (assuming the OsmoSDR module supports it).
I'll update this issue when it's ready for testing -- thanks for your help! Ultimately I think we'll want a native standalone SoapyAirSpy to replace the OsmosSDR stuff as there's only a few devices left that we don't already cover with standalone modules and it removes a nice pile of dependencies in most cases.
@antigraviton haven't got the gain support in yet; but I've pushed a pile of optimizations to the soapysdr-support branch -- let me know if that improves performance for you on the AirSpy.
Dear Charles,
I've tried running CubicSDR with the airspy. Initially I get an error (from Soapy), about an unsupported samplerate.
Hardcoding the sample rate in
sdr/SoapySDRThread.cpp
line 177, i.e. replacingsampleRate.load()
with2.5e6
solves the initial startup problems, however it looks like there's something else wrong. Also tried changing the default sample rateDEFAULT_SAMPLE_RATE
to 2500000, with the same result. Difficult to describe aside from 2 weakish signals that don't move when changing frequencies, see below.How can I help?
Kind regards (and many compliments for your work),
Derk