Observation 12914367: TUBIN (48900)

Regarding Observation 12914367

Why is not Tubin decoded?

I guess the gr-satellites integration isn’t activated and that is the only way a satnogs client can decode TUBIN.

Jan | PE0SAT

As far as I know, is activated….

Jan, you are always right…. Was “False” in satnogs-setup

I thought it was active because I set the PRE and POST observation scripts

Many thanks

With SatNOGS-Client 2.1 it is part of the client and doesn’t need the PRE and POST scripts.
The scripts don’t exist so you should disable them.

Jan | PE0SAT

1 Like

After activation of gr-satelites still not decoding Tubin sat with good signal

I had a quick look

cat /usr/lib/python3/dist-packages/satellites/satyaml/TUBIN.yml

name: TUBIN
norad: 48900
telemetry_servers:
  - SIDS http://fachgebiet.rft.tu-berlin.de/ham/telemetry/send
data:
  &tlm Telemetry:
    unknown
transmitters:
  4k8 FSK downlink:
    frequency: 435.950e+6
    modulation: FSK
    baudrate: 4800
    deviation: 1200
    framing: Mobitex-NX
    data:
    - *tlm

This seems to be the old Mobitex solution and not using the new one, so it is missing the correct deframer.

Looking at the gr-satelites version this is already the GNURadio 3.10.x based release and that can’t use the GNURadio 3.8 based Mobitex OOT.

gr_satellites --version

gr_satellites v5.7.0
Copyright (C) 2020 Daniel Estevez
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

So we need gr-satellites 5.8 or higher for the new Mobitex deframer.

The current image: 'librespace/satnogs-client:master-unstable' has gr-satellites 5.8 and the updated yaml file. At the moment I don’t know how to alter the image when using the satnogs-setup ansible solution.

@kerel @Acinonyx Is there a way to move to another image ?

Jan | PE0SAT

1 Like