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

Satellites & Observations Launches
61

4 posts were split to a new topic: Legality of ISM from space

62

An update on TLE sets (letters on OBJECTS names doesn’t follow the first line letters on spacetrack, I’m going to use letters from line 1(tle1) and not from the names (tle0)):

  • MEZNSAT : Identified as OBJECT D (46489)
  • YARILO-1 : one of OBJECT E-G (46490-46492), selected OBJECT E (46490) to follow in DB (received, 1 object rejected)
  • YARILO-2 : one of OBJECT F-G (46491-46492), selected OBJECT F (46491) to follow in DB (1 object rejected)
  • DEKART : one of OBJECT G-H (46492-46493), selected OBJECT H (46493) to follow in DB
    (5 objects rejected)
  • NORBI : Identified as OBJECT J (46494)
  • SALSAT : identified as OBJECT K (46495)
  • NETSAT 1-4 : one of OBJECT U-X (46504-46507), selected OBJECT U-X (46504-46507) to follow in DB (2 objects rejected, each NETSAT follows different object, still not separated enough but we receive all of them)

Identified satellites has been updated in DB and Network and now have the identified NORAD ID.

3 Likes
63

As a non-programmer, I will almost certainly embarrass myself with this, but here is the result of my first flailing attempt to decode the 250k LoRa from NORBI (even though we don’t know what all the settings are supposed to be) with alterations to the default scripts in gr-lora:

2 Likes
64

A quick update DEKART is now identified as OBJECT H (46493).

The rest, the two YARILOs and the 4 NETSATs are still not clear.

65

NORBI LoRa Update:

I have been able to assemble most of the LoRa settings used on NORBI from various sources including R4UAB (thanks!), which unfortunately indicate that my decoding efforts so far have not been accurate. But now I finally have a known format to shoot for, so will keep trying!

NORBI LoRa settings list: SF=10, BW=250, CR=4/5, parameter LowDataRateOptimize is activated, Explicit Header mode, CRC – on.

The “SYNCWORD” value on NORBI is 0x12

Packet format on successful decode:

8E – frame length in bytes

FF FF FF FF – broadcast address

0A 06 01 C9 – source address

0A F1 00 00 00 00 – block of specific information

F1 0F – header signature

00 00 D2 0B EE 9F 02 00 – block of specific information

42 52 4B 20 4D 57 20 56 45 52 3A 30 32 5F 31 32 – ASCII string “BRK MW VER:02_12”
3 Likes
66

Norby - First decodes using sx1278 LoRa chip. Norby Telemetry - 9Sept20 0516Z. FN41iq 13E pass. My first LoRa decodes. sx1278 hardware. Big thanks @scott23192](https://twitter.com/scott23192)
K4KDR, abd Norby team! Collaboration with Scott on many telemetry projects including LoRa. Thanks also to jrgromes](https://twitter.com/hashtag/jrgromes?src=hashtag_click) for RadioLib and @FossaSys(https://twitter.com/FossaSys) for GS code templates.
see https://twitter.com/n6rfm/status/1314441456950669314?s=20 and https://twitter.com/scott23192/status/1314440966661693442?s=20

image

2 Likes
67
  • YARILO-1 : Identified as OBJECT E (46490)
  • YARILO-2 : Identified as OBJECT F (46491)
  • NETSAT 1-4 : still one of OBJECT U-X (46504-46507), not separated enough to identify each one of them.
68

NETSAT 1 hasn’t been demodulated, so probably stopped transmitting, since 2020-10-20. However with combining results of observations back then and more recent ones, we managed to identify all of NETSAT satellites:

NETSAT 1: Identified as OBJECT W (46506) based on https://network.satnogs.org/observations/3011550/ and https://network.satnogs.org/observations/3011610/
NETSAT 2: Identified as OBJECT X (46507) based on https://network.satnogs.org/observations/3035746/, https://network.satnogs.org/observations/3035754/ and https://network.satnogs.org/observations/3035772/
NETSAT 3: Identified as OBJECT V (46505) based on https://network.satnogs.org/observations/3035787/
NETSAT 4: Identified as OBJECT U (46504) based on https://network.satnogs.org/observations/3035874/

2 Likes
69

NetSat update:

OBC Beacon format Documentation is now publicly available here, ( via ).

As this information is now public, I will share the ksy-file for NetSat ASAP.

3 Likes
70

I see that 868, 915, & 399 MHz downlink transmitters were added to LACUNASAT-3 last month.

I was under the impression that LACUNASAT-3 was only listening for UPLINK IoT LoRaWAN packets and did not transmit on those bands.

Is there any information to indicate that LACUNASAT-3 is transmitting?

Thanks!

-Scott, K4KDR