about twice a month I get an email from Dimitri that my station 1433 has unwanted behaviour.
2026-09-07T14:39:27.012432000Z netrigctl_close: done
2026-09-07T14:39:28.452989000Z INFO satnogsclient.observer.observer Observation 14939607 finished.
2026-09-07T14:39:28.454000000Z ERROR satnogsclient.observer.observer Waterfall data array is empty
2026-09-07T14:39:41.242561000Z INFO satnogsclient.scheduler.tasks Upload of audio recording for observation 14939607 successful.
Allways solved the same way, hackrf disconnect usb, reconnect and running again.
when in error state:
pe2bz@raspberrypi:~ $ timeout 10 hackrf_transfer -r /dev/null -f 100000000
call hackrf_set_sample_rate(10000000 Hz/10.000 MHz)
call hackrf_set_hw_sync_mode(0)
call hackrf_set_freq(100000000 Hz/100.000 MHz)
Stop with Ctrl-C
0.0 MiB / 1.000 sec = 0.0 MiB/second, average power nan dBfs
Couldn’t transfer any bytes for one second.
Exiting… hackrf_is_streaming() result: HACKRF_TRUE (1)
But
pe2bz@raspberrypi:~ $ sudo usbreset 001/003
Resetting HackRF One … ok
pe2bz@raspberrypi:~ $ timeout 10 hackrf_transfer -r /dev/null -f 100000000
call hackrf_set_sample_rate(10000000 Hz/10.000 MHz)
call hackrf_set_hw_sync_mode(0)
call hackrf_set_freq(100000000 Hz/100.000 MHz)
Stop with Ctrl-C
19.9 MiB / 1.000 sec = 19.9 MiB/second, average power -29.1 dBfs
19.9 MiB / 1.000 sec = 19.9 MiB/second, average power -29.1 dBfs
19.9 MiB / 1.000 sec = 19.9 MiB/second, average power -29.1 dBfs
20.2 MiB / 1.000 sec = 20.2 MiB/second, average power -29.1 dBfs
19.9 MiB / 1.000 sec = 19.9 MiB/second, average power -29.1 dBfs
So for now I did the cheap and dirty, cronjob at 04:30 which usbresets the hackrf even it it’s running and even if there’s an observation going.
I am considering to add this as command at the start of an observation instead, does that make sense ?
Ben