Hi, Patrick (@DL4PD) ,
Sorry for the late response here. To ensure that other amateur operators can monitor Phoenix in orbit, we have also been working on a way to decode packets from our engineering model of our AX100 radio using an SDR and other software based platforms. I have been able to configure gqrx and direwolf to display the incoming packets. The packets appear as just hex at the moment, but Direwolf displays the SRC and DST callsigns from the AX.25 header, so an operator can at least interpret that they are receiving packets from Phoenix with that information.
This is a start for users to decode our packets with a software-based setup, and I am working on taking this the rest of the way, as well as linking our ground software with this, which will not only allow amateur operators to see our packets, but also send basic “ping” commands to the spacecraft if they wish to interact with it. We’ve been moving our ground station to a new location over the past few weeks, though, so i’m not entirely finished with this however. In this regard, I believe I have mainly resolved the issues discussed in my previous post. It just took us a while to find the right software platform.
I have updated our website to include information on Phoenix’s transmitter as well as the decoding methods discussed above. You can see that here: http://phxcubesat.asu.edu/content/amateur-operations
If you have any suggestions to improve this setup, I would be happy to hear your thoughts. In addition, how would you recommend we proceed in combining forces with ESA?
Finally, @fredy does the content on our website provide enough information to get Phoenix registered in the SatNOGS database? If I can be more specific with an of the information provided, I would be happy to explain anything further.