Soyuz-2-1b Fregat-M (METEOR M N2-2) launch on 2019-07-05


#1

Finally, after the failure of the launch of the Meteor M N2-1 a few years ago, on 6 July 2019 from the spaceport of the Russian Space Agency Roscosmos will take off the Soyuz Rocket with the new Meteor METEOR M N2 satellite on board, which, in theory, should be the project twin of the mythical Meteor M N2 currently in orbit, that is sending fantastic images in LRPT at 137.900 Mhz. If all goes well the satellite after the test phase then in the following months should come into operation.
The frequencies in use should be the following:
AHRPT S-E 1700 MHz 3000 kHz RHCP D 3000 kbps
AHRPT S-E 1705 MHz 3000 kHz RHCP D 3000 kbps
LRPT S-E 137.1 MHz 150 kHz RHCP D 80 kbps
LRPT S-E 137.9 MHz 150 kHz RHCP D 80 kbps
LRPT S-E 137.9125 MHz 150 kHz RHCP D 80 kbps
therefore there should be no problems with the reception and decoding of images with the usual methods provided.I remember that the software package I created and configured for real-time reception of images still works perfectly and therefore is also good for the new satellite. On the internet (youtube) there are video tutorials on the subject.The software package can be downloaded from my website http://www.caturegli.it and the tutorials on youtube (search for iz5rzr meteor m2)I hope we could soon publish the photos received by this new Satellite.
Thanks again Roscosmos for the fun.
IZ5RZR


#2

Hello evererybody,

Also we are looking forward to this launch, because our next CubeSat actually ist on that rocket. It would be great, if this awesome community could help us with finding and comissioning our satellite again!

Current Launch date: July 5, 08:41 Moscow Time
(see: http://www.russianspaceweb.com/2019.html)

Could someone add it the database?
Downlink Specs:

Name: MOVE-IIb
Downlink: 145.840 MHz (alternating CW and BPSK12k5)

More Info (given frequencies are not updated yet for MOVE-IIb but protocol will be the same): https://www.move2space.de/MOVE-II/satellite/radio-amateurs/

We would also be very happy to receive some SatNOGS raw recordings to tune our decoders and decode initial in-orbit data. Please just let me know, if you would like to contribute!

Best regards,
Martin


#3

And before someone asks about it. Here is it’s co-ordination http://www.amsatuk.me.uk/iaru/finished_detail.php?serialnum=645

:slight_smile:


#4

Hello everybody,
Technische Universität Berlin will launch BEESAT-9 on this rocket as well. We would also be very glad to get some help from the community especially during the early orbit phase.

Therefore, I kindly ask to add BEESAT-9 (IARU Coordination) to the database:

Telemetry Downlink: 435.950 MHz, FM, GMSK 4k8
Beacon: 435.950 MHz, Morse telegraphy via FM subcarrier (F2A)

TLE:

BEESAT-9
1 99990U 19001a   19186.42129861  .00000000  00000-0  00000-0 0    19
2 99990 097.5444 148.1364 0018488 174.4536 124.7361 15.14664823    12

The beacon is the callsign DP0BEM in morse code every 40 seconds starting from around 10:37:30 UTC on July 5, 2019.
Telemetry Downlink will be activated during passes over the ground station in Berlin.

Telemetry structure and conversion formulas are published under https://www.raumfahrttechnik.tu-berlin.de/menue/amateur_radio/

Our GNU Radio Block, gr-satellites or Soundmodem can be used to demodulate telemetry rawdata.

Thank you very much in advance!

Best regards
Sascha


#5

Thanks to all for the details we’ll try to add them as soon as possible in DB, at least 24h before the launch.

Thanks @kappi for the initial TLE, we are going to use this for scheduling, if there is any update on them please let as know to re-organize the scheduling properly.


#6

I leave here this link for JAISAT-1


#7

A short update for all Radio Amateurs out there:

The launch is still scheduled for tommorow, Friday 05:41 UTC.
A couple of live streams should cover the launch:

Similar to BEESAT, we expect MOVE-II to be operational from about 10:40 UTC. According to the TLE first signals can be received across the USA and Canada. The satellite will send a short pilot or callsign every 20s and a data beacon every minute. (compare https://network.satnogs.org/observations/717121/).

As said, we would be happy to receive any recordings. You may either upload those files directly at https://www.move2space.de/MOVE-II/satellite/radio-submission-leaderboard/ or contact me here via PN - and of course we’ll send nice QSL cards to all contributors :slight_smile:

@fredy Will the SatNOGS entries be ready for tomorrow?


#8

Thanks for the update!!!

I’m finishing some work and I’m going to work on the entries for this launch! I’ll let you know here when I have everything ready :slight_smile:


#9

I have started working on it… I didn’t expect so many satellites need to be added… it will take some time… sorry for that :slight_smile:

But worry not, will be ready for the launch :slight_smile:


#10

Satellites with their transmitters have been added with temporary NORAD IDs, please confirm that data are correct!

99800 Meteor M 2-2
99801 Move-IIbIARU Coordination
99802 BEESAT-9IARU Coordination
99803 BEESAT-10IARU Coordination
99804 BEESAT-11IARU Coordination
99805 BEESAT-12IARU Coordination
99806 BEESAT-13IARU Coordination
99807 JAISAT-1IARU Coordination
99808 SEAM 2.0IARU Coordination
99809 SONATEIARU Coordination
99810 Lucky-7IARU Coordination
99811 MTCube (ROBUSTA 1C)IARU Coordination
99812 TTU101IARU Coordination

Most of them are in UHF, so I’ll try to schedule them sharing the observation time as fair as I can, with priority to those that have requested here for our help. Also I’ll prioritize those that have complete info (encoding information and coordination complete).

Three Notes:

  1. I’m not going to add TLE for METEOR as there is no reason for observations before it get functional. I’ll wait also for a NORAD ID to be assigned, which will be soon after the launch
  2. BEESAT 10-13 are going to use the same frequency with BEESAT 9 according to their site. As I’m not 100% sure if they are going to transmit on this frequency, I’ll pass to schedule them for the next couple of hours after launch. However will be visible in BEESAT 9 observations if they transmit.
  3. There is possibility of 6 More satellites to transmit in radio amateur frequencies. Two ( EXOCONNECT, LightSat) are from german orbital systems which has transmitted in the past on radio amateur frequencies with D-STAR satellites. The other other three ( VDNH-80 or VDNKH-80, Sokrat and AmGU 1 or AmurSat) are russian cubesats and one ( UTE-Ecuador) from UTE (https://www.ute.edu.ec/) of ecuador that in the past has used amateur radio frequencies.

#11

Move-IIb seen to have a crossband repeater on it based on their request. Yet the IARU did not provide a freq for its UHF uplink. (Seems odd)

MTCube seems odd that it in the finished area when it was no co-ordinated a freq nor was it denied.

Lucky-7 seems pretty neat with its blue LEDs.

SONATE has Data and SSTV which is pretty cool.

Also fredy why do BEESAT-10 thru 13 link to the TTU101 sats coordination? This is there coordination url http://www.amsatuk.me.uk/iaru/formal_detail.php?serialnum=684


#12

If I understand correctly this is the command and control uplink. Not sure if this should be coordinated by IARU.

fixed!


#13

Thanks for all your contributions!

The entry of MOVE-IIb looks perfect. If we could make a request, we’d especially love to schedule stations 213 and 644 for the first passes.

Of course we will cover the passes over Munich in the afternoon with our SatNOGS station (355) while we can also do very wide raw baseband recordings with our main not-yet-SatNOGS station. We may provide these recordings upon request - just let me know, if you need it.


#14

Sure… there isn’t any other satellite in VHF so that would be easy :slight_smile:

We may need these if we have issues on decoding in order to improve our scripts… I let you know. :wink:


#15

This is correct. The upload channel does not bring any benefit to others.


#16

So no cross band repeater?


#17

No, not as far as I know. But I’ll cross-check asking the satellite staff tomorrow.

Update: Our team did confirm this information - unfortunately there is no repeater.


#18

Thank you for all the work @fredy!
The BEESAT 9-13 entries look good to me.
Also it is absolutely fine to record observe BEESAT 10-13 together with BEESAT-9.
For now the plan is that they will transmit in the time frame 13:40 - 13:52 UTC today.

Thank you guys for all the help!


#19

I found a small mistake, checking the entry a 2nd time:
The callsign of MOVE-IIb will be DP0MVB (DP0MVE is MOVE-II).


#20

It should be fixed now! :slight_smile: