Regarding Observation 6156701 …
As I think, the datarate is 9600 bps based on bandwidth
1 Like
No, this is 1200 baud, after a replay I get the following output:
-> Packet from 1k2 BPSK downlink
Container:
header = Container:
addresses = ListContainer:
Container:
callsign = u'ASCL' (total 4)
ssid = Container:
ch = True
ssid = 0
extension = False
Container:
callsign = u'RANDEV' (total 6)
ssid = Container:
ch = False
ssid = 0
extension = True
control = 0x03
pid = 0xF0
info = b'\n9\xfc\xca\x17\x05\x14\x05\x14\x00d\x00h\x11\x11\x11\x11\x11\x11\x11\x11\x12\x12\x12\x12\x12\x12\x12\x12\x13\x13\x13\x13\x13\x13\x13\x13\x01\x01\x01\x01\x01\x01\x01\x01\x02\x02\x02\x02\x02\x02\x02\x02\x03\x03\x03\x03\x03\x03\x03\x03\x00\x00\x02`\x003\x03\\\x00\x12\x00\x11\x00\x07\x03W\x00\t\x03\\\x00\x12\x03\x06\x00\x02\x00\x02\x00\x02\x00\x02\x03[\x00\x08\x03\\\x00\x02\x00\x05\x00\x02\x00\x02\x00\x02\x03\x06\x00\x1e\x03\x0b\x01e\x00\xb7\x02\x19\x01\t\x03U\x00\x05\x00\x08\x02\xfc\x00\x02\xf2\xf2\n\x14\x06\xca\x06\x1b\x014\x00I\x02L\x00\x01\tr\ts\x00\x7f\x00E\x06\x1b\x013\x00K\x02I\x00\x01\tq\ts\x08\x98\x00\x00\x00\x01\x01\x01\x00\x00XX\xb0\xb0XX\x00\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x93\x00\x93\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00' (total 230)
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 1k2 BPSK downlink))
pdu length = 246 bytes
pdu vector contents =
0000: 82 a6 86 98 40 40 e0 a4 82 9c 88 8a ac 61 03 f0
0010: 0a 39 fc ca 17 05 14 05 14 00 64 00 68 11 11 11
0020: 11 11 11 11 11 12 12 12 12 12 12 12 12 13 13 13
0030: 13 13 13 13 13 01 01 01 01 01 01 01 01 02 02 02
0040: 02 02 02 02 02 03 03 03 03 03 03 03 03 00 00 02
0050: 60 00 33 03 5c 00 12 00 11 00 07 03 57 00 09 03
0060: 5c 00 12 03 06 00 02 00 02 00 02 00 02 03 5b 00
0070: 08 03 5c 00 02 00 05 00 02 00 02 00 02 03 06 00
0080: 1e 03 0b 01 65 00 b7 02 19 01 09 03 55 00 05 00
0090: 08 02 fc 00 02 f2 f2 0a 14 06 ca 06 1b 01 34 00
00a0: 49 02 4c 00 01 09 72 09 73 00 7f 00 45 06 1b 01
00b0: 33 00 4b 02 49 00 01 09 71 09 73 08 98 00 00 00
00c0: 01 01 01 00 00 58 58 b0 b0 58 58 00 01 00 00 00
00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00e0: 00 00 00 00 00 00 00 93 00 93 00 00 00 00 00 00
00f0: 00 00 00 00 00 00
************************************
2 Likes
Hello,
I am the French guy who visited your Daejeon facility a month ago for the S-band tests for RANDEV.
Thanks a lot for the help.
I can answer your question, we were hesitating and registered both to ITU, but we are only using 1200.
More exactly this is a ISIS TRXVU with BPSK-G3RUH at 1200bps.
@PE0SAT your callsigns are correct.
I am discovering the Satnogs network and I see your kind contribution, thank you.
We have our own software, but I will investigate and try to make a decoder next week. Maybe a dashboard as this is a great initiative.
Right now I am not sure about how the G3RUH scrambler can be added to Satnogs.
Mikaël,
2 Likes
Hey Mikael!
Nice to have you onboard and I am really interested in getting you into the dashboard activities! What I am seeing at a first glimpse is: your AX.25 header is invalid, as one of your callsigns only has 4 characters set! Please read the AX.25 specs carefully or feel free to ask me for clarifications. It would be cool if this is something fixable…
Our SatNOGS infrastructure always tries to demodulate normal and G3RUH scrambled frames simultaneously, so this is not a problem for us!
HTH,
Patrick
2 Likes
Hello,
Thanks for the warm welcome.
Our SatNOGS infrastructure always tries to demodulate normal and G3RUH scrambled frames simultaneously, so this is not a problem for us!
Perfect !
This explains why I couldn’t find any information on this.
your AX.25 header is invalid, as one of your callsigns only has 4 characters set! Please read the AX.25 specs carefully or feel free to ask me for clarifications. It would be cool if this is something fixable…
I will ask the guys in charge of the flight software and satellite control if he can change this.
Otherwise I believe this will be solved w hen I add a new KAITAI frame decoder.
Mikaël
3 Likes
Hi,
Our groundstation guy plugged your raw data on his software, it’s all good. Here is the display:
That’s helping a lot, thank you.
We will make a SatNOGS dashboard ASAP.
By the way, how can we get these raw data? It seems that for RANDEV records we can only download .ogg file.
Mikaël,
1 Like
Hi Mikael,
Welcome, and if you have any questions or something isn’t clear feel free to ask.
I know the ISIS solution can also work at higher baud rates, will you switch to higher rates in the future?
“@PE0SAT your callsigns are correct.” And yes that is my Ham radio call sign
Unfortunately a modification at satnogs-decoders isn’t enough as these only translate binary data into their original bounding, like bits, intgeres and floats and such. If your callsign has only 4 characters a lot of modems won’t work. It needs to be filled to 6 characters with trailing spaces…
It might be as easy as this: just set the callsign to ASCL (ASCL[SPACE][SPACE]).
1 Like
Congratulation!!
I recommend to install gr-satnogs (librespacefoundation / SatNOGS / gr-satnogs · GitLab) with gnuradio.
As I know you already use gnuradio. After installation, I can help you decode the packets.
Dear all,
I managed to decode many beacon signals from the .ogg files using all of your advises and Satnog’s BPSK flowchart.
The main problem was an improper bit synchronization, I added a Costas loop block with a loop bandwidth of 0.1.
Here is the flowchart for record:
So far I managed to decode 45 beacons from 07/01 to 07/08. I am getting the rest of the .ogg, and I will try to see if I can optimize a bit to get more beacons.
It might be as easy as this: just set the callsign to
ASCL(ASCL[SPACE][SPACE]).
I decoded many more beacons using the AX.25 decoder, the callsignTo is ASCL[SPACE][SPACE] as you suggested.
I recommend to install gr-satnogs (librespacefoundation / SatNOGS / gr-satnogs · GitLab ) with gnuradio.
Perfect
@fredy roblem was an improper bit synchronization, I added a Costas loop block with a loop bandwidth of 0.1.
It might be as easy as this: just set the callsign to
ASCL(ASCL[SPACE][SPACE]).
I decoded many more beacons using the AX.25 decoder, the callsignTo is ASCL[SPACE][SPACE] as you suggested.
I recommend to install gr-satnogs (librespacefoundation / SatNOGS / gr-satnogs · GitLab ) with gnuradio.
Yes, I went this route. It took a bit of effort to find an operating system compatible with it. Debian 11 WSL worked flawlessly. Thanks for the advise !
@fredy I would like to contribute back to Satnogs, is there a way to feed the decoded frames back to Satnogs’s database for all existing .ogg files so that we can add a KAITAI decoder and a Dashboard.
Also, can I add a wiki page for BPSK decoding from ogg. files ?
Mikaël
2 Likes