Gr-satellites UPloader

1

You may remember DK3WN’s Online Telemetry Forwarder.
It recognizes a satellite by its callsign or unique pattern and uploads the received data automatically to (SatNOGS) database using the satellite’s associated Norad ID.
It’s still doing this fine job, but is not updated with new satellites any longer.

I’ve now built something equivalent, the gr-satellites UPloader, based on gnuradio.

It uses the gr-satellites block Check AX.25 address to recognize the source or destination callsign of a received packet and the block Telemetry Forwarder to upload the data (switchable).
Additionally, it counts the packets, prints its content in hex (switchable) and stores the data as .kss and .hex files named after the satellite.
The uploader can be updated easily via a .ini file with new satellites (callsigns, Norad IDs) and settings for your modem (url, kiss port) and target database (url, sender’s callsign, coordinates).

gr_satellites_uploader
gr_satellites_uploader1380×569 96.8 KB

Packets received by (in this example) the High-Speed SoundModem are timestamped, counted, displayed in hex (if activated), stored as .hex and .kss, and of course uploaded (if activated).

Using this uploader prevents you from uploading non AX.25 packets.

If you also have the problem to decode yourself (mostly near TCA) while digipeating, this uploader also prevents uploading of packets sent by you (instead of your digipeated packets).
This is done by the updated block Check AX.25 address which is checking the so-called hbit.

Have fun.
73
Daniel, dl7ndr

gr_satellites_uploader.zip (1.1 MB)
Currently supporting up to 16 satellites.

Preconfigured: GRBAlpha, GRBbeta, BDSat-2, ISS (RS0ISS, NA1SS), UMKA-1, StratoSat TK1, SONATE-2, Veronika, LASARSat, CroCube, YOMOGI, QUBE, NO-44 (W3ADO, PCSAT), UWE4.

5 Likes
2

Nice developement, but a correction on the Telemetry Forwarder.

The Online Telemetry Forwarder was replaced with GetKiss+ and if you make sure you use a recent up to date TLE set all new satellites will be available to forward to the SatNOGS database.

image
image747×405 6.37 KB

As an example ZIMSAT-2 one of the latest satellites launched and active.

The TLEFILE option in conf.ini determines what TLE set is used

3

I know GetKISS+ very well, of course.
However, it’s not a replacement for Online Telemetry Forwarder.

Online Telemetry Forwarder recognizes the satellites automatically, GetKISS+ doesn’t. You have to choose the satellite manually.
Also in contrast, once a satellite is chosen, all received data will be uploaded to the associated Norad ID regardless of non AX.25 data and those received from different satellites.

Looking at the ability to be extended, GetKISS+ is a step forward.
From the perspectives of comfort and safety, it’s a step backwards.

I tried to combine features from both, the ability to extend / update from GetKISS+ with the comfort and safety from Online Telemetry Forwarder.

1 Like
4

You are right, there is no satellite identity auto detect based on received frames with GetKISS+.

Not all satellites send identity frames and then automation becomes difficult and manual selecting is the best trade-off.

On the other hand if the id is known, it is a good idea to try and use it.

Good luck with the further development.

5

This is why I referred to Online Telemetry Forwarder.

For satellites not using AX.25 there is for example GetKISS+ or my SatNOGS UPloader using block Check Hex String.

1 Like