Thanks, @bali
. We looked at Observation 12491306 as well.
The 26-byte HEX burst shown in the Data tab
2E 94 58 3C F5 F2 80 48 0E 9D 37 6A B6 F6 E1 2F 04 F2 4E 84 28 5C 0F F6 5D CE
doesn’t match the RSP-03 HK beacon format we’ve defined.
If it were an RSP-03 beacon, the payload would likely begin with the fixed header sequence 00 18 AD 80 ..., as specified in the beacon structure (AX.25 frame > payload).
So far, we haven’t found any data block consistent with that structure in the GMSK frames.
Thanks. Best Regards,
czh00361(estima5633)
Rymansat project
Be aware that the automatic decoding of CW signal in SatNOGS network is subject to decoding error. In this observation with a very very weak signal (if any) like this, the data showed in the data tab are probably noise.
Most of the time apart from getting a very strong CW signal (and the good wpm), the data in the data tab cannot be trusted at all. This is the reason why there are not upload in DB automatically
Thanks for the reminders about CW auto-decode. We fully understand the false-positive risk.
On our side we’re decoding manually with fldigi and plan to use the “RSP-03 CW Beacon Uploader” from @dl7ndr to push vetted frames to Grafana.
At the moment RSP-03 is transmitting in test mode, so only limited housekeeping is obtainable. With a small Yagi the CW/GMSK is only a few dB above the noise, and we’ve been verifying passes by hand in SDR Console. An example spectrogram is here:
We’re gradually learning the spacecraft state and working on countermeasures. We’re not ready to publish technical details yet, but we’re definitely not giving up and would really appreciate any continued community support.
We’ll keep validating carefully and share confirmed decodes as they come. Many thanks for watching for it and for all your advice!
Indeed it is almost invisible… I’ve changed the colour levels and with the red line showing the path of the expected signal maybe it is little easier to see it in the middle between the black lines:
“manual” means -by hand-.
You have to listen in with your own ears or better see the dashes and dots on a spectrogram (not on a waterfall) of a recording.
With the latest observation from Dwingeloo telescope:
we have reception of RSP-03 with 4 frames decoded.
These observations in combination with the 12502206 by 2380 - Piszkesteto UHF which have also received it and analyzed with ikhnos, identifies successfully that RSP-03 is OBJECT XL (65732).
@estima5633 you can find the IQ of the observation (two files one for each polarization) in:
You may be able to decode more frames from that IQ file after processing it.
Please let us know if there are any useful findings!
EDIT:
PS I’m going to update the NORAD ID in DB later today
Thank you so much for the detailed updates and continuous support!
I saw the amazing waterfall plot from EU1SAT — it looks like a very clean signal from RSP-03 around 437.040 MHz, beautifully tracked over KO33ru using WIMO 2x9 el antennas. This gives us valuable insight into the signal stability and Doppler profile. Thank you for this excellent capture!
Also, thank you bali for working on the color adjustment of the waterfall image. If you manage to get good contrast or visibility using GIMP, please let us know your settings — I’d love to learn from your approach.
On our side, we’re continuing the uplink command trials and confirming the antenna deployment status. We’ll share results once we have more data.
Thanks again to everyone for the collaboration and great observations from around the world!
We used the Dwingeloo telescope to observe RSP-03 for four passes today. Each of the observations show good signals in both horizontal and vertical polarization.
Hi @tammojan,
Thank you so much for this great CW decoding and detailed report!
It’s impressive to see such clear signals in both polarizations, and the decoded results have been extremely helpful for our team to understand the current satellite condition.
I’d like to ask — would it be possible to contact you personally (for example, by email) to learn more about how the Dwingeloo team manages these observations?
I’m especially interested in whether it’s feasible for us to coordinate or request Dwingeloo observations occasionally for further verification.
Many thanks again for your amazing support and dedication.
Hi @estima5633, you’re welcome! Unfortunately we’re quite limited by the number of operators for the telescope, so we cannot observe every day. We’re happy to coordinate, so that you can command the satellite to transmit something useful when we are listening. You can reach us at info@camras.nl
Hi,@tammojan
Thank you very much.
I realize that my earlier message saying “it would be great if I could use Dwingeloo” may have sounded too direct — my apologies.
From now on, I’ll make sure to reach out through info@camras.nl when coordination is needed, and only within a scope that doesn’t cause any inconvenience to the Dwingeloo team.
I really appreciate all your kind support and efforts.
Thanks again for your support and for all the help from Dwingeloo!
