Request to add COSMO to the SatNOGS DB

SatNOGS
1

Hi all,

I am a graduate student working in spaceflight operations at the Laboratory for Atmospheric and Space Physics (LASP) at the University of Colorado, Boulder (CU). I work with the SmallSat Operations (SMOPS) team.

I am reaching out because of the upcoming launch of one of our new CubeSats: COSMO. COSMO (Compact Spaceborne Magnetic Observatory) is a 6U CubeSat that will measure the Earth’s magnetic fields with quantum magnetometers. The mission utilizes Rubidium Optically-Pumped Magnetometers (OPMs) to provide high-quality World Magnetic Field Model (WMM) data at a low cost.

COSMO will be launching alongside AEPEX on Transporter-16 in March. I would like to request that COSMO is added to the SatNOGS db, I have created a SatNOGS issue report with documentation on COSMO’s radios.

I am actively working on a kaitai telemetry decoder and a gr-satellites telemetry decoder. When these are complete and the pull requests have been submitted, I will make sure to reply with their links.

Please let me know if there is anything else I should do to get COSMO added to the SatNOGS DB. Thank you to to everyone who has helped build and maintain this wonderful community.

Adrian

Adrian Bryant
Graduate Command Controller
Mission Operations and Data Systems
Laboratory for Atmospheric and Space Physics
University of Colorado Boulder
1234 Innovation Drive
Boulder, CO 80303

4 Likes
2

If you are curious and would like to see more:

–Adrian

1 Like
3

just signup and create account here

and submit your satellite and transmitter there.

thank you and good luck for your sats!

73!

1 Like
4

Hi Adrian,

I’ve seen that for AEPEX @fredy added it to the database for you.
Please let us know if you prefer that we do that for you again.

If you like to do it on your own, sign up as @bali already stated, visit https://db.satnogs.org/satellites/ after the approval and click …

Suggest New Satellite
Suggest New Satellite1030×416 36.6 KB

This will also add a temporary Norad ID.

As for the transmitters, just add them as transmitter, not as transceiver (as mentioned for UHF).
Otherwise amateur operators like me tend to think the satellite is to play with it.

Do you plan on issuing QSL cards for COSMO, or at least for AEPEX since this will transmit on an amateur frequency?

73
Daniel, dl7ndr

4 Likes
5

Hi all,

Thank you for the prompt responses. I went ahead and suggested it. Please let me know if I have done anything incorrectly.

Daniel, I will ask if we are planning to issue QSL cards for COSMO or AEPEX. I don’t believe we have in the past.

3 Likes
6

For us amateurs, it’s always great to have QSL cards :grin:

Consider this because it’s super exciting to receive a satellite and then receive a QSL card for it :star_struck:

3 Likes
7

And I would add a great way to get more people tracking your satellite :slight_smile:

@abryant thanks for the suggestions I’m going to review them later today or tomorrow.

3 Likes
8

Hi @fredy ,

Have you had a chance to take a look at the suggestions?
I should note that since I don’t have an official launch date, I just went with the info here: https://nextspaceflight.com/launches/details/7609/

9

I’m sorry for the delay but there were some other priorities I had to manage. My estimation is that by the end of the week I’ll be able to have checked all the recent suggestions.

1 Like
10

Hi all,

I am looking to investigate some COSMO decoding issues and I am worried that I ran into some faulty documentation when putting together the radios. A SatNOGS user identified that perhaps the UHF encoding is FSK and not GMSK.

When I run the packet bits from SatNOGS observations through a local decoder, everything decodes 100% as expected. However, when I query the db for COSMO packets to place in the dashboard, I only see CCSDS headers.

Has anyone seen a similar issue before? Is it worth trying to change the transmitter type to FSK?

EDIT: It was a decoder doc issue