Small question of workflow for a ground station #319
-
Hi Daniel, I’m currently working on a ground station that should be able to decode incoming telemetry from passing satellites. I have hooked up Gpredict for the antenna control and have a doppler shift correction inside my GNURadio flowgraph. I’m using gr-satellite to try to print out the decoded PDU’s. I’m still a BIG noob in radio frequencies and still am learning each time I’m working on this project 😵💫. I wanted to ask you what should be my general flow to be capable of decoding telemetry. My current setup have a USRP that is multiplied with the doppler to make the frequency shift. After this I have the satellite decoder block. Here is an image to visualise it: The cosine from the signal source is updated each 0.1sec via XMLRPC server! I DO see a beautiful red line coming out from the multiply block but I think that maybe a filter could help to extract it out from all the noise. I don’t see any data coming out from the satellite decoder block. I have tested out gr-satellite with some recordings from the submodule and I’m sure that they are working. I’m pretty sure the problem is coming from all the noise I’m getting from cranking the gain to 76 on the URSP. I’m coming from a computer science background so I’m really more hands on with code than with RF theory. I wanted your thoughts on how could I extract something (I sure I’m missing some stuff), maybe it’s because of sample rate, but at this point I’m really clueless. p.s. thanks for your work, I think I’m praising you at this point. 👍🏻 |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 10 replies
-
Hi. In general lines your decoding scheme looks good. If everything is working correctly you should get decodes with this flowgraph. A suggestion is to tune the USRP away from the frequency of interest and use the Frequency Xlating FIR Filter to downconvert to baseband, filter and downsample the signal of interest. This avoids the DC frequency at the USRP, which can be problematic. Also, it's not necessary to run the satellite decoder at 192ksps, and depending on the USRP model, it might be advantageous to run it a sample rate higher than 192ksps, so decimation between the USRP and satellite decoder is advisable. Besides this, I suggest you add a File Sink block so that you can record the the signal and take a look at it later on to assess signal quality and check for other problems. Looking at recordings with inspectrum can be quite helpful. Something else: you shouldn't use the "print" port of the Message Debug block (which prints out ASCII data), but rather the "print_pdu" port (which prints out a hex dump). Or you could use instead the Hexdump Sink from gr-satellites, which is just a wrapper around the print_pdu port of Message Debug. |
Beta Was this translation helpful? Give feedback.
-
If you would like some satellites that have particularly strong downlinks, a couple of good ones are: RamSat #48850 ( https://db.satnogs.org/satellite/YJWC-7364-7085-7563-0113#transmitters ) -and- ELFIN-A #43617 ( https://db.satnogs.org/satellite/JSEY-1831-4025-6206-5301#transmitters ) |
Beta Was this translation helpful? Give feedback.
Hi. In general lines your decoding scheme looks good. If everything is working correctly you should get decodes with this flowgraph.
A suggestion is to tune the USRP away from the frequency of interest and use the Frequency Xlating FIR Filter to downconvert to baseband, filter and downsample the signal of interest. This avoids the DC frequency at the USRP, which can be problematic. Also, it's not necessary to run the satellite decoder at 192ksps, and depending on the USRP model, it might be advantageous to run it a sample rate higher than 192ksps, so decimation between the USRP and satellite decoder is advisable.
Besides this, I suggest you add a File Sink block so that you can record the…