If the current mode is 1200 baud FSK, then that is correct.
However, I think the FSK demod flowgraph is expecting G3RUH scrambling? If this signal is being decoded using the soundmodem ‘AFSK’ setting (e.g. 1200 baud AFSK, NRZI, etc…) then it likely doesn’t have scrambling.
Hi
Confirm that the data is decoded with UZ7HO soundmodem, exactly as you described.
It is very hard to decode indeed. Fast doppler changes at high attitude passes are terrible, even if the signal is clearly heard, trying to decoding is a nightmare sometimes.
On the other hand, since very first orbits we were able to uplink to the satellite succesfully from our GS. The uplink is at the same frequency (doppler corrected).
From Monday we are in trouble to uplink any command. We do not know why at this moment. Nothing changed at our GS position.
We are speculating if the problem is the satellite antenna pointing off towards the Earth or, the receiver is going deaf…
So, we appreciate very much any TLM data decoded with the software decoding published or any other made by the Community and sent to us. The data collected will be useful to understand what it is happening.
@ea5wa Preferred method would be the data decoded by our program. But, a .kss file will be fine too. I am using kissdump.exe from DK3WN to convert in .hex. However, we are more interested to collect TLM from places where the sat is not visible to us (footprint). We are receiving telemetry at our GS, fortunately.
@pierros method sugested will be fine also. I need to learn how to setup a dasboard to collect and centralize whole data here in SatNOGS. I am doing several tasks at work with little time to do one more,
