← Back to context

Comment by toomuchtodo

10 hours ago

I have to dive in a bit more to give good and specific guidance/context, but fundamentally, your system will require a shim to "speak" $UAT_SOURCE and the output this would expect, assuming the source was an sdr. Want help writing the code for this? Specs to build requirements RNO-G in -> SDR out are welcome.

https://airplanes.live/hardware/

https://sdr-enthusiasts.gitbook.io/ads-b/ might also be of value.

4 comments

toomuchtodo

Reply
cozzyd  8 hours ago

yes, we have an SDR running some form of dump1090, then we are parsing json output from that and sticking it in a local sqlite database (we cycle databases once per day). Then that sqlite database eventually gets copied down. There are plans to improve our system to read a bit more directly but on low priority. It looks like these tools expect some format called BEAST that maybe can already be generated by dump1090, and then it's just a TCP stream to some endpoint?

  • rufo  8 hours ago

    Pretty much that. The SDR enthusiast's docker guide the parent comment linked to uses this ultrafeeder container, which has instructions on how to connect directly to dump1090 running on a port. Pairing that[1] plus the rest of the guide instructions should get you a decent ADS-B setup that can feed any of the services you might want - and if you don't want to use the Docker container(s), you should be able to at least use the services and configuration they use as a guide.

    [1]: https://github.com/sdr-enthusiasts/docker-adsb-ultrafeeder/t...