I was able to decode this pass with using the Direwolf tool, I was able to receive data at a baud rate of 9600. I’m not sure how this affects the definition of this satellite, but I will slowely start working on other waveforms to see if I can get an output.
I would post the commands I used and the data decoded in this post, but I’m not sure of the correct format to insert a snippet of terminal output. Would anyone be able to give me a hint on how to do this properly without violating any forum rules?
It surely depends how much output you want to paste. If it is just a few frames: use three backtics ` to start a code block and add another three to end it. In between paste the CLI output.
I was able to demodulate the signal by following the instructions in the Decode and Telem wiki with small changes to the cli commands. ($arg is the filename)
sox $arg -esigned-integer -b 16 -r 48000 file.raw
direwolf -B 9600 -b 16 -n 1 -r 48000 -q hd -t 0 -q h -q d -d p -d t -a 0 - < file.raw > "output_$arg.txt"
Here are the 3 beacons I was able to demodulate using direwolf from Observation 1459855. I left out the initial output from direwolf and the unformatted output.
I think this may be due to the current baud rate of RADSAT-G being assumed 19.2 kbaud. I think if the ground station decoders were trying to decode at a 9.6kbaud rate, they might have more luck. I ran the same process on another pass and I was able to decode from the perceived beacons in the water fall in that one. If I decode more data should I create a post for each of the passes that I decode? while posting in a format similar to this post?
It is more the fact that it still has a temporary norad Id assigned. This means that no one reported a working satellite in the days after launch. This is usually done by visually inspecting the spectrum and running some tools. There is also an estimation on the whole modulation scheme done to catch wrong informations spread about that. All of this didn’t happen for RADSAT-G, what is really curious…
I’ve already suggested a new transmitter with the correct baudrate in DB.
Sorry for the delay on this. I’ve just approved the 9k6 transmitter. @skylart indeed after checking also myself a couple of observations from different location, it seems that this is RADSAT-G.
From the deployment there were two objects that weren’t identified. One of them was MEMSAT and the other one RADSAT-G.
Recently (November 2019)@lameres from the team of RADSAT-G suggested to use TLE for 43553 as they have spotted something by following this object. Until then we used TLE for 43554 for RADSAT-G, this is probably why we didn’t catch anything.
@lameres can you please confirm that the frames above come from RADSAT-G?
My only objections are:
The source callsign is not “WJ2XFH” but “K7MSU” which is the callsign of the station of Montana State University.
That the baudrate is not 19200 as expected but 9600.
PS in the next week we have the RADSAT-U deployment, it is also stated in its IARU application that will use 19200 as baudrate but with the above I’m not sure if that’s right. @lameres any confirmation on that too would be very useful!
PS2 This means that MEMSAT is object 43554, I guess we should schedule a couple more observations and if we are lucky we may receive it.