New TLE set for DEWASAT-2 generated based on observations 7420343, 7420344 and 7420348.
DEWASAT-2
1 99186U 23106.40000000 .00000000 00000-0 00000-0 0 02
2 99186 97.4174 2.0052 0008664 133.7476 349.5957 15.21067846 03
1 Like
New TLE set for Connecta T2.1 generated based on observations 7417944, 7417945 and 7417946.
Connecta T2.1
1 99195U 23106.40000000 .00000000 00000-0 00000-0 0 02
2 99195 97.4076 2.2638 0013002 106.2765 23.8123 15.22604790 07
New TLE for SSS-2B generated based on observations 7420846, 7420854, 7420860, 7420861 and 7420865.
SSS-2B
1 99190U 23106.40000000 .00000000 00000-0 00000-0 0 07
2 99190 97.4202 1.5883 0009416 108.0335 16.3066 15.20912138 03
Given the long interval the TLE may not describe very well the orbit of this satellite.
@fredy our nominal transmission interval is 20s in maximum power mode, decreasing in intervals of 20s down to as long as 10 minutes between the beacons if the satellite is in a critical power state. Note that our sister satellite Pleiades - Sapling Giganteum on the same frequency beacons once every minute, unchanging unless the satellite is put in deep sleep. The bandwidth should be 125 kHz, per our IARU coordination, but we do not have good data on how the LoRa modulation will appear on a waterfall at this range.
We got good AoS and around 35 modulated packets from the TinyGS network over Europe and Hawaii during the first 50 minutes after deployment, but have not heard back from the satellite since. Initial telemetry did not indicate any issues with regard to the power situation, received signal strength, or component failure, so we think we have probably suffered some kind of SEU or a thermal shock related failure. Continuing to monitor and hoping to get AoS again soon!
5 Likes
Hello! I am from the Sapling team. We have a new TLE:
SAPLING
1 00000U 00000AAA 23107.59813617 .00000000 00000-0 11787-2 0 02
2 00000 97.4760 3.4376 0029551 148.8917 66.2545 15.23004631 01
Most of our work has been with the TinyGS ground station network, but I will be more active on here.
Our LoRa parameters are 437.4 MHz, SF7, CR8, BW 125KHz, with Low Data Rate Optimize turned on. Telemetry is in a custom binary format, you can use these python scripts to decode: Sapling Giganteum Telemetry Decoder · GitHub
We’re still working out some issues with the GPS, it is only fixing intermittently because of the high rotation rate of the satellite. We are going to attempt to detumble it this week which should hopefully improve reliability of the GPS fix.
Flynn
KN6HCC
4 Likes
how are you generating these? is this satellite capable of ranging?
It appears that the 401.100 MHz downlink from DEWASAT-2 is 2k4 w/ the ‘Light-1’ framing used previously by BlueWalker-3 & Light-1.
https://twitter.com/scott23192/status/1648213668964728832
4 Likes
Hi @KN6HCC and welcome!
I’ve updated the TLE of Sapling in SatNOGS DB. Please keep us updated as currently we can not properly track it due to the LoRa restrictions and the wide bandwidth (we don’t have a gnuradio flowgraph to cover LoRa’s width).
We use rffit software from strf tools suite with data extracted from the observations’ waterfalls. It is still a manual process but slowly we move to automate it.
1 Like
Thank you for the details, I’ve updated the DEWASAT-2 transmitter details in DB.
New TLE sets from each satellite team for SAPLING and Sateliot-0, changed to use the temporary NORAD ID we use in SatNOGS DB:
SAPLING
1 99236U 00000AAA 23107.59813617 .00000000 00000-0 11787-2 0 01
2 99236 97.4760 3.4376 0029551 148.8917 66.2545 15.23004631 00
Sateliot-0
1 99180U 23106.83792407 .00015915 00000+0 71754-3 0 0009
2 99180 97.4113 2.6603 0008099 247.1100 112.9281 15.21083187 00080
1 Like
@depegasus do you know if there is any chance to increase the interval of transmissions of RoseyCubesat-1?
It will help a lot on TLE generation and on identification process to have more frequent signals received.
2 Likes
Awesome! No worries about lack of decoding. Is there any chance the SatNOGS community would be willing to help take some Doppler measurements of Sapling? Is there a formal request process?
Flynn
KN6HCC
we do not have good data on how the LoRa modulation will appear on a waterfall at this range
Good day! Despite horrible noise on my RF spectrum today, here is an SDR waterfall view of Sapling’s 125k LoRa from the 1450utc pass this morning.
A LoRa packet that you see AT ALL is a strong signal; often they decode on a LoRa receiver below SNRs that you can even see on a waterfall. (Obviously today’s noise [blacked-out] did not help, but is a lesson learned in that I still got -3- clean decodes!)
1 Like
Hi, there is no formal process. We just try to identify all satellites and receive as much as possible. For that some members of this community sometimes make updates to TLEs using doppler measurements. This process is quite time consuming and that is a major limitation.
The amateur community likes to use open standards, and Lora just doesn’t fit in, because it is patented. That said, I don’t like to think in limitations and more in challenges.
@pe2bz and I have once chatted about doppler measurements on Lora. And we came up with using the Tinygs received data. It includes a timestamp and a frequency error. We think we can transform this into a file that rffit uses, and use this data to identify the satellite or update the TLE. However we have never done this. And I don’t know if the tinygs data is accurate enough. Are the time stamps based on a NTP server? How accurate is the frequency measured?
I personally don’t have any Tinygs experience, so I don’t know how to get the data.
4 Likes
New TLE sets generated:
ION SCV-010
1 99179U 23107.50000000 .00000000 00000-0 00000-0 0 06
2 99179 97.4118 3.2965 0009176 281.1468 106.5519 15.21723946 02
Connecta T2.1
1 99195U 23107.50000000 .00000000 00000-0 00000-0 0 04
2 99195 97.4076 3.6503 0012988 102.8170 292.9486 15.22835557 05
BRO-9
1 99185U 23107.50000000 .00000000 00000-0 00000-0 0 03
2 99185 97.4083 3.3581 0000243 212.9110 171.6916 15.20841525 04
SSS-2B
1 99190U 23107.50000000 .00000000 00000-0 00000-0 0 09
2 99190 97.4202 3.6304 0009369 102.8867 280.6850 15.21287885 05
RoseyCubesat-1
1 99201U 23107.50000000 .00000000 00000-0 00000-0 0 02
2 99201 97.4177 3.0130 0017696 247.1240 149.7822 15.22888819 09
- For ION SCV-010 based on observations 7421423, 7420373 and 7430087. ion10.dat (1.8 KB)
- For Connecta T2.1 based on observations 7429640, 7429639 and 7429605. ct21_2.dat (1.2 KB)
- For BRO-9 based on observations 7430107, 7430321 and 7430319. bro9_2.dat (1.7 KB)
- For SSS-2B based on observations 7430404, 7430395 and 7420861. sss2b_2.dat (595 Bytes)
- For RoseyCubesat-1 based on observations 7420732, 7420742, 7421267, 7430867, 7430866, 7430836 and 7430808. rosey_2.dat (525 Bytes)
2 Likes
A status update for the last two days:
| Temporary NORAD ID | Satellite | NORAD ID to follow | Other NORAD IDs | Identified | Deployed | Last Update |
|---|---|---|---|---|---|---|
| RECEIVED AND DEMODULATED | ||||||
| 99401 | CIRBE | - | - | NO | YES | New TLE set |
| 99179 | ION SCV-010 | - | - | NO | YES | New TLE set |
| 99195 | CONNECTA T2.1 | - | - | NO | YES | New TLE set |
| 99185 | BRO-9 | - | - | NO | YES | New TLE set |
| 99245 | INSPIRE-SAT 7 | - | - | NO | YES | |
| 99193 | KILICSAT | - | - | NO | YES | New TLE set - Silent since 2023-04-16 23:55:25 |
| 99201 | RoseyCubesat-1 | - | - | NO | YES | New TLE set |
| RECEIVED | ||||||
| 99186 | DEWASAT-2 | - | - | NO | YES | New TLE set |
| 99178 | Vigoride-6 | - | - | NO | YES | |
| 99257 | Tomorrow-R1 | - | - | NO | YES | |
| 99171 | LEMUR-2-ROMEO-N-LEO | - | - | NO | YES | |
| 99190 | SSS-2B | - | - | NO | YES | New TLE set |
| 99236 | SAPLING | - | - | NO | YES | Received by 3rd party |
| 99184 | PLEIADES YEARLING | - | - | NO | YES | Received by 3rd Party but only for the first 50min |
| NOT RECEIVED | ||||||
| 99283 | TAIFA-1 | - | - | NO | YES | Not received - There are some signals in some observations but probably not TAIFA-1 |
| 99180 | Sateliot-0 | - | - | NO | YES | Not received |
| 99173 | VCUB1 | - | - | NO | UNKNOWN | Waiting deployment from ION SCV-010 |
| 99177 | REVELA | - | - | NO | UNKNOWN | Waiting deployment from Vigoride 6 |
| 99176 | VIREO | - | - | NO | UNKNOWN | |
| 99187 | ROM-2 | - | - | NO | UNKNOWN | Waiting deployment from ION SCV-010 |
| 99182 | MRC-100 | - | - | NO | UNKNOWN | Waiting deployment from ION SCV-010 |
| 99181 | IRIS-C | - | - | NO | UNKNOWN | Waiting deployment from Vigoride 6 |
| 99175 | LLITED A | - | - | NO | UNKNOWN | Waiting deployment from Vigoride 6 |
| 99174 | LLITED B | - | - | NO | UNKNOWN | Waiting deployment from Vigoride 6 |
| 99183 | DISCO-1 | - | - | NO | UNKNOWN | Waiting deployment from Vigoride 6 |
| NOT IN DB | ||||||
| - | GHGSAT-C6 | NO | YES | |||
| - | GHGSAT-C8 | NO | YES | |||
| - | LEMUR-2-ONREFLECTION | NO | YES | |||
| - | GHGSAT-C7 | NO | YES | |||
| - | FACSAT-2 | NO | YES | |||
| - | LEMUR-2-SPACEGUS | NO | YES | |||
| - | NUSAT-36 | NO | YES | |||
| - | NUSAT-37 | NO | YES | |||
| - | NUSAT-38 | NO | YES | |||
| - | UMBRA-06 | NO | YES | |||
| - | HAWK-7B | NO | YES | |||
| - | HAWK-7A | NO | YES | |||
| - | HAWK-7C | NO | YES | |||
| - | NUSAT-39 | NO | YES | |||
| - | IMECE | NO | YES | |||
| - | GHOST-2 | NO | YES | |||
| - | GHOST-1 | NO | YES | |||
| - | NORSAT TD | NO | YES | |||
| - | ORBASTRO-AF-1(Brokkr) | NO | YES | |||
| - | LS3C | NO | YES | |||
| - | ITS ABOUT TIME | NO | YES | |||
| - | EPICHyper-1 | NO | UNKNOWN | Waiting deployment from ION SCV-010 |
3 Likes
Extremely helpful list w/ so many objects deployed at once. Thanks!!
A correction on the LoRa sats…
Sapling (99236) is being heard from on a regular basis by numerous stations (tinygs-webapp)
Pleiades Yearling (i.e., ‘PROVES’, 99184) is unfortunately not being heard from currently (tinygs-webapp)
2 Likes
Fixed on the initial post. Thank you!
3 Likes
KILICSAT has gone silent for now. There are no GMSK or CW signals at all.
2 Likes
KILICSAT satellite has been in a reset loop and appears to be alive.
2 Likes