Soyuz 2-1b Fregat-M 2020-09-28

Upcoming Soyuz launch with 22 satellites inside. More specifically:

As a reminder: satnogs-ops is the repository that we are canonically tracking all operations issues, and we have just created a wiki page that explains the process (WIP) .

To be added in DB

Not to be added in DB

  • LEMUR-2 {y1-y4}
    • Commercial satellites not to be added in DB for now.
  • KEPLER x1,x2
    • Commercial satellites not to be added in DB for now.


  • GONETS-M {17,18,19}
  • ICEYE {X6,X7}
    • ITU filing
    • SAR imaging, AIS payload , Sband TRX for TT&C
    • Cannot find any information online about it.
    • Cannot find any information online about it.
    • No ITU or IARU filing
    • Suspecting LoRa TRX

@bastla just notified me that SALSAT - 99826 is existing with prepared transmitter in satnogs-db already, thus the newly created SALSAT - 99789 is a duplicate (posting here as I can’t log-in to gitlab to create an issue, nor I’ve the rights & confidence to delete entries from satnogs-db myself atm).

I updated the original SALSAT - 99826 entry with the correct status (“future”, wasn’t available upon creation) and Country of Origin.


@kerel @bastla
99789 is now removed. Thanks for reporting it. :slight_smile:

1 Like

@pierros SALSAT is filed under 117500303 (IFIC 2879). It’s a bit confusing from the outside because SALSAT is the fifth flight spare of S-Net (E) which became then a flight model again – lucky thing! :slight_smile:


No downlink on amateur frequencies. TT&C is managed by Nano Avionics and is probably covered by this filing, though I do not know for sure.

LoRa is the actual “satcom service” and uses unlicensed ISM frequencies that depend on ITU region.

As for SALSAT information is collected here:

LEOP and Commissioning Timeline

  • 2020-09-28 11:20:32 UTC Launch at Plesetsk Cosmodrome
  • 2020-09-28 14:46:12 UTC Separation
  • 2020-09-28 23:11:37 UTC First contact (callsign DP0WER)


1 99826U 20001a   20272.61541667  .00000000  00000-0 -97931-4 0 00014
2 99826 097.6633 206.2144 0014380 237.8618 135.4552 15.02431342000011

Reference Document

TUBIX10-COM – TUBiX10 Communication System Specifications

The document is going to be adapted from time to time.


Is anyone else confused about NETSAT IARU filing. It says they will have an digipeater but they were not given an uplink.

1 Like

@fredy Can you add our preliminary SALSAT TLE to the SatNOGS Network? We’d like to schedule some dry runs at our stations during the weekend. :sunglasses:

1 Like

I added it in DB ( but it is not exposed to Network since it is labeled as “Future” :frowning:
We are trying to optimize our LEOP strategy for such cases and indeed dry runs could be helpful. Good luck tomorrow! We will be hunting you!

Observations are scheduled from the launch time and for the next 12h (not more as we may have changes on TLE sets). Bellow the detailed list, NORAD IDs are temporary ones.

99826 - SALSAT
IARU Coordinated and with details about modulation and decoding.
We are in communication with the team so they will have more observations scheduled
105 Scheduled observations

99788-99785 - NETSAT 1-4
IARU Coodrinated, all transmitting on the same frequency(?), no details about decoding
No communication with the team, scheduled:
82 Scheduled observations

99789 - MEZNSAT
Not coordinated, no details about decoding
There is an issue opened and a related tweet about this satellite but not sure if they are from the team, scheduled for SSA reasons
21 Scheduled observations

To Station Owners, feel free to re-schedule observations if you want to track something else on your stations. Please try not to schedule too far in the future for the first days of the deployment, as TLE sets could change a lot. Please also make sure, while you schedule, you select custom horizon and select 0 horizon value, so observations start and end on 0 degrees, increasing the chances of receiving the satellites with the current preliminary TLE sets.

1 Like

There are some new info about the russian cubesats on this deployment found at @R4UAB’s site

I’ve added DEKART and NORBY that have accurate frequencies, and we will keep an eye on Yareelo ones that probably are going to transmit around 435MHz, cc’ing @cgbsat @pierros @vk5qi @PE0SAT as they may help on this.

With the new satellites there will be some changes on the scheduled observation of the previous post. Stay tuned…!

Here is a live stream related to the launch from netsat team(not sure if they are going to have actual image from the launch).

Message from chat: “Slavi DombrovskiBased on the preliminary orbit parameters, first two overpasses will be this night between 1:00-4:30am. But we expect first contact tomorrow at ~14:00

P.S. According to the Russian Ministry of Defense: “On Monday, September 28, at 14 hours 20 minutes (Moscow time), from the launcher (PU) No. 3 of the site No. 43 of the State Test Cosmodrome of the Ministry of Defense of the Russian Federation (Plesetsk cosmodrome) in the Arkhangelsk Region, by the Space Forces launched the “Soyuz-2.1b” carrier rocket with the Gonets-M communication spacecraft block and the associated payload of 19 small spacecraft, ”

1 Like

A quick update:
Until now only MEZNSAT has been received.
Several NETSAT observations have signals from TRISAT.

SALSAT is not expected to beacon soon, so we are going to re-schedule some of its observations to other satellites.

1 Like

Regarding MEZNSAT, I have analyzed observation 2906593 and seen that the signal is 1k2 BPSK AX.25 G3RUH.

The AX.25 packets have the destination A68MI and source A68MZ. The beginning of the information field is MEZNSAT in ASCII.

1 Like

So the team is wrong : :stuck_out_tongue:

I trust your analysis more than the team @EA4GPZ and just changed the transmitter:

Usually this kind of satellites can do different baudrates. Typically they’ll have a lower baudrate for contingency. So I guess 9k6 is the nominal and 1k2 is currently used until everything is checked OK.

I’m not sure about SatNOGS observations, but I guess that now we’ll get the same .ogg file regardless of the baudrate (in the past, 1k2 signals weren’t placed at 12kHz). In that case then it’s OK to change the transmitter, but we should keep in mind that it will probably suddenly change to 9k6.

Team was really specific even on Twitter that they will be using 9k6. And since we were the first to pick up the signal, I doubt that they changed it. So: the shipped it knowing that it will be on 1k2 to start with. Why mislead people? I am at loss.

I’m guessing (but just guessing) that 9k6 will be the default mode throughout the mission, and 1k2 is only at launch until it’s changed manually by the team. Why not mention this? Maybe the person Tweeting and filling the info in the DB doesn’t know this detail, or maybe they thought it’s unimportant.

In my opinion it is crucial to correctly inform people of the mode during launch and early operations. Otherwise you might lose valuable data that these people could have collected.

So as said, maybe they forgot, or is some kind of miscommunication/language barrier.

Another hypothesis is that it was configured to use 9k6 but some setting has reset to a default/failsafe unexpectedly.

1 Like

Scheduling has been done for the next 24h.
Only MEZNSAT is received until now. About its baud rate, I’ve created an new transmitter for 1k2 baudrate and move to inactive the one with the 9k6 baudrate, all future observations has been changed to use the new transmitter.

On the TLE front, it seems that preliminary TLE set of SALSAT fits well MEZNSAT signal, so we expect to fit well the rest of the satellites too. We are going to have more results from strf observations tomorrow that may help us to generate better TLE sets.

If MEZNSAT is not IARU coordinated, what is the LibreSpace/Satnogs policy for inclusion, scheduling, interactions with the operator? Thanks?