Development branch - Githubissues

Hi @shajen !

First of all - thanks for a fantastic software! Great functionality! With all respect, this is open source and you are doing this in your private/own time. Other things in the world can be more important than maintaining a git repo.

So, a very humble, as humble as this question can be. Are there any plans to continue to improve and evolve this repo?

Best regards, Tubalainen

Thank you for the very kind words!

The project is still in progress. I have a huge update planned over the next few weeks/months, including:

classification of recordings using artificial intelligence (detect noise, speech etc.)
web configuration
using SoapySDR library that support almost all sdr device
recordings grouping
publication of web panel sources
and more

I need time to test it all, which I haven't had much lately, so please be patient.

Hi @shajen please shout if I want some help with testing and eval. :) Hope development is going well.

Hello, the final version is almost ready! The development version is available for test, follow these steps to run:

IMPORTANT

old config is dropped, you have to configure it again via gui, but now it's very easy, check manual
transmissions and spectrograms are transferred but you have to use the same directory for docker compose (due to default docker compose volume name) which was used in previous version (sdr in home directory by default)

stop and remove old version:

cd ~/sdr
docker compose down
cd ..
rm -rf ~/sdr

download and run new version

git clone --branch devel https://github.com/shajen/rtl-sdr-scanner-cpp.git ~/sdr
cd ~/sdr
sed -i 's/latest/devel/' .env
nano .env # customize settings if you want: timezone, admin account and other
docker compose up -d

More info in README on devel branch.

I hope it works! Enjoy it!

new version crashs here:

sdr-sdr-monitor-setup-1 exited with code 0 Error response from daemon: driver failed programming external connectivity on endpoint sdr-sdr-monitor-server-1 (33b5118a36517a3e5aee040cb2dc149ea6e1df26e657737e079fe0ef5c1a3818): Bind for 0.0.0.0:8000 failed: port is already allocated root@openwebrx:/home/mike/sdr#

ps. i send u a smal donation for your work! keep it up please!!

new version crashs here:

sdr-sdr-monitor-setup-1 exited with code 0 Error response from daemon: driver failed programming external connectivity on endpoint sdr-sdr-monitor-server-1 (33b5118a36517a3e5aee040cb2dc149ea6e1df26e657737e079fe0ef5c1a3818): Bind for 0.0.0.0:8000 failed: port is already allocated root@openwebrx:/home/mike/sdr#

ps. i send u a smal donation for your work! keep it up please!!

Please stop your old sdrscanner instance. Some other docker/service is utilizing port 8000 .

@shajen WAAAHOOO!! Thanks a billion!

I am using my attic server for many things, AIS-catcher, dump1090. They are hugging RTL/Airspy devices for each service. Ive got two devices allocated for sdrscanner. One airspy r2 and one rtl-sdr.

How ever - hence the other devices on the machine are used by other services sdrscanner cannot connect to them and utilize them the system exits and no devices are presented to sdrscanner.

sdrscanner-sdr-scanner-1     | [2023-11-01 10:01:31.838612] [info   ] [SoapySDR   ] found 4 devices:
sdrscanner-sdr-scanner-1     | [2023-11-01 10:01:31.838634] [info   ] [SoapySDR   ] #0, driver: airspy, serial: 62cc68ff3584805b
sdrscanner-sdr-scanner-1     | [2023-11-01 10:01:31.848847] [info   ] [SoapySDR   ]  gain: LNA, min: 0 dB, max: 15 dB
sdrscanner-sdr-scanner-1     | [2023-11-01 10:01:31.848871] [info   ] [SoapySDR   ]  gain: MIX, min: 0 dB, max: 15 dB
sdrscanner-sdr-scanner-1     | [2023-11-01 10:01:31.848875] [info   ] [SoapySDR   ]  gain: VGA, min: 0 dB, max: 15 dB
sdrscanner-sdr-scanner-1     | [2023-11-01 10:01:31.848880] [info   ] [SoapySDR   ]  frequency range: 24 MHz - 1800 MHz
sdrscanner-sdr-scanner-1     | [2023-11-01 10:01:31.848888] [info   ] [SoapySDR   ]  sample rates: 10 MHz, 2500 kHz
sdrscanner-sdr-scanner-1     | [2023-11-01 10:01:31.849232] [info   ] [SoapySDR   ] #1, name: Realtek RTL2838UHIDIR unavailable, driver: rtlsdr, serial: ais
sdrscanner-sdr-scanner-1     | [2023-11-01 10:01:32.006904] [info   ] [Mqtt       ] stop thread id: 10
sdrscanner-broker-1          | 1698829292: Client auto-346B48ED-E70A-773F-D8DF-1B016D3894A7 disconnected.
sdrscanner-sdr-scanner-1     | [2023-11-01 10:01:32.007568] [error  ] [main       ] main exception: Unable to open RTL-SDR device
sdrscanner-sdr-scanner-1 exited with code 1

If i stop dump1090 and ais-catcher and free up all connected devices and then start sdrscanner it all works like a charm.

I have also tried to stop dump1090 and ais-catcher, start sdrscanner and remove the devices in the GUI that I am using for dump1090 and ais-catcher. Save the config. But it does not help. The devices are still there (the deletion does not work). And upon a restart of the docker compose the devices are back again.

Can i in config.json specify devices? If so, please help me with syntax. Thanks :)

I have now installed the denvelop version and am thrilled again! You're doing a great job!

I now have a nooelec dongle and an AirSpy Mini connected. But what I noticed is that when I use the AirSpy mini and set the sample rate to 8 MHz, the audio files are much too fast. They sound as if they are being played at 4x speed. The files recordet with the nooelec and 2MHz Sample mode are normal

if i change the samplerate of the airspy mini back to 2 MHz .. the audiofiles are to slow, sounds like 0.25 speed

@tubalainen

I am using my attic server for many things, AIS-catcher, dump1090. They are hugging RTL/Airspy devices for each service. Ive got two devices allocated for sdrscanner. One airspy r2 and one rtl-sdr.

How ever - hence the other devices on the machine are used by other services sdrscanner cannot connect to them and utilize them the system exits and no devices are presented to sdrscanner.

If i stop dump1090 and ais-catcher and free up all connected devices and then start sdrscanner it all works like a charm.

It's a bug. Thank you for investigation and very useful debug info! I just pushed a fix. Please download latest images, run again and check if it work:

docker compose pull 
docker compose up

@ar8001

ps. i send u a smal donation for your work! keep it up please!!

Thank you! I got it.

I now have a nooelec dongle and an AirSpy Mini connected. But what I noticed is that when I use the AirSpy mini and set the sample rate to 8 MHz, the audio files are much too fast. They sound as if they are being played at 4x speed. The files recordet with the nooelec and 2MHz Sample mode are normal

if i change the samplerate of the airspy mini back to 2 MHz .. the audiofiles are to slow, sounds like 0.25 speed

I have no AirSpy Mini - I have only rtl-sdr and HackRf. It is really hard to fix a bug without hardware. Please install SoapySDR (sudo apt-get install soapysdr-tools) on your host machine and send back full output of command (run for each your devices separately) while sdr-scanner is down:

SoapySDRUtil --probe=serial=XXX

where xxx is a serial of device (to find serial run SoapySDRUtil --find).

Hi,

I have an SDRPlay RSP1A and unfortunately can't get it working with the devel docker image. I think it's due to specific drivers / dependencies being required to get it working with SoapySDR.

For example, the drivers located here: https://www.sdrplay.com/downloads/

And the SoapySDR SDRPlay module located here: https://github.com/pothosware/SoapySDRPlay3

I've managed to get the RSP1A working on my machine with other SDR tools (running Debian) using the instructions here: https://groups.io/g/SDRPlayUsers/topic/83829243

But I don't know enough about docker to get your image to install these drivers when running docker compose.

If it helps, you can see how openwebrx handle it here: https://github.com/jketterl/openwebrx/blob/develop/docker/scripts/install-dependencies-sdrplay.sh

Is there any scope to add SDRPlay support to the image, or do you have any thoughts on how to run this outside of docker as I have all the drivers installed and working on the host machine?

Many thanks!

Thanks @shajen the device lock thing works great now! Only adapts and starts the devices that are not used! :)

New bugs/Feature Req´s 1.) Ive got a airspy r2 that is capable of 10MHz bandwidth. All "transmissions" are very distorted and sound very very odd. If I fall back to have 2.4MHz bandwidth it works. I am running the docker on a capable machine with a core i5 7500 processor and 32 gigs of memory. The CPU is idling. I am able to connect to the Airspy r2 via spyserver or soapsdrserver without any issues. So there is not a issue with the USB bus either. 2.) When editing my second device I cannot push "save". When I do so it all hangs. All I did was removing the 70 cm ham band section. Any changes I make here will end up hanging up the system require me to "docker compose restart".

3.) Would it be possible not to start the whole system (including the new AI stuff for SnR etc) before you have set all config? Hence if you make a lot of changes the Signal to noise (for instance) will change. Can be gain, can be freq band and sections etc. 3A.) So, Would it be possible to introduce a "welcome to sdrscanner" wizard and after you have set it all up kick off the auto adjustments and the AI stuff? 3B,) Do the same, relearn SnR etc. when you make changes to your setup (even if it has been running for awhile)?

@JulianDFarmer

I have an SDRPlay RSP1A and unfortunately can't get it working with the devel docker image. I think it's due to specific drivers / dependencies being required to get it working with SoapySDR.

Is there any scope to add SDRPlay support to the image, or do you have any thoughts on how to run this outside of docker as I have all the drivers installed and working on the host machine?

Hi,

I added SDRplay support to docker image in 5432b24.

Save udev rules on your host OS to /etc/udev/rules.d/66-mirics.rules (if don't have yet):

SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="1df7",ATTRS{idProduct}=="2500",MODE:="0666"
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="1df7",ATTRS{idProduct}=="3000",MODE:="0666"
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="1df7",ATTRS{idProduct}=="3010",MODE:="0666"
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="1df7",ATTRS{idProduct}=="3020",MODE:="0666"
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="1df7",ATTRS{idProduct}=="3030",MODE:="0666"

Then reload udev rules:

sudo udevadm control --reload-rules && sudo udevadm trigger

Then run new images and check:

docker compose pull
docker compose up -d

@tubalainen

New bugs/Feature Req´s 1.) Ive got a airspy r2 that is capable of 10MHz bandwidth. All "transmissions" are very distorted and sound very very odd. If I fall back to have 2.4MHz bandwidth it works. I am running the docker on a capable machine with a core i5 7500 processor and 32 gigs of memory. The CPU is idling. I am able to connect to the Airspy r2 via spyserver or soapsdrserver without any issues. So there is not a issue with the USB bus either.

Try to set 10240000 Hz sample rate. It's very important that sample rate should be the power of 2 multiplied by some factor, 10240000 = 2^10 * 10000, so looks ok.

2.) When editing my second device I cannot push "save". When I do so it all hangs. All I did was removing the 70 cm ham band section. Any changes I make here will end up hanging up the system require me to "docker compose restart".

When you click save sdr-scaner module need restart, so you have to wait few seconds before click save again or refresh page. Moreover, you can change the settings of any devices and click save once - all settings will be saved.

3.) Would it be possible not to start the whole system (including the new AI stuff for SnR etc) before you have set all config? Hence if you make a lot of changes the Signal to noise (for instance) will change. Can be gain, can be freq band and sections etc.

Yes, you can do this by start only selected services (but then spectrograms and transmissions are not captured), set config, and run rest services:

docker compose up -d broker sdr-scanner monitor-server
#set config 
docker compose up -d

3A.) So, Would it be possible to introduce a "welcome to sdrscanner" wizard and after you have set it all up kick off the auto adjustments and the AI stuff?

Maybe in the distant future. I have some other features to do.

3B,) Do the same, relearn SnR etc. when you make changes to your setup (even if it has been running for awhile)?

It works as you wrote. If you change the configuration, the scanner learns the SnR again.

Hi,

I added SDRplay support to docker image in 5432b24.

Thanks, that works! I'm coming across an issue, though, where if I have more than one set of frequencies set to scan it does not record anything and resets itself every few minutes.

Let me know if you want me to open this as a separate issue - not sure if you would prefer to keep all the development branch issues separate from the main issues?

Here is an example of the logging output:


sdr-sdr-scanner-1     | [2023-11-05 21:31:05.757485] [info   ] [SoapySDR   ] found 1 devices:
sdr-sdr-scanner-1     | [2023-11-05 21:31:05.757540] [info   ] [SoapySDR   ] #0, driver: sdrplay, serial: 2235023799
sdr-sdr-scanner-1     | [2023-11-05 21:31:05.798098] [info   ] [SoapySDR   ]  gain: IFGR, min: 20 dB, max: 59 dB
sdr-sdr-scanner-1     | [2023-11-05 21:31:05.798133] [info   ] [SoapySDR   ]  gain: RFGR, min: 0 dB, max: 9 dB
sdr-sdr-scanner-1     | [2023-11-05 21:31:05.798147] [info   ] [SoapySDR   ]  frequency range: 0 MHz - 2000 MHz 
sdr-sdr-scanner-1     | [2023-11-05 21:31:05.798169] [info   ] [SoapySDR   ]  sample rates: 62500, 96 kHz, 125 kHz, 192 kHz, 250 kHz, 384 kHz, 500 kHz, 768 kHz, 1 MHz, 2 MHz, 2048 kHz, 3 MHz, 4 MHz, 5 MHz, 6 MHz, 7 MHz, 8 MHz, 9 MHz, 10 MHz
sdr-sdr-scanner-1     | [2023-11-05 21:31:06.934939] [info   ] [RingBuffer ] init, buffer size: 41943040
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.064016] [info   ] [SoapySDR   ] open device: 2235023799
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.064211] [info   ] [SoapySDR   ] set offset: 0, device: 2235023799
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.064230] [info   ] [SoapySDR   ] set gain IFGR: 40, device: 2235023799
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.064237] [info   ] [SoapySDR   ] set gain RFGR: 2, device: 2235023799
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.064273] [info   ] [spectrogram] init
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.064353] [info   ] [spectrogram] init
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.064458] [info   ] [spectrogram] init
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.064524] [info   ] [SamplesWrk ] start thread id: 62
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.064575] [info   ] [spectrogram] init
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.064676] [info   ] [SamplesWrk ] start thread id: 63
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.064828] [info   ] [SamplesWrk ] start thread id: 64
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.065120] [info   ] [Scanner    ] original frequency ranges: 2
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.065145] [info   ] [Scanner    ] frequency range start: 130.000 kHz, stop: 135.000 kHz, sample rate: 005.120 kHz, fft: 0
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.065153] [info   ] [Scanner    ] frequency range start: 155.500 kHz, stop: 157.500 kHz, sample rate: 002.048 kHz, fft: 0
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.065155] [info   ] [SamplesWrk ] start thread id: 65
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.065160] [info   ] [Scanner    ] splitted frequency ranges: 2
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.065201] [info   ] [Scanner    ] frequency range, start: 130.000 kHz, stop: 135.000 kHz, fft: 4096
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.065208] [info   ] [Scanner    ] frequency range, start: 155.500 kHz, stop: 157.500 kHz, fft: 2048
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.065349] [info   ] [Scanner    ] start thread id: 66
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.412950] [info   ] [fft        ] init size: 4096
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.413203] [info   ] [fft        ] init size: 4096
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.413207] [info   ] [fft        ] init size: 4096
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.413462] [info   ] [fft        ] init size: 4096
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.414586] [warning] [NoiseLrn   ] signals and noise do not match
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.414635] [info   ] [NoiseLrn   ] initialize, start: 130.000 kHz, stop: 135.000 kHz
sdr-sdr-scanner-1     | [2023-11-05 21:31:07.415260] [info   ] [SignalMediator] aggregation time: 1000 ms
sdr-sdr-scanner-1     | [2023-11-05 21:31:09.145637] [info   ] [fft        ] init size: 2048
sdr-sdr-scanner-1     | [2023-11-05 21:31:09.145656] [info   ] [fft        ] init size: 2048
sdr-sdr-scanner-1     | [2023-11-05 21:31:09.146171] [info   ] [fft        ] init size: 2048
sdr-sdr-scanner-1     | [2023-11-05 21:31:09.146218] [info   ] [fft        ] init size: 2048
sdr-sdr-scanner-1     | [2023-11-05 21:31:09.146631] [warning] [NoiseLrn   ] signals and noise do not match
sdr-sdr-scanner-1     | [2023-11-05 21:31:09.146643] [info   ] [NoiseLrn   ] initialize, start: 155.500 kHz, stop: 157.500 kHz
sdr-sdr-scanner-1     | [2023-11-05 21:31:09.146928] [info   ] [SignalMediator] aggregation time: 1000 ms
sdr-sdr-scanner-1     | [2023-11-05 21:33:44.444820] [info   ] [SdrDevice  ] average samples time: 1575.54 ms
sdr-sdr-scanner-1     | [2023-11-05 21:33:44.445114] [info   ] [Scanner    ] average samples time: 1573.80 ms
sdr-sdr-scanner-1     | [2023-11-05 21:36:22.872358] [info   ] [SdrDevice  ] average samples time: 1584.28 ms
sdr-sdr-scanner-1     | [2023-11-05 21:36:22.872649] [info   ] [Scanner    ] average samples time: 1584.27 ms
sdr-sdr-scanner-1     | [2023-11-05 21:39:01.450428] [info   ] [SdrDevice  ] average samples time: 1585.78 ms
sdr-sdr-scanner-1     | [2023-11-05 21:39:01.450725] [info   ] [Scanner    ] average samples time: 1585.78 ms
sdr-sdr-scanner-1     | [2023-11-05 21:41:40.108054] [info   ] [SdrDevice  ] average samples time: 1586.58 ms
sdr-sdr-scanner-1     | [2023-11-05 21:41:40.108750] [info   ] [Scanner    ] average samples time: 1586.58 ms
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.612302] [error  ] [SoapySDR   ] can not activate stream device: 2235023799
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.612489] [error  ] [Scanner    ] exception: can not activate stream device: 2235023799
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.612519] [info   ] [Scanner    ] stop thread id: 66
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.641214] [error  ] [main       ] some device stop working
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.642727] [info   ] [SamplesWrk ] stop thread id: 62
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.642943] [info   ] [spectrogram] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.642963] [info   ] [fft        ] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.642979] [info   ] [fft        ] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.643027] [info   ] [SamplesWrk ] stop thread id: 63
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.643214] [info   ] [spectrogram] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.643277] [info   ] [fft        ] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.643326] [info   ] [fft        ] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.643435] [info   ] [SamplesWrk ] stop thread id: 64
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.643707] [info   ] [spectrogram] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.643723] [info   ] [fft        ] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.643735] [info   ] [fft        ] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.643850] [info   ] [SamplesWrk ] stop thread id: 65
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.644304] [info   ] [spectrogram] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.644391] [info   ] [fft        ] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:42:41.644446] [info   ] [fft        ] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:42:42.234001] [info   ] [Mqtt       ] stop thread id: 12
sdr-broker-1          | 1699220562: Client auto-905BFB22-2575-B4B1-755D-BCEE58625A08 disconnected.
sdr-sdr-scanner-1 exited with code 0
sdr-broker-1          | 1699220563: New connection from 172.20.0.4:59052 on port 1883.
sdr-broker-1          | 1699220563: New client connected from 172.20.0.4:59052 as auto-6261C31B-5097-C4EE-0B1A-7A967FD3F9F0 (p2, c1, k60, u'user').
sdr-sdr-scanner-1     | [2023-11-05 21:42:43.221516] [info   ] [Mqtt       ] connected
sdr-sdr-scanner-1     | [2023-11-05 21:42:43.333357] [info   ] [SoapySDR   ] found 1 devices:
sdr-sdr-scanner-1     | [2023-11-05 21:42:43.333410] [info   ] [SoapySDR   ] #0, driver: sdrplay, serial: 2235023799
sdr-sdr-scanner-1     | [2023-11-05 21:42:43.375500] [info   ] [SoapySDR   ]  gain: IFGR, min: 20 dB, max: 59 dB
sdr-sdr-scanner-1     | [2023-11-05 21:42:43.375539] [info   ] [SoapySDR   ]  gain: RFGR, min: 0 dB, max: 9 dB
sdr-sdr-scanner-1     | [2023-11-05 21:42:43.375554] [info   ] [SoapySDR   ]  frequency range: 0 MHz - 2000 MHz 
sdr-sdr-scanner-1     | [2023-11-05 21:42:43.375577] [info   ] [SoapySDR   ]  sample rates: 62500, 96 kHz, 125 kHz, 192 kHz, 250 kHz, 384 kHz, 500 kHz, 768 kHz, 1 MHz, 2 MHz, 2048 kHz, 3 MHz, 4 MHz, 5 MHz, 6 MHz, 7 MHz, 8 MHz, 9 MHz, 10 MHz
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.510212] [info   ] [RingBuffer ] init, buffer size: 41943040
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.643110] [info   ] [SoapySDR   ] open device: 2235023799
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.643320] [info   ] [SoapySDR   ] set offset: 0, device: 2235023799
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.643345] [info   ] [SoapySDR   ] set gain IFGR: 40, device: 2235023799
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.643355] [info   ] [SoapySDR   ] set gain RFGR: 2, device: 2235023799
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.643400] [info   ] [spectrogram] init
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.643496] [info   ] [spectrogram] init
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.643619] [info   ] [spectrogram] init
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.643744] [info   ] [SamplesWrk ] start thread id: 62
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.643841] [info   ] [SamplesWrk ] start thread id: 64
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.643801] [info   ] [SamplesWrk ] start thread id: 63
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.643762] [info   ] [spectrogram] init
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.644632] [info   ] [Scanner    ] original frequency ranges: 2
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.644665] [info   ] [Scanner    ] frequency range start: 130.000 kHz, stop: 135.000 kHz, sample rate: 005.120 kHz, fft: 0
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.644677] [info   ] [Scanner    ] frequency range start: 155.500 kHz, stop: 157.500 kHz, sample rate: 002.048 kHz, fft: 0
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.644686] [info   ] [Scanner    ] splitted frequency ranges: 2
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.644691] [info   ] [SamplesWrk ] start thread id: 65
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.644697] [info   ] [Scanner    ] frequency range, start: 130.000 kHz, stop: 135.000 kHz, fft: 4096
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.644764] [info   ] [Scanner    ] frequency range, start: 155.500 kHz, stop: 157.500 kHz, fft: 2048
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.644938] [info   ] [Scanner    ] start thread id: 66
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.991666] [info   ] [fft        ] init size: 4096
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.991754] [info   ] [fft        ] init size: 4096
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.991697] [info   ] [fft        ] init size: 4096
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.991928] [info   ] [fft        ] init size: 4096
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.993260] [warning] [NoiseLrn   ] signals and noise do not match
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.993308] [info   ] [NoiseLrn   ] initialize, start: 130.000 kHz, stop: 135.000 kHz
sdr-sdr-scanner-1     | [2023-11-05 21:42:44.993956] [info   ] [SignalMediator] aggregation time: 1000 ms
sdr-sdr-scanner-1     | [2023-11-05 21:42:46.747679] [info   ] [fft        ] init size: 2048
sdr-sdr-scanner-1     | [2023-11-05 21:42:46.747683] [info   ] [fft        ] init size: 2048
sdr-sdr-scanner-1     | [2023-11-05 21:42:46.747747] [info   ] [fft        ] init size: 2048
sdr-sdr-scanner-1     | [2023-11-05 21:42:46.747771] [info   ] [fft        ] init size: 2048
sdr-sdr-scanner-1     | [2023-11-05 21:42:46.749465] [warning] [NoiseLrn   ] signals and noise do not match
sdr-sdr-scanner-1     | [2023-11-05 21:42:46.749503] [info   ] [NoiseLrn   ] initialize, start: 155.500 kHz, stop: 157.500 kHz
sdr-sdr-scanner-1     | [2023-11-05 21:42:46.750251] [info   ] [SignalMediator] aggregation time: 1000 ms
sdr-sdr-scanner-1     | [2023-11-05 21:45:21.604243] [info   ] [SdrDevice  ] average samples time: 1571.39 ms
sdr-sdr-scanner-1     | [2023-11-05 21:45:21.605071] [info   ] [Scanner    ] average samples time: 1569.61 ms
sdr-sdr-scanner-1     | [2023-11-05 21:47:59.500164] [info   ] [SdrDevice  ] average samples time: 1578.96 ms
sdr-sdr-scanner-1     | [2023-11-05 21:47:59.500630] [info   ] [Scanner    ] average samples time: 1578.95 ms
sdr-sdr-scanner-1     | [2023-11-05 21:50:37.805447] [info   ] [SdrDevice  ] average samples time: 1583.05 ms
sdr-sdr-scanner-1     | [2023-11-05 21:50:37.806306] [info   ] [Scanner    ] average samples time: 1583.06 ms
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.807214] [error  ] [SoapySDR   ] can not activate stream device: 2235023799
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.807380] [error  ] [Scanner    ] exception: can not activate stream device: 2235023799
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.807409] [info   ] [Scanner    ] stop thread id: 66
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.850859] [error  ] [main       ] some device stop working
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.851845] [info   ] [SamplesWrk ] stop thread id: 62
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.852002] [info   ] [spectrogram] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.852040] [info   ] [fft        ] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.852056] [info   ] [fft        ] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.852114] [info   ] [SamplesWrk ] stop thread id: 63
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.852467] [info   ] [spectrogram] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.852492] [info   ] [fft        ] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.852506] [info   ] [fft        ] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.852568] [info   ] [SamplesWrk ] stop thread id: 64
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.852740] [info   ] [spectrogram] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.852754] [info   ] [fft        ] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.852765] [info   ] [fft        ] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.852826] [info   ] [SamplesWrk ] stop thread id: 65
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.853320] [info   ] [spectrogram] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.853346] [info   ] [fft        ] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:50:40.853360] [info   ] [fft        ] deinit
sdr-sdr-scanner-1     | [2023-11-05 21:50:41.406927] [info   ] [Mqtt       ] stop thread id: 12
sdr-broker-1          | 1699221041: Client auto-6261C31B-5097-C4EE-0B1A-7A967FD3F9F0 disconnected.
sdr-sdr-scanner-1 exited with code 0```

@shajen : if you need access to a remote system with AirSpy Mini .... let me know, and i will send you more donations from time to time to support you and this project

@JulianDFarmer

Hi, I added SDRplay support to docker image in 5432b24.

Thanks, that works! I'm coming across an issue, though, where if I have more than one set of frequencies set to scan it does not record anything and resets itself every few minutes.

Let me know if you want me to open this as a separate issue - not sure if you would prefer to keep all the development branch issues separate from the main issues?

This is problem with SoapySdr. I'm working on it. Please create new issue.

@ar8001

@shajen : if you need access to a remote system with AirSpy Mini .... let me know, and i will send you more donations from time to time to support you and this project

Please follow this instruction and send logs.

Great work on this @shajen & team...

Looks awesome so far and seems to work...

Keep up the good work and look forward to the official release.

shajen / rtl-sdr-scanner-cpp

Development branch #76