shajen / rtl-sdr-scanner-cpp Goto Github PK

Hi, sript always runs without problem, spectograms are saved, everything runs as it should until a new record is loaded.
then the whole program stops working completely. I'm attaching the output from the terminal.

sdr-sdr-monitor-reader-1 | [2023-01-03 19:14:59.529][mqtt_reader ][Spectrogram ][INFO ] save finish
sdr-sdr-monitor-reader-1 | [2023-01-03 19:14:59.851][mqtt_reader ][Spectrogram ][INFO ] rtlsdr_00000001 save, 2023-01-03 19:14:49.699 - 2023-01-03 19:14:58.130, 448000000 - 450000000
sdr-sdr-monitor-reader-1 | [2023-01-03 19:14:59.855][mqtt_reader ][Spectrogram ][INFO ] new data shape: (6, 8001), size: 48.0 kB
sdr-sdr-monitor-reader-1 | [2023-01-03 19:14:59.869][mqtt_reader ][Spectrogram ][INFO ] save finish
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:08.360][mqtt_reader ][Spectrogram ][INFO ] rtlsdr_00000001 save, 2023-01-03 19:14:58.302 - 2023-01-03 19:15:06.641, 171000000 - 173000000
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:08.365][mqtt_reader ][Spectrogram ][INFO ] new data shape: (6, 8001), size: 48.0 kB
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:08.378][mqtt_reader ][Spectrogram ][INFO ] save finish
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:08.521][mqtt_reader ][Spectrogram ][INFO ] rtlsdr_00000001 save, 2023-01-03 19:14:58.472 - 2023-01-03 19:15:06.820, 442000000 - 444000000
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:08.526][mqtt_reader ][Spectrogram ][INFO ] new data shape: (6, 8001), size: 48.0 kB
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:08.537][mqtt_reader ][Spectrogram ][INFO ] save finish
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:08.855][mqtt_reader ][Spectrogram ][INFO ] rtlsdr_00000001 save, 2023-01-03 19:14:58.816 - 2023-01-03 19:15:07.168, 446000000 - 448000000
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:08.860][mqtt_reader ][Spectrogram ][INFO ] new data shape: (6, 8001), size: 48.0 kB
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:08.873][mqtt_reader ][Spectrogram ][INFO ] save finish
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:09.520][mqtt_reader ][Spectrogram ][INFO ] rtlsdr_00000001 save, 2023-01-03 19:14:59.506 - 2023-01-03 19:15:07.851, 444000000 - 446000000
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:09.525][mqtt_reader ][Spectrogram ][INFO ] new data shape: (6, 8001), size: 48.0 kB
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:09.535][mqtt_reader ][Spectrogram ][INFO ] save finish
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:09.853][mqtt_reader ][Spectrogram ][INFO ] rtlsdr_00000001 save, 2023-01-03 19:14:59.846 - 2023-01-03 19:15:08.190, 448000000 - 450000000
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:09.858][mqtt_reader ][Spectrogram ][INFO ] new data shape: (6, 8001), size: 48.0 kB
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:09.880][mqtt_reader ][Spectrogram ][INFO ] save finish
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:18.470][mqtt_reader ][Spectrogram ][INFO ] rtlsdr_00000001 save, 2023-01-03 19:15:08.355 - 2023-01-03 19:15:16.783, 171000000 - 173000000
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:18.475][mqtt_reader ][Spectrogram ][INFO ] new data shape: (6, 8001), size: 48.0 kB
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:18.489][mqtt_reader ][Spectrogram ][INFO ] save finish
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:18.635][mqtt_reader ][Spectrogram ][INFO ] rtlsdr_00000001 save, 2023-01-03 19:15:08.516 - 2023-01-03 19:15:16.950, 442000000 - 444000000
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:18.639][mqtt_reader ][Spectrogram ][INFO ] new data shape: (6, 8001), size: 48.0 kB
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:18.651][mqtt_reader ][Spectrogram ][INFO ] save finish
sdr-sdr-scanner-1 | [2023-01-03 19:15:18.802] [auto_sdr] [info] [RtlSdr] start stream
sdr-sdr-scanner-1 | Allocating 15 zero-copy buffers
sdr-sdr-scanner-1 | [2023-01-03 19:15:18.872] [auto_sdr] [info] [Recorder] create worker frequency: 444.000 kHz, total workers: 1, queue size: 0
sdr-sdr-scanner-1 | [2023-01-03 19:15:18.872] [auto_sdr] [info] [RecorderWrk] start thread id: 24, frequency: 444.000 kHz
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:18.874][mqtt_reader ][Spectrogram ][INFO ] rtlsdr_00000001 save, 2023-01-03 19:15:08.851 - 2023-01-03 19:15:17.290, 446000000 - 448000000
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:18.879][mqtt_reader ][Spectrogram ][INFO ] new data shape: (6, 8001), size: 48.0 kB
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:18.940][mqtt_reader ][Spectrogram ][INFO ] save finish
sdr-sdr-scanner-1 | [2023-01-03 19:15:18.956] [auto_sdr] [info] [DataCtrl] start transmission frequency: 444.000 kHz
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:19.577][mqtt_reader ][Spectrogram ][INFO ] rtlsdr_00000001 save, 2023-01-03 19:15:09.515 - 2023-01-03 19:15:19.253, 444000000 - 446000000
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:19.582][mqtt_reader ][Spectrogram ][INFO ] new data shape: (7, 8001), size: 56.0 kB
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:19.594][mqtt_reader ][Spectrogram ][INFO ] save finish
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:19.898][mqtt_reader ][Spectrogram ][INFO ] rtlsdr_00000001 save, 2023-01-03 19:15:09.849 - 2023-01-03 19:15:16.620, 448000000 - 450000000
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:19.902][mqtt_reader ][Spectrogram ][INFO ] new data shape: (5, 8001), size: 40.0 kB
sdr-sdr-monitor-reader-1 | [2023-01-03 19:15:19.916][mqtt_reader ][Spectrogram ][INFO ] save finish
sdr-sdr-scanner-1 | [2023-01-03 19:15:20.663] [auto_sdr] [info] [TornDtr] report transmission frequency: 444.000 kHz, duration: 1.35 seconds
sdr-sdr-scanner-1 | [2023-01-03 19:15:20.664] [auto_sdr] [info] [DataCtrl] finish transmission frequency: 444.000 kHz, duration: 1.28 seconds, reach minimum: false
sdr-sdr-scanner-1 | [2023-01-03 19:15:20.664] [auto_sdr] [info] [RecorderWrk] stop thread id: 24, frequency: 444.000 kHz, queue size: 0
sdr-sdr-scanner-1 | [2023-01-03 19:15:20.664] [auto_sdr] [info] [Recorder] erase worker frequency: 444.000 kHz, total workers: 0, queue size: 0
sdr-sdr-scanner-1 | [2023-01-03 19:15:20.725] [auto_sdr] [info] [RtlSdr] cancel stream
sdr-sdr-scanner-1 | [2023-01-03 19:15:20.764] [auto_sdr] [info] [RtlSdr] stop stream
sdr-sdr-scanner-1 | [2023-01-03 19:15:21.023] [auto_sdr] [error] [Scanner] exception: read samples error
sdr-sdr-scanner-1 | [2023-01-03 19:15:21.023] [auto_sdr] [info] [Scanner] stop thread id: 23
sdr-sdr-scanner-1 | [2023-01-03 19:15:21.026] [auto_sdr] [info] [Recorder] stop thread id: 22
sdr-sdr-scanner-1 | [2023-01-03 19:15:21.026] [auto_sdr] [info] [SamplesWrk] stop thread id: 18
sdr-sdr-scanner-1 | [2023-01-03 19:15:21.027] [auto_sdr] [info] [spectrum] deinit
sdr-sdr-scanner-1 | [2023-01-03 19:15:21.027] [auto_sdr] [info] [SamplesWrk] stop thread id: 19
sdr-sdr-scanner-1 | [2023-01-03 19:15:21.027] [auto_sdr] [info] [spectrum] deinit
sdr-sdr-scanner-1 | [2023-01-03 19:15:21.027] [auto_sdr] [info] [SamplesWrk] stop thread id: 20
sdr-sdr-scanner-1 | [2023-01-03 19:15:21.027] [auto_sdr] [info] [spectrum] deinit
sdr-sdr-scanner-1 | [2023-01-03 19:15:21.027] [auto_sdr] [info] [SamplesWrk] stop thread id: 21
sdr-sdr-scanner-1 | [2023-01-03 19:15:21.028] [auto_sdr] [info] [spectrum] deinit
sdr-sdr-scanner-1 | [2023-01-03 19:15:21.045] [auto_sdr] [info] [RtlSdr] close device, index: 0, name: Generic RTL2832U OEM, serial: 00000001
sdr-sdr-scanner-1 | [2023-01-03 19:15:21.129] [auto_sdr] [info] [Mqtt] stop thread id: 9
sdr-sdr-broker-1 | 1672769721: Client auto-98DF898A-08B3-4177-82ED-39B93D466E9C disconnected.
sdr-sdr-scanner-1 | [2023-01-03 19:15:21.131] [auto_sdr] [info] [main] stop app auto_sdr
sdr-sdr-scanner-1 | [2023-01-03 19:15:21.131] [auto_sdr] [info] [main] stop thread id: 8
sdr-sdr-scanner-1 exited with code 0

And this is my config.json
{
"scanner_frequencies_ranges": [
{
"device_serial": "auto",
"ranges": [
{
"start": 171000000,
"stop": 173000000,
"step": 250,
"sample_rate": 2048000
},
{
"start": 442000000,
"stop": 444000000,
"step": 250,
"sample_rate": 2048000
},
{
"start": 444000000,
"stop": 446000000,
"step": 250,
"sample_rate": 2048000
},
{
"start": 446000000,
"stop": 448000000,
"step": 250,
"sample_rate": 2048000
},
{
"start": 448000000,
"stop": 450000000,
"step": 250,
"sample_rate": 2048000
}
]
}
],
"devices": {
"rtl_sdr": {
"ppm_error": 40,
"tuner_gain": 25.0,
"offset": 0
},
"hack_rf": {
"lna_gain": 0,
"vga_gain": 0,
"offset": 0
}
},
"recording": {
"max_noise_time_ms": 500,
"min_time_ms": 2000,
"min_sample_rate": 16000
},
"detection": {
"frequency_grouping_size": 10000,
"frequency_range_scanning_time_ms": 64,
"noise_learning_time_seconds": 30,
"noise_detection_margin": 10,
"torn_transmission_learning_time_seconds": 60
},
"output": {
"logs": "sdr/logs",
"file_log_level": "info",
"console_log_level": "info"
},
"cores": 4,
"memory_limit_mb": 0,
"mqtt": {
"hostname": "sdr-broker",
"port": 1883,
"username": "admin",
"password": "password"
}
}

thank you very much

Would it be possible to have a single docker container? I really don’t like having so many different containers. I want to run it on unraid which isn’t possible currently

Hi
Are you allow to edit the web interface? And how can I do it? I haven't found it's source code

I keep getting the following error starting the docker compose file:

sdr-sdr-monitor-setup-1 | Operations to perform:
sdr-sdr-monitor-setup-1 | Apply all migrations: admin, auth, contenttypes, graphs, logs, sdr, sessions
sdr-sdr-monitor-setup-1 | Running migrations:
sdr-sdr-monitor-setup-1 | No migrations to apply.
sdr-sdr-monitor-setup-1 | CommandError: Error: That username is already taken.
sdr-sdr-monitor-setup-1 exited with code 0

Running the stock compose file, only change is the port that is changed from 8000 to 10123 to not interfere with my home-assistant and portainer running on the same host.

All other parts start fine.

First of all, great product I was playing with it since yesterday and I love it. But I was wondering if it was possible to use SoapySDR as the backend thus enabling pretty much every SDR device to work. I stumbled across another issue/feature request that asked for RSP support. I'm aware that integrating every single piece of hardware is just not viable for a small personal project. I'm not fully aware of how the project is structured and if it's even possible to implement it but I would guess it would be a game changer.

Hey,

for me the waterfall html page thing does not work. It is just a blank white page, if i inspect the element i can see that it loaded the correct html file.

I installed apache2 and configured it that the www directory is "/home/pi/rtl-sdr-scanner-cpp/waterfall live/"

If i go to my raspberry ip with port 9999 it says: "The WebSocket handshake Connection field is missing the upgrade token"

So the "WebSocket connection to 'ws://localhost:9999/' failed:"

I am having some sort of problem, either configuration or code, that causes sdr-scanner to crash after a while. Spectrum is graphed (although it looks... strange) but no transmissions have been received. I suspect, but have not yet verified, that receiving a transmission causes sdr-scanner to crash.

I'm using a HackRF with the latest firmware:

hackrf_info version: 2022.09.1
libhackrf version: 2022.09.1 (0.7)
Found HackRF
Index: 0
Serial number: 0000000000000000a06063c82876671b
Board ID Number: 2 (HackRF One)
Firmware Version: 2023.01.1 (API:1.07)
Part ID Number: 0xa000cb3c 0x00704358
Hardware Revision: older than r6
Hardware supported by installed firmware:
    HackRF One

Config:

{
  "scanner_frequencies_ranges": [
    {
      "device_serial": "auto",
      "ranges": [
        {
          "start": 144000000,
          "stop": 146000000,
          "sample_rate": 2048000
        },
        {
          "start": 128000000,
          "stop": 130000000,
          "sample_rate": 2048000
        }
      ]
    }
  ],
  "ignored_frequencies": [],
  "devices": {
    "rtl_sdr": {
      "ppm_error": 0,
      "tuner_gain": 0.0,
      "offset": 0
    },
    "hack_rf": {
      "lna_gain": 16,
      "vga_gain": 42,
      "offset": 0
    }
  },
  "recording": {
    "max_noise_time_ms": 500,
    "min_time_ms": 2000,
    "min_sample_rate": 16000
  },
  "detection": {
    "frequency_grouping_size": 10000,
    "frequency_range_scanning_time_ms": 64,
    "noise_learning_time_seconds": 30,
    "noise_detection_margin": 10,
    "torn_transmission_learning_time_seconds": 60
  },
  "output": {
    "logs": "sdr/logs",
    "file_log_level": "info",
    "console_log_level": "info"
  },
  "cores": 4,
  "memory_limit_mb": 0,
  "mqtt": {
    "hostname": "sdr-broker",
    "port": 1883,
    "username": "admin",
    "password": "password"
  }
}

Logs

sdr-scanner_1         | [2023-02-18 15:29:14.465032] [info   ] [HackRf     ] start stream, samples: 262144
sdr-scanner_1         | [2023-02-18 15:29:14.547823] [info   ] [HackRf     ] stop stream
sdr-scanner_1         | [2023-02-18 15:29:14.560697] [info   ] [HackRf     ] start stream, samples: 262144
sdr-monitor-reader_1  | [2023-02-18 15:29:14.595][mqtt_reader    ][Spectrogram  ][INFO   ] save, hackrf_a06063c82876671b, 2023-02-18 15:29:14.559, 144000000 - 146000000, 2.0 kB, -72.59 dBfs
sdr-scanner_1         | [2023-02-18 15:29:14.644670] [info   ] [HackRf     ] stop stream
sdr-scanner_1         | [2023-02-18 15:29:14.662337] [info   ] [HackRf     ] start stream, samples: 262144
sdr-scanner_1         | [2023-02-18 15:29:14.663258] [error  ] [Scanner    ] exception: can not start stream
sdr-scanner_1         | [2023-02-18 15:29:14.663370] [info   ] [Scanner    ] stop thread id: 18
sdr-scanner_1         | [2023-02-18 15:29:14.672394] [info   ] [SamplesWrk ] stop thread id: 14
sdr-scanner_1         | [2023-02-18 15:29:14.672656] [info   ] [spectrogram] deinit
sdr-scanner_1         | [2023-02-18 15:29:14.672748] [info   ] [fft        ] deinit
sdr-scanner_1         | [2023-02-18 15:29:14.672834] [info   ] [SamplesWrk ] stop thread id: 15
sdr-scanner_1         | [2023-02-18 15:29:14.672944] [info   ] [spectrogram] deinit
sdr-scanner_1         | [2023-02-18 15:29:14.673026] [info   ] [fft        ] deinit
sdr-scanner_1         | [2023-02-18 15:29:14.673115] [info   ] [SamplesWrk ] stop thread id: 16
sdr-scanner_1         | [2023-02-18 15:29:14.673238] [info   ] [spectrogram] deinit
sdr-scanner_1         | [2023-02-18 15:29:14.673323] [info   ] [fft        ] deinit
sdr-scanner_1         | [2023-02-18 15:29:14.673415] [info   ] [SamplesWrk ] stop thread id: 17
sdr-scanner_1         | [2023-02-18 15:29:14.673717] [info   ] [spectrogram] deinit
sdr-scanner_1         | [2023-02-18 15:29:14.673839] [info   ] [fft        ] deinit
sdr-scanner_1         | [2023-02-18 15:29:14.674132] [info   ] [HackRf     ] close device, serial: a06063c82876671b
sdr-scanner_1         | [2023-02-18 15:29:15.188436] [info   ] [HackRf     ] exit
sdr-scanner_1         | [2023-02-18 15:29:15.294856] [info   ] [Mqtt       ] stop thread id: 10
sdr-scanner_1         | [2023-02-18 15:29:15.295698] [info   ] [main       ] stop app auto_sdr
sdr-scanner_1         | [2023-02-18 15:29:15.295766] [info   ] [main       ] stop thread id: 7
sdr-broker_1          | 1676755755: Client auto-3C730CAA-260C-3D3C-8FA6-F78C0B869E55 disconnected.
sdr-scanner_sdr-scanner_1 exited with code 0

debug log

sdr-scanner_1         | [2023-02-18 15:44:16.508177] [trace  ] [HackRf     ] read samples: 262144
sdr-scanner_1         | [2023-02-18 15:44:16.508825] [trace  ] [HackRf     ] read samples: completed
sdr-scanner_1         | [2023-02-18 15:44:16.509013] [info   ] [HackRf     ] stop stream
sdr-scanner_1         | [2023-02-18 15:44:16.519931] [trace  ] [SamplesProc] start processing
sdr-scanner_1         | [2023-02-18 15:44:16.519957] [trace  ] [SamplesProc] start waiting
sdr-scanner_1         | [2023-02-18 15:44:16.519998] [trace  ] [SamplesWrk ] thread id: 14, start processing
sdr-scanner_1         | [2023-02-18 15:44:16.520075] [trace  ] [SamplesWrk ] thread id: 14, uint8 to complex finished
sdr-scanner_1         | [2023-02-18 15:44:16.520625] [trace  ] [SamplesWrk ] thread id: 17, start processing
sdr-scanner_1         | [2023-02-18 15:44:16.520688] [trace  ] [SamplesWrk ] thread id: 17, uint8 to complex finished
sdr-scanner_1         | [2023-02-18 15:44:16.520810] [trace  ] [SamplesProc] thread id: 17, psd finished
sdr-scanner_1         | [2023-02-18 15:44:16.520817] [trace  ] [SamplesWrk ] thread id: 17, finish processing
sdr-scanner_1         | [2023-02-18 15:44:16.520828] [trace  ] [SamplesWrk ] thread id: 15, start processing
sdr-scanner_1         | [2023-02-18 15:44:16.520883] [trace  ] [SamplesWrk ] thread id: 15, uint8 to complex finished
sdr-scanner_1         | [2023-02-18 15:44:16.521000] [trace  ] [SamplesProc] thread id: 15, psd finished
sdr-scanner_1         | [2023-02-18 15:44:16.521009] [trace  ] [SamplesWrk ] thread id: 15, finish processing
sdr-scanner_1         | [2023-02-18 15:44:16.521071] [trace  ] [SamplesProc] thread id: 14, psd finished
sdr-scanner_1         | [2023-02-18 15:44:16.521076] [trace  ] [SamplesWrk ] thread id: 14, finish processing
sdr-scanner_1         | [2023-02-18 15:44:16.520004] [trace  ] [SamplesWrk ] thread id: 16, start processing
sdr-scanner_1         | [2023-02-18 15:44:16.521137] [trace  ] [SamplesWrk ] thread id: 16, uint8 to complex finished
sdr-scanner_1         | [2023-02-18 15:44:16.521253] [trace  ] [SamplesProc] thread id: 16, psd finished
sdr-scanner_1         | [2023-02-18 15:44:16.521258] [trace  ] [SamplesWrk ] thread id: 16, finish processing
sdr-scanner_1         | [2023-02-18 15:44:16.521266] [trace  ] [SamplesProc] finish waiting
sdr-scanner_1         | [2023-02-18 15:44:16.521292] [trace  ] [SamplesProc] finish processing
sdr-scanner_1         | [2023-02-18 15:44:16.521394] [trace  ] [Recorder   ] active transmissions finished, count: 0
sdr-scanner_1         | [2023-02-18 15:44:16.521414] [debug  ] [HackRf     ] set center frequency: 129.000 kHz
sdr-scanner_1         | [2023-02-18 15:44:16.522432] [info   ] [HackRf     ] start stream, samples: 262144
sdr-scanner_1         | [2023-02-18 15:44:16.522854] [error  ] [Scanner    ] exception: can not start stream
sdr-scanner_1         | [2023-02-18 15:44:16.522872] [info   ] [Scanner    ] stop thread id: 18
sdr-scanner_1         | [2023-02-18 15:44:16.526843] [info   ] [SamplesWrk ] stop thread id: 14
sdr-scanner_1         | [2023-02-18 15:44:16.527261] [info   ] [spectrogram] deinit
sdr-scanner_1         | [2023-02-18 15:44:16.527275] [info   ] [fft        ] deinit
sdr-scanner_1         | [2023-02-18 15:44:16.527458] [info   ] [SamplesWrk ] stop thread id: 15
sdr-scanner_1         | [2023-02-18 15:44:16.527582] [info   ] [spectrogram] deinit
sdr-scanner_1         | [2023-02-18 15:44:16.527589] [info   ] [fft        ] deinit
sdr-scanner_1         | [2023-02-18 15:44:16.527607] [info   ] [SamplesWrk ] stop thread id: 16
sdr-scanner_1         | [2023-02-18 15:44:16.527639] [info   ] [spectrogram] deinit
sdr-scanner_1         | [2023-02-18 15:44:16.527645] [info   ] [fft        ] deinit
sdr-scanner_1         | [2023-02-18 15:44:16.527662] [info   ] [SamplesWrk ] stop thread id: 17
sdr-scanner_1         | [2023-02-18 15:44:16.527732] [info   ] [spectrogram] deinit
sdr-scanner_1         | [2023-02-18 15:44:16.527736] [info   ] [fft        ] deinit
sdr-scanner_1         | [2023-02-18 15:44:16.527936] [info   ] [HackRf     ] close device, serial: a06063c82876671b
sdr-scanner_1         | [2023-02-18 15:44:17.039991] [info   ] [HackRf     ] exit
sdr-scanner_1         | [2023-02-18 15:44:17.077344] [info   ] [Mqtt       ] stop thread id: 10
sdr-broker_1          | 1676756657: Client auto-37ED2681-84EF-0B65-C1F8-741BF2230DE4 disconnected.
sdr-scanner_1         | [2023-02-18 15:44:17.077625] [info   ] [main       ] stop app auto_sdr
sdr-scanner_1         | [2023-02-18 15:44:17.077641] [info   ] [main       ] stop thread id: 7

Hi Shajen,

Lots of broken recording/lost recording.., take away charm of listening ham radio. I am a Ham radio operator where I am listening more of Net meeting on vhf/uhf.

The overall PROBLEM for ham radio operator is, we are missing some live Net meetings due to some other commitments.

The SOLUTION is rtl-sdr-scheduler where once you setup config.json then all transmitted Net meeting are recorded for you to Listen at your convenient time.

Advantages of proposed rtl-sdr-scheduler

• You do not need to worry for gap/Silence between recording...Just evoke the timer and tune frequency, start recording and stop when time reaches.
• Due to "auto_delete_after_days", you delete recording in system so special admin screen NOT required to delete.
• When recording overlap you activate your time sharing else single recording, No load on the system.
• Recording is full meetings no broken fragments...easy to listen.
• I believe every HAM radio operator will use this rtl-sdr-scheduler due to its simplicity...

The proposed rtl-sdr-scheduler CONFIG.JSON may looks like as follows....

{
"scanner_frequencies_scheduler": [
{
"device_serial": "00000001",
"schedule": [
{
"start_time": 20:00:00,
"stop_after": 01:00:00,
"record_freq": 147050000,
"sample_rate": 2048000,
"record_days": 1,2,3,4,5,6,7, # Record all 7 days
"description": "ACMA Daily Net",
"auto_delete_after_days": 7
}
{
"start_time": 10:00:00,
"stop_after": 00:30:00,
"record_freq": 145300000,
"sample_rate": 2048000,
"record_days": 0,2,3,4,0,0,0, # Record only on Tuesday, Wenusday, Thursday
"description": "Somersbay Morning Net",
"auto_delete_after_days": 7
}
]
},
{
"device_serial": "00001399",
"schedule": [
{
"start_time": 17:00:00,
"stop_after": 01:00:00,
"record_freq": 438050000,
"sample_rate": 2048000,
"record_days": 1,2,3,4,5,6,7, # Record all 7 days
"description": "ACMA Evening Net",
"auto_delete_after_days": 7
}
{
"start_time": 21:00:00,
"stop_after": 00:30:00,
"record_freq": 439300000,
"sample_rate": 2048000,
"record_days": 0,2,0,0,0,0,0, # Record only on Tuesday
"description": "Blue Mountain Radio club",
"auto_delete_after_days": 5
}
]
}
],
"devices": {
"rtl_sdr": {
"ppm_error": 0,
"tuner_gain": 29.0,
"offset": 0
},
"hack_rf": {
"lna_gain": 0,
"vga_gain": 0,
"offset": 0
}
},
"recording": {
"max_noise_time_ms": 500,
"min_time_ms": 10000,
"min_sample_rate": 16000
},
"detection": {
"frequency_grouping_size": 10000,
"frequency_range_scanning_time_ms": 64,
"noise_learning_time_seconds": 30,
"noise_detection_margin": 10,
"torn_transmission_learning_time_seconds": 60
},
"output": {
"logs": "sdr/logs",
"file_log_level": "info",
"console_log_level": "info"
},
"cores": 4,
"memory_limit_mb": 0,
"mqtt": {
"hostname": "sdr-broker",
"port": 1883,
"username": "admin",
"password": "password"
}
}

See how you go..It will be your baby...

Regards
Kesh VK2KES

Hi everyone,

Quick question - I noticed in the docs that it's possible to have the the scanner look at two different frequency ranges as it does its scanning. Per the docs:

{ "scanner_frequencies_ranges": [ { "device_serial": "auto", "ranges": [ { "start": 144000000, "stop": 146000000, "sample_rate": 2048000 }, { "start": 440000000, "stop": 442000000, "sample_rate": 2048000 } ] } ] }

When I set this up in my installation I can see the application bouncing back and forth between the two frequency ranges but it's not recording anything - including strong signals that are normally recorded when I have only one range in my config file. Any thoughts or is this not supported with a single device?

First off thanks for creating this, very cool! I have it running in an Ubuntu 22 VM in VMWare. I am not an experienced Linux user but following your instructions I believe I have updated to the new version released today.

My one stumbling block with this is the step size. I guess I am just not wrapping my brain around the concept. In the USA, there is a 7.5 kHz step in the VHF-HI band between 154.650 MHz and about 156.240. 7.5 kHz steps fit that range fine but I can't see any way, especially in the new version, to make that step work. Having to go through that band with 1 kHz steps is not ideal.

Same with any UHF traffic, where the step can be either 6.25 kHz or 12.5 kHz. For example, I should be able to search 482.000 MHz to 484.000 MHz with 12.5 kHz steps as they fit into that span. 1 kHz steps are not logical here either.

Other than that this is a very impressive program. When AM mode is added for aircraft band reception that will be fantastic, but again here in the US in the VHF Aviation band of 118-137 MHz the step size is 25 kHz.

Hopefully I'm just being a dummy with figuring this out; it's entirely possible and/or quite likely!

Thanks,
Scott

Can you please add support for other SDRs or Osmocom library.
Is it possible to add support for recording of multiple frequencies simultaneously?

Thanks.

Is raw branch can be used for development purpose?
Does it make sense to make bugs on the raw branch?
Thank you!

It's cool that you can record the full range but I have only a set of requencies (about 200 values) I want to follow. I guess it's not really useful to create 200 ranges 10kHz bandwithed each. Is there a way to do it effective? Or do you plan to create this function in future?

What are the supported modes? I have been scanning in the air band but haven't found any signals. Is AM supported? Have there been any tests with the AM mode?

Has anyone had any luck running this on a Pi? I cannot get it to work unfortunatly

Hello,

I understand that your Scanner can not decode AM Signals right now.
The possibility to download the RAW file is enough for me, but how to use the file?
No program I tried was able to open the RAW file.

Is the file maybe currupt?

Thank you

Hello,

docker-compose successfully downloads and creates all 3 containers.
But sdr_scanner and sdr_monitor keep restarting with the same error "standard_init_linux.go:219: exec user process caused: exec format error ".

Builing sdr_scanner myself fixed the problem for that container, but there's no way to also simply build sdr_monitor.

Please provide docker images for ARM aswell or a guide to build myself.

Thank you!

I have the software up and running including the 2 Panels .
Can this software scan the above 118-136 mhz AM airband ??
If so how do i get the software to scan it ???

Or can it only scan VHF/UHF ??

Thank you in advance
Regards
Graeme

I ran docker compose up and keep getting the following errors:

sdr-sdr-monitor-reader-1  | [2023-02-08 15:00:16.720][mqtt_reader    ][main         ][WARNING] can not parse, topic: sdr/rtlsdr_stratux:1090/spectrogram
sdr-sdr-monitor-reader-1  | [2023-02-08 15:00:16.720][mqtt_reader    ][Transmission ][INFO   ] sdr/rtlsdr_stratux:1090/transmission
sdr-sdr-monitor-reader-1  | [2023-02-08 15:00:16.720][mqtt_reader    ][main         ][WARNING] can not parse, topic: sdr/rtlsdr_stratux:1090/transmission
sdr-sdr-monitor-reader-1  | [2023-02-08 15:00:16.172][mqtt_reader    ][Transmission ][INFO   ] sdr/rtlsdr_stratux:1090/transmission
sdr-sdr-monitor-reader-1  | [2023-02-08 15:00:16.172][mqtt_reader    ][main         ][WARNING] can not parse, topic: sdr/rtlsdr_stratux:1090/transmission
sdr-sdr-monitor-reader-1  | [2023-02-08 15:00:16.272][mqtt_reader    ][Transmission ][INFO   ] sdr/rtlsdr_stratux:1090/transmission
sdr-sdr-monitor-reader-1  | [2023-02-08 15:00:16.272][mqtt_reader    ][main         ][WARNING] can not parse, topic: sdr/rtlsdr_stratux:1090/transmission
sdr-sdr-monitor-reader-1  | [2023-02-08 15:00:16.272][mqtt_reader    ][Transmission ][INFO   ] sdr/rtlsdr_stratux:1090/transmission
sdr-sdr-monitor-reader-1  | [2023-02-08 15:00:16.272][mqtt_reader    ][main         ][WARNING] can not parse, topic: sdr/rtlsdr_stratux:1090/transmission
sdr-sdr-monitor-reader-1  | [2023-02-08 15:00:16.372][mqtt_reader    ][Transmission ][INFO   ] sdr/rtlsdr_stratux:1090/transmission
sdr-sdr-monitor-reader-1  | [2023-02-08 15:00:16.372][mqtt_reader    ][main         ][WARNING] can not parse, topic: sdr/rtlsdr_stratux:1090/transmission
sdr-sdr-monitor-reader-1  | [2023-02-08 15:00:16.473][mqtt_reader    ][Transmission ][INFO   ] sdr/rtlsdr_stratux:1090/transmission
sdr-sdr-monitor-reader-1  | [2023-02-08 15:00:16.473][mqtt_reader    ][main         ][WARNING] can not parse, topic: sdr/rtlsdr_stratux:1090/transmission
sdr-sdr-monitor-reader-1  | [2023-02-08 15:00:16.473][mqtt_reader    ][Transmission ][INFO   ] sdr/rtlsdr_stratux:1090/transmission

Nothing is showing up in the web UI either. Any idea what's going on here?

Here is my attempt to install the system in ARMBIAN 64
i get this error after all containers are pulled (except this one)
Attaching to sdr-sdr-broker-1, sdr-sdr-monitor-reader-1, sdr-sdr-monitor-server-1, sdr-sdr-monitor-setup-1, sdr-sdr-scanner-1
Error response from daemon: failed to create endpoint sdr-sdr-broker-1 on network sdr_default: failed to add the host (veth170fb26) <=> sandbox (veth14dac1a) pair interfaces: operation not supported

Any hint ?

Thanks in advance

Hi, your project is amazing. It works absolutely great.
But I would have a query, I would need to write data (frequency, file name and time) to the SQL database (for example via http request)
Could you please advise me?
Thank you so much

Around 12 years ago I was building MDC1200 & GE-Star signaling encoders based on PIC Microchip MCUs.
I do have the decoder section as well.
Would you be interested on decode these ? I can send you the C source code .
It would be nice to see which ANI IDs are involved in the recording.

Hi , I can't set the frequency range with one SDR,
it still says samples not ok, start: 144.000 kHz, stop: 146.000 kHz, step: 001.000 Hz, bandwidth: 002.048 kHz
samples not ok, start: 440.000 kHz, stop: 442.000 kHz, step: 001.000 Hz, bandwidth: 002.048 kHz
In the previous version of the scanner it worked perfectly.
Here is my config:
{
"scanner_frequencies_ranges": [
{
"device_serial": "auto",
"ranges": [
{
"start": 144000000,
"stop": 146000000,
"step": 1000,
"sample_rate": 2048000
},
{
"start": 440000000,
"stop": 442000000,
"step": 1000,
"sample_rate": 2048000
}
]
}
],
"devices": {
"rtl_sdr": {
"ppm_error": 40,
"tuner_gain": 10.0,
"offset": 0
},
"hack_rf": {
"lna_gain": 0,
"vga_gain": 0,
"offset": 0
}
},
"recording": {
"max_noise_time_ms": 500,
"min_time_ms": 2000,
"min_sample_rate": 16000,
"max_concurrent_recordings": 10
},
"detection": {
"frequency_grouping_size": 10000,
"frequency_range_scanning_time_ms": 64,
"noise_learning_time_seconds": 30,
"noise_detection_margin": 20,
"torn_transmission_learning_time_seconds": 60
},
"output": {
"logs": "sdr/logs",
"file_log_level": "info",
"console_log_level": "info"
},
"mqtt": {
"hostname": "sdr-broker",
"port": 1883,
"username": "admin",
"password": "password"
}
}

Hi @shajen,

How can i configure the path to recorded audio files?
Or how can i get recorded audio files?

Old setting from config.json doesn't work.

"output": {
"recordings": "/home/pi/recs",

Hello and thank you for what seems like a great piece of sw. Having issues getting to the localhost for the UI. I followed the steps to build locally with docker. After messing with the typical rtl-sdr blacklist settings I was able to get it running using docker compose up. It is clearing running in the command line and I can even see it recording transmissions when keying up my radio, however, I can not get to the UI on the localhost. I tried 0.0.0.0:8000, 127.0.0.1:8000, localhost:8000, and many more with no joy.

Are there additional steps required when building locally to get the web server running? Running raspbian bullseye on a libre computer AML-S905X-CC. My logs.txt is attached below. Thanks.

Hi first of all, very good work !!!
I wonder if there is a posibility to listen some/all files transmition with out having to play one by one.
Like you select some files and push only one play button.
Or to have an option that if checked, when the browser end the listening of one file start automaticaly the listening of the next

As said before, Good work :-)
Best regards
Nacho

sdr-sdr-monitor-reader-1 | ValueError: Incorrect timezone setting: -03

On a few of the screens in the admin interface where you can add a device and/or a transmission the text is appearing in a language different than English (see attached screenshot). I'd be happy to translate and do a PR but can't find exactly where you are pulling the language resources from (I am not as familiar with Django I must admit). There is a prompt for a file at the bottom of this screen but I cannot for the life of me figure out what it is for, and it appears to be required!

Thanks.

Can you share a full config.json implementing two sdr's.

I've added per instructions but it than fails

log of failed run with ignored frequencies
https://justpaste.it/aribq

config with ignored frequencies added
https://justpaste.it/2x752

working config with two sdr's
https://justpaste.it/anth4

appreciate your help/insight on where I am going wrong in my edits

Hello.
I upgraded to the latest version and when I have multiple band scanned with one SDR, it no longer crashes after the first recording.
But it still crashes for me, it lasted about 5 hours this time:

sdr-sdr-monitor-reader-1 | [2023-02-09 23:40:53.164][mqtt_reader ][Spectrogram ][INFO ] save, rtlsdr_00000001, 2023-02-09 23:40:53.109, 438000000 - 440000000, 2.0 kB, -65.14 dBfs
sdr-sdr-monitor-reader-1 | [2023-02-09 23:40:53.466][mqtt_reader ][Spectrogram ][INFO ] save, rtlsdr_00000001, 2023-02-09 23:40:53.399, 445000000 - 447000000, 2.0 kB, -59.49 dBfs
sdr-sdr-scanner-1 | rtlsdr_demod_read_reg failed with -7
sdr-sdr-scanner-1 | r82xx_write_arr: i2c wr failed=-9 reg=17 len=1
sdr-sdr-scanner-1 | rtlsdr_demod_write_reg failed with -9
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.749325] [error ] [Scanner ] exception: set center frequency error
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.749352] [info ] [Scanner ] stop thread id: 23
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.759626] [info ] [SamplesWrk ] stop thread id: 19
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.759736] [info ] [spectrogram] deinit
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.759750] [info ] [fft ] deinit
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.759882] [info ] [SamplesWrk ] stop thread id: 20
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.759980] [info ] [spectrogram] deinit
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.759993] [info ] [fft ] deinit
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.760074] [info ] [SamplesWrk ] stop thread id: 21
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.760154] [info ] [spectrogram] deinit
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.760164] [info ] [fft ] deinit
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.760249] [info ] [SamplesWrk ] stop thread id: 22
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.760352] [info ] [spectrogram] deinit
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.760410] [info ] [fft ] deinit
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.771296] [info ] [RtlSdr ] close device, index: 0, name: Generic RTL2832U OEM, serial: 00000001
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.929286] [info ] [Mqtt ] stop thread id: 9
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.929655] [info ] [main ] stop app auto_sdr
sdr-sdr-scanner-1 | [2023-02-09 23:40:55.929674] [info ] [main ] stop thread id: 7
sdr-sdr-broker-1 | 1675982455: Client auto-194E1C2E-EA88-AEEE-C231-86CA0090E3B1 disconnected.
sdr-sdr-scanner-1 exited with code 0

^CGracefully stopping... (press Ctrl+C again to force)
Aborting on container exit...

I set the log level to trace and will provide full log once it happens again.
Device is normal cheap dongle with R820T, Ubuntu 22.04.1 in VMWare Player (VM have 8 of AMD 5950X cores + 16GB RAM) with RTL-SDR about 5 days old from GIT. I will later configure it on old laptop to see if the VM is the problem.

Otherwise I like the SW very much, but I would appreciate a full list of possible config values to be documented.
(and of course other demodulators later)

Hi Shajen,
first of all, let me thank you for great piece of software, I will probably donate to support you.
I do not know how much time or passion you have for it, but let me suggest some UI improvements for the future.

1. it would be great if you could implement frequency mapping to a name. So in the Frequency column, we could see a name for a frequency. In some external file which can be given to the container on load so it can be easily transferred maybe? Or in the Admin section, but with possibility to import and export.
2. the slider for moving time in the recording should be much wider, to be able better move inside the recording. But it seems this is some kind of browser feature, because the column "Decoded file" have a different appearance in Edge and in Firefox. So not sure if that would be possible.
3. it would be great to be able to see ignored frequencies in the spectrogram. Something like a grey line overlay over the whole spectrogram. Or if that would be difficult to do, a mark on the top gray frequency bar (like a red dot or bar or triangle) would be also great. Would be helpful when analyzing the spectrograms.
4. the AM decoder would be nice for people who want to record the air band.
5. maybe some kind of GUI configuration tool for the config file with all the possible options, but that is the last thing to do (after everything else is done), because people will probably want it for multiple platforms including Windows, for cases where is no X server on their Linux boxes.

Nothing else comes to mind after few days of use, which I think is a good thing.
73

This is a very interesting !! I could install it correctly , using ubuntu 22.04 20gb mem 256gb HDD i7 proc.
But however I have no luck recording anything.
I do have a NESDR SMART which I tested and works fine in linux . I have followed the instructions but no joy I do transmit within the range ( so far I'm following the example 144-146mhz) I'm using the "Auto" config.
Is there a discord group or google group for this .?
Any help woyuld be appreciated

Running the start up command in Ubuntu has a spelling mistake
it si ./build/auto-sdr config.json in docs but should be as below "-" hyphen should be underscore "_"
./build/auto_sdr config.json

All start up and it scans the frequency but how do I get to the Admin console.
The program dose not seem to listen on 8088 or 8000 where can I get or set the port details or do I need to run something else.
I notes that the program is doing something with MQTT but not sure what to do next to get the admin console?

FM Frequencies are working perfectly, however I set a range for aircraft (124000000 - 126000000) and while it picks up the transmissions, the recordings won't play back.

config:
{
"start": 124000000,
"stop": 126000000,
"step": 1000,
"sample_rate": 2048000
}

You can see an example on this on a AM freq of the public view of the app:
https://freqs.avairspace.com/sdr/transmission/1846
The play button and download show a broken audio file.

To compare to a working FM freq:
https://freqs.avairspace.com/sdr/transmission/1839
which plays fine.

I put the trace log level up on pastebin
https://pastebin.com/4Sfc17SN

Hi Shajen,

SDR-Scanner will become decent product if you nurture well....

Within 3 hrs of transmition activity there are hundred of transmitions which audio is less then 10 second. This looks select and delete nightmare in admin.

Please provide Auto-clean or Auto-delete on a criteria to be setup in "Admin" so that sdr-scanner system Auto-delete them in background. We do not wants to record tee, too and tow-tow and listen.

Please do urgently...Thank you.. Kesh

I'm wanting to build an arm64 version of each, but I can't find the source for the srd-monitor docker image. Is that not OSS?

For me it just records noise no matter if i configure 0.0 or 40.2 gain in the config.

Here are three .mp3 for example but i got 100 in like 15 minutes. It is a zip as i can't upload .mp3
rtl-sdr-scanner.zip

So how to prevent this?

x-special/nautilus-clipboard
copy
file:///home/debian/Pictures/Error_sdr.png

I am using RTL SDR(RTL2832U R820T2 TCX0+BIAS T+HF) to intecept motorola (GP338) communication on channel 16 in a test environment.

The auto-sdr starts and automatically stop with error. Error in screenshot.
kindly help resolve the issue.

PS - My config.json file is in the same config as provide by you!!

thanks,
Amina

Hi! Is it possible to add compatibility with the new procps (procps2-dev)?

Hi,
I tried to delete all ca. 15000 Transmissions files in my Database but if i select all 15000 Files at once and try to delete i get a "400 bad request"

So i delete 14000 in 100 Steps and the last 1000 i could delete all at once.

Thank you for your work!

Hi :)
Assuming I have multiple SDR dongles attached, how do I select which one this will run on?

Nuno

@shajen

i try to monitor 3 frequencyranges but can not use a sample rate above 2mhz (hackrf can have a sample rate up to 20Mhz)
when i run the scanner and do a test sending with a radio 500m away its will be not recorded. if i have only 1 frequencyrange with 2mhz bandwith (eg: 144-146) it works but when i have a wider frequency range like 118-130 or 146-173 it record nothing.

Second: in the Readme you say for starting run: "./build/auto-sdr config.json" but its "auto_sdr"
Question can i also add ignored frequencies like in the old version?

my config:
{
"scanner_frequencies_ranges": [
{
"device_serial": "auto",
"ranges": [
{
"start": 146010000,
"stop": 173010000,
"step": 1000,
"sample_rate": 2048000
},
{
"start": 58000000,
"stop": 87000000,
"step": 1000,
"sample_rate": 2048000
},
{
"start": 446000000,
"stop": 446200000,
"step": 1000,
"sample_rate": 2048000
}
]
}
],
"devices": {
"hack_rf": {
"lna_gain": 16,
"vga_gain": 42,
"offset": 0
}
},
"recording": {
"max_noise_time_ms": 50,
"min_time_ms": 2000,
"min_sample_rate": 16000,
"max_concurrent_recordings": 10
},
"detection": {
"frequency_grouping_size": 10000,
"frequency_range_scanning_time_ms": 64,
"noise_learning_time_seconds": 30,
"noise_detection_margin": 20,
"torn_transmission_learning_time_seconds": 60
},
"output": {
"logs": "sdr/logs",
"recordings": "sdr/recordings",
"file_log_level": "info",
"console_log_level": "info"
},
"mqtt": {
"hostname": "sdr-broker",
"port": 1883,
"username": "admin",
"password": "password"
}
}

Hi
How can i delete all recordings and waterfalls?

Thank you

Hi.. ist the interface compatible with rsp2?

Firstly, this a really great application - thanks!

I had tried to use a step size of 2500. Took me a while to figure out what was causing no rtl-scanner-sdr-monitor-reader output. Seemed like no scanning was happening. When I changed it back to 1000 it works fine. Am I misunderstanding what step means here?
Did not work:

{
      "device_serial": "02",
      "ranges": [
        {
          "start": 115000000,
          "stop": 136000000,
          "step": 2500,
          "sample_rate": 2048000
        }
      ]
    },

Worked:

{
      "device_serial": "02",
      "ranges": [
        {
          "start": 115000000,
          "stop": 136000000,
          "step": 1000,
          "sample_rate": 2048000
        }
      ]
    },

Can post my full config and console output but nothing seemed to stand out. Just no output from the rtl-scanner-sdr-monitor-reader container.

Get the following error when running "docker compose up":

Error response from daemon: error gathering device information while adding custom device "/dev/bus/usb": no such file or directory

Hackrf is connected and reports status via hackrf_info

xxxxxxxx@xxxxxx:~/sdr$ hackrf_info
hackrf_info version: unknown
libhackrf version: unknown (0.6)
Found HackRF
Index: 0
Serial number: 000000000000000014d463dc2f1351e1
Board ID Number: 2 (HackRF One)
Firmware Version: 2022.09.1 (API:1.06)
Part ID Number: 0xa000cb3c 0x0053434d

Full trace running docker compos up:

kobus@Dozer:~/sdr$ docker compose up
[+] Running 6/6
⠿ Network sdr_default Created 0.0s
⠿ Container sdr-sdr-broker-1 Created 0.1s
⠿ Container sdr-sdr-monitor-setup-1 Created 0.1s
⠿ Container sdr-sdr-scanner-1 Created 0.1s
⠿ Container sdr-sdr-monitor-server-1 Created 0.1s
⠿ Container sdr-sdr-monitor-reader-1 Created 0.1s
Attaching to sdr-sdr-broker-1, sdr-sdr-monitor-reader-1, sdr-sdr-monitor-server-1, sdr-sdr-monitor-setup-1, sdr-sdr-scanner-1
sdr-sdr-broker-1 | 1677113658: mosquitto version 2.0.15 starting
sdr-sdr-broker-1 | 1677113658: Config loaded from /mosquitto/config/mosquitto.conf.
sdr-sdr-broker-1 | 1677113658: Opening ipv4 listen socket on port 1883.
sdr-sdr-broker-1 | 1677113658: Opening ipv6 listen socket on port 1883.
sdr-sdr-broker-1 | 1677113658: mosquitto version 2.0.15 running
sdr-sdr-monitor-setup-1 | timezone: Etc/UTC
sdr-sdr-monitor-setup-1 | Operations to perform:
sdr-sdr-monitor-setup-1 | Apply all migrations: admin, auth, contenttypes, graphs, logs, sdr, sessions
sdr-sdr-monitor-setup-1 | Running migrations:
sdr-sdr-monitor-setup-1 | No migrations to apply.
sdr-sdr-monitor-setup-1 exited with code 0
Error response from daemon: error gathering device information while adding custom device "/dev/bus/usb": no such file or directory

Am I missing a configuration step?

Thank you for all your great work on this tool.

So i have followed the the instructions .cd into rtl-sdr-cpp folder $cmake -B build -DCMAKE_BUILD_TYPE=Release.
On doing this i get an error

Have googled for any help but all i get is confusing info .
This project looks great apart from the fustrating holdup .
Hope someone can come up with a simple remedy i can follow.
Thankyou and regards
graeme

I hope you can help me with this one. I've now successfully installed the software on Ubuntu and on Debian (two different machines) with the latest pull and I get the same problem with my RTL-SDRs (I have two that have been tested).

After a few minutes of running the app, it stops collecting transmissions, and when I check the docker logs, I see usb_claim_interface error -6 followed by an exit code 0. If I try and restart or stop/start docker, it refuses to start after that, citing the same error in the logs, exiting out.

I'm able to use other software with the RTL-SDR (such as dump1090), to test that it isn't the issue.

Once this error state occurs, the only way to mitigate it appears to be rebooting the system. After a full reboot the interface claim is removed and I can run the software again, but it will soon hit this error after several (about 7-8) audio files are processed. I was scanning 470-472Mhz which had quite activity (about 7 broadcasts a min).

First a big thank you to Shajen for an awesome app. I have been playing with this all week and had some great results on the 2 meter band listening for the most active repeaters in my area.

What I'd like to do next is have it scan popular packet radio frequencies (including APRS) to see what kind of activity is happening around me. So far I've been able to get only one packet transmission recorded (my own) but haven't been able to get anything else to save. I reduced the minimum record time to see if maybe the packet transmissions are too short to get picked up.

Any thoughts or tips?