Regarding Observation 9263111 …
Is there a specfic reason for the client to not demodulate the Signal. In the waterfall it looks pretty fine to me and should be demodulatable? Or how can i try to decode it from the .ogg file?
Tanks in advance
Kilian
Hi,
quick answer is gr-satellites.
gr_satellites 58472 --wavfile satnogs_9263111_2024-03-26T20-53-34.ogg or if you’re on gnuradio 3.8 you need to convert it to wav first with sox or similar.
The stations doing it live is probably using one of my integrations:
satnogs_gr-satellites
docker addons, grsat
Tank you!
I am having the same issue, great passes ( SatNOGS Network - Observation 10016397 ), but no demod data. I am using the raspberry distro. I am confused by the statement “Now finally completely integrated in satnogs stable client.” from GitHub - kng/satnogs_gr-satellites: First try on combining gr-satellites with the satnogs-client and satnogs-flowgraphs. Is the entire satnogs_gr-satellites in the client download or that it works but I have to go through the steps discussed at the GitHub for satnogs_gr-satellites. I am a bit challenged with learning with the pi, but I am game.
It is always a challenge to find satellite information such as the radio, modulation and framing used.
Especially commercial satellites in the 400 MHz range often do not share details.
In that case we need to try and reverse engineer the information and update the satnogs database with the correct transmitter definition.
With the help of you observation and the great gr-satellites toolbox I found that this observation is using a GOMSpace AX100 radio with ASM+Golay framing at 2400 baud.
After that I proposed a new transmitter definition in the satnogs database and it is now available for creating new obs in the network.
The gr-satellites yml used:
name: BRIO
norad: 43813
data:
&tlm Unknown telemetry:
unknown
transmitters:
2k4 FSK AX100 ASM+Golay downlink:
frequency: 400.595e+6
modulation: FSK
baudrate: 2400
framing: AX100 ASM+Golay
data:
- *tlm
Decoding your obs:
gr_satellites BRIO.yml --wavfile 10016397.ogg --samp_rate 48e3 (convert ogg to wav if you use the 3.8 gr-satellites branch)
************************************
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 2k4 FSK AX100 ASM+Golay downlink))
pdu length = 207 bytes
pdu vector contents =
0000: 42 ea c9 03 10 00 00 00 04 00 00 66 b9 44 c8 01
0010: 01 00 00 00 c3 88 70 60 c3 88 70 60 c3 88 70 60
0020: c3 88 70 60 3c a3 d7 0a 00 00 00 00 40 20 00 00
0030: 66 b9 47 20 01 01 00 00 00 c3 88 70 60 c3 88 70
0040: 60 c3 88 70 60 c3 88 70 60 3c a3 d7 0a 00 00 00
0050: 00 bf 80 00 00 66 b9 49 78 01 01 00 00 00 c3 88
0060: 70 60 c3 88 70 60 c3 88 70 60 c3 88 70 60 3c a3
0070: d7 0a 00 00 00 00 c0 a0 00 00 66 b9 4b d0 01 01
0080: 00 00 00 c3 88 70 60 c3 88 70 60 c3 88 70 60 c3
0090: 88 70 60 3c a3 d7 0a 00 00 00 00 c1 08 00 00 66
00a0: b9 4e 28 01 01 00 00 00 c3 88 70 60 c3 88 70 60
00b0: c3 88 70 60 c3 88 70 60 3c a3 d7 0a 00 00 00 00
00c0: c0 f0 04 6d 65 51 f1 c1 f0 be 1e 1d bc 7f 1f
Thank you for your response.
I found out from a friend that the BRIO satellite uses a variable baud rate depending on communication conditions. Does that mean that gr-satellites would need multiple entries for BRIO or is there a way for it to check multiple rates?
Thankl you.
This should work, but maybe needs some tuning
name: BRIO
norad: 43813
data:
&tlm Unknown telemetry:
unknown
transmitters:
1k2 FSK AX100 ASM+Golay downlink:
frequency: 400.595e+6
modulation: FSK
baudrate: 1200
framing: AX100 ASM+Golay
data:
- *tlm
2k4 FSK AX100 ASM+Golay downlink:
frequency: 400.595e+6
modulation: FSK
baudrate: 2400
framing: AX100 ASM+Golay
data:
- *tlm
4k8 FSK AX100 ASM+Golay downlink:
frequency: 400.595e+6
modulation: FSK
baudrate: 4800
framing: AX100 ASM+Golay
data:
- *tlm
9k6 FSK AX100 ASM+Golay downlink:
frequency: 400.595e+6
modulation: FSK
baudrate: 9600
framing: AX100 ASM+Golay
data:
- *tlm
Thank you!
This means the udp output from -flowgraphs, the relevant variables in -config and the -client, if you look at the readme history you can see the different monstrositys of workarounds I had in the beginning.
I very much appreciate all your efforts. I am seeing demod data.
THEA, norad: 43796 has the same xmtr characteristics as BRIO. Here is a link to my latest THEA observation. SatNOGS Network - Observation 10033272
Copying your yml and substituting gives:
name: THEA
norad: 43796
data:
&tlm Unknown telemetry:
unknown
transmitters:
1k2 FSK AX100 ASM+Golay downlink:
frequency: 400.595e+6
modulation: FSK
baudrate: 1200
framing: AX100 ASM+Golay
data:
- *tlm
2k4 FSK AX100 ASM+Golay downlink:
frequency: 400.595e+6
modulation: FSK
baudrate: 2400
framing: AX100 ASM+Golay
data:
- *tlm
4k8 FSK AX100 ASM+Golay downlink:
frequency: 400.595e+6
modulation: FSK
baudrate: 4800
Am I able to upload this to the Satnogs database or does someone else have to do this?
The yaml structure needs to be followed otherwise you could introduce an error that will interfere in the generic gr-satellites functionality.
Looking at this observation, I have changed the SatNOGS db transmitter entry.
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 2k4 FSK AX100 ASM+Golay downlink))
pdu length = 207 bytes
pdu vector contents =
0000: 42 ec 49 03 10 00 00 00 2a 01 01 66 bc ac a8 41
0010: 70 00 00 41 d1 4c 80 43 53 89 d9 c2 e5 2d f3 42
0020: f5 6f 98 01 43 b0 bb bc 42 9c df ec 43 bc 19 9a
0030: 01 3e f8 f4 1d 40 d3 4f 9a 3f 29 4b 52 00 00 00
0040: 00 00 00 00 00 00 00 00 00 01 c1 73 d4 67 41 97
0050: 58 02 40 e5 00 c6 00 00 00 00 01 00 20 00 81 3e
0060: 1b 85 8a 3d e3 8a ad 3d de ed 6e be 34 a0 1a 3c
0070: 4b f9 1b 01 06 06 03 03 01 01 66 bc ad d4 41 08
0080: 00 00 41 cd 28 5c 42 29 3b 14 43 70 89 da c3 7a
0090: 5b e6 01 43 41 e4 b1 43 d8 3f 81 c2 53 33 32 01
00a0: bb e0 95 ef 40 c6 3c a2 be be 47 bd 00 00 00 00
00b0: 00 00 00 00 00 00 00 00 01 c0 be 4c 3c 40 82 91
00c0: 66 41 04 d1 38 1b 9b a3 3b 2b bc 8f c2 da a4
************************************
name: THEA
norad: 43796
data:
&tlm Unknown telemetry:
unknown
transmitters:
1k2 FSK AX100 ASM+Golay downlink:
frequency: 400.595e+6
modulation: FSK
baudrate: 1200
framing: AX100 ASM+Golay
data:
- *tlm
2k4 FSK AX100 ASM+Golay downlink:
frequency: 400.595e+6
modulation: FSK
baudrate: 2400
framing: AX100 ASM+Golay
data:
- *tlm
4k8 FSK AX100 ASM+Golay downlink:
frequency: 400.595e+6
modulation: FSK
baudrate: 4800
framing: AX100 ASM+Golay
data:
- *tlm
9k6 FSK AX100 ASM+Golay downlink:
frequency: 400.595e+6
modulation: FSK
baudrate: 9600
framing: AX100 ASM+Golay
data:
- *tlm
Looking at this observation, we see almost all baud-rates in one single pass.
gr_satellites THEO.yml --wavfile 10033257.ogg --samp_rate 48e3
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 2k4 FSK AX100 ASM+Golay downlink))
pdu length = 207 bytes
pdu vector contents =
0000: 42 ad 89 03 10 00 00 00 04 cc 55 3e 83 12 6f 00
0010: 00 00 00 66 bc 06 b8 20 aa 2b 2f 24 b6 3e 1c 00
0020: 91 00 71 00 49 00 a3 00 00 00 01 01 88 00 a3 00
0030: 61 01 4c 00 99 00 bc 00 bb ff 97 f8 cb ff 9a 00
0040: 0c 00 00 00 00 00 00 66 bc 06 b7 27 4f a1 14 3e
0050: 83 12 6f 00 00 00 00 66 bc 07 30 1e dc 2c 2b 24
0060: 03 3e 58 00 50 00 61 00 49 00 a6 00 00 00 01 01
0070: 8b 00 ce 01 8a 01 f2 00 a6 00 c0 00 be ff 9a fd
0080: 78 ff 97 00 0c 00 00 00 00 00 00 66 bc 07 2f 27
0090: 51 75 d4 3e 83 12 6f 00 00 00 00 66 bc 07 a8 1f
00a0: 2b 22 0c 22 1e 3e 8d 00 62 00 63 00 49 00 a3 00
00b0: 00 00 01 01 32 01 73 02 96 02 70 00 a6 00 c3 00
00c0: c1 ff 04 db 9d 05 b7 6d 95 b6 ac 8e 23 50 8f
************************************
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 4k8 FSK AX100 ASM+Golay downlink))
pdu length = 71 bytes
pdu vector contents =
0000: 42 a8 89 02 09 00 00 48 45 41 4c 5f 31 2e 42 49
0010: 4e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 f2 04 7c
0040: 6f 90 a4 e9 d3 b6 be
************************************
There is also a 9k6 signal but that has not enough SNR
Yes, like BRIO its sister, I am told that the baud rate can change based on the quality of the connection with its earth station.
So, some detail, the transmitter type is gomspace aX100 and the framing is AX.25 for both BRIO and THEA.
GOMspace AX100 is correct, but the framing is not AX.25.
Thank you. Very interesting about the framing. I was told specifically that it was AX.25. I expect to hear more about the twins design later this eveing.
I should get 9k6 data if the elevation increases. Looking forwad to it.
Thank you.