Good day Bill,
It is a bit of a mystery why Satellites that should produce a good signal aren’t in your case.
There is one settings that could be influencing this behavior and that is the SDR LO correction, set with ppm value.
If the LO correction would be very high, then it is possible that currently the received signals are outside the tuned range, bw.
Connecting the SDR to a computer with SDR software like, GQRX, SDR++, SDR#, SDRConsole and manually try to received signals that would give you a good indication if the SDR is receiving signals at the correct frequency, you can use a local Ham Radio repeater or another stable signal preferable with a locked freq.
Now a days it is possible to measure the ppm correcting with the rtl_test utility, this can be done in the following way:
Start rtl_test -d 0 -p and keep it running until the cumulative PPM: value stabilizes, that could be a few minutes.
example output:
Found 1 device(s):
0: RTLSDRBlog, Blog V4, SN: 40004541
Using device 0: Generic RTL2832U OEM
Found Rafael Micro R828D tuner
RTL-SDR Blog V4 Detected
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
Sampling at 2048000 S/s.
Reporting PPM error measurement every 10 seconds...
Press ^C after a few minutes.
Reading samples in async mode...
Allocating 15 zero-copy buffers
lost at least 168 bytes in buffer 0
real sample rate: 2047993 current PPM: -3 cumulative PPM: -3
real sample rate: 2047994 current PPM: -3 cumulative PPM: -3
real sample rate: 2047992 current PPM: -4 cumulative PPM: -3
real sample rate: 2047985 current PPM: -7 cumulative PPM: -4
real sample rate: 2047997 current PPM: -1 cumulative PPM: -4
real sample rate: 2047982 current PPM: -8 cumulative PPM: -4
real sample rate: 2047990 current PPM: -5 cumulative PPM: -4
real sample rate: 2047989 current PPM: -5 cumulative PPM: -5
real sample rate: 2047993 current PPM: -3 cumulative PPM: -4
real sample rate: 2047998 current PPM: -1 cumulative PPM: -4
real sample rate: 2047985 current PPM: -7 cumulative PPM: -4
real sample rate: 2047990 current PPM: -4 cumulative PPM: -4
real sample rate: 2047988 current PPM: -6 cumulative PPM: -4
real sample rate: 2047989 current PPM: -5 cumulative PPM: -4
real sample rate: 2047981 current PPM: -9 cumulative PPM: -5
real sample rate: 2047994 current PPM: -3 cumulative PPM: -5
real sample rate: 2047996 current PPM: -2 cumulative PPM: -4
Some information on running the command on your docker environment, there can be a chicken and the egg challenge. My best guess is, that that the rtl_test command is only part of the docker container so it needs to be running, but at the same time if an observation is running the rtl_test command can’t connect to the SDR because it is already in use. I hope I make myself clear.
Running the command with the container enabled, normal operations:
docker exec satnogs_satnogs-client rtl_test -d 0 -p
Jan | PE0SAT