NOTE: as of this writing (2019-7-7) the raspberry pi image we generate is not compatible with the RPi 4, and the gr-satnogs package we generate is not compatible with buster. This is a compatibility testing report, not a howto.
That said - this weekend I’ve tested SatNOGS on a Raspberry Pi 4 (2GB), running buster, and it pretty much all works fine. It is currently running on #300 but I’m not sure how long I will leave it in that config as I’m concerned about heat between the pi 4 and the airspy I have with it in the enclosure.
I ran the ansible scripts, minus the gr-satnogs install which is pinned to the older gnuradio dependencies. Everything else works fine.
I built gr-satnogs, no issues there either. In fact, the build time dropped from 4:35 on a rpi3b+ to 2:30 on the 4.
As you can see the rpi4 is pretty bored with the MSK script. The BPSK script will cause it to churn however.
Unfortunately its still not enough to take the full sample rates of the airspy or hackrf, however in my testing I’ve discovered that the overruns are occurring only once the doppler correction block kicks in (prior to that, there are no drops). I set the update frequency very high in the code and it didn’t fix the issue. Something to maybe look into @surligas? With USB 3.0, spyserver on the rpi4 handles the 10M rate just fine.
Don’t let the poor results on #300 reflect on the pi, I’ve been messing with gain settings and the antenna is not ideal at the moment.
So - I think we need to update the gnuradio dependencies pinned in gr-satnogs-package to 3.7.13, and update pi-gen to buster and everything else should run fine! /cc @Acinonyx
I haven’t tried this setup in the rpi3 yet to see if anything breaks, that will come another day.