Both TLE sets have been added in DB and Network.
1 Like
Corrected CS
Altair
1 98795U 24318.11639709 .00000000 00000-0 86299-3 0 00002
2 98795 097.3845 182.7983 0016123 210.4026 149.6277 15.23142917001262
2 Likes
ZIMSAT-2 is still there, but with +20 minutes from TLE of 8th.
2024-11-18T20:30:19Z ZIMSAT-2 - National Anthem of Zimbabwe.mp3.remove-suffix-zip.zip (735.4 KB)
2024-11-18 20:33:39 UTC
The AFSK beacons are too distorted to decode.
No signal from RS6S also on 437.050.
2 Likes
These TLE (from R4UAB) are more suitable:
ZIMSAT-2
1 98777U 24310.15937500 .00000000 00000-0 52244-5 0 03
2 98777 97.2925 175.4491 0014470 63.8934 243.9382 15.23217526 09
2 Likes
Added in DB and Network! Thank you for sharing!
EDIT:
I’ve just noticed that the epoch of the TLE is not propagated. I’m going to propagate it and re-add it.
EDIT 2:
Here is the propagated TLE, however it may not be fully accurate with the original:
ZIMSAT-2
1 98777U 24323.92792825 .00000000 00000-0 52244-5 0 01
2 98777 97.2925 188.8243 0014550 10.1045 150.3072 15.23220000 07
3 Likes
Since it has been two weeks since the launch and there are still no official objects, we are increasingly dependent on observations to generate TLEs.
I personally find it very difficult to match signals to satellites that are part of this launch.
Is it possible to get updates from the various teams that make clear which frequency and modulation are currently being used by which satellite. (and make proposals for these changes in the satnogs database https://db.satnogs.org/)
Without this information, it is like looking for a needle in a haystack.
Jan - PE0SAT
5 Likes
Well said Jan. Indeed I am seeing that many of these new sats are multiple minutes behind the TLEs here, or not observed. This is using an omni-directional helix.
In the meantime, perhaps these tle data may help in some cases.
https://r4uab.ru/satonline.txt
73,
Bob
N6RFM
3 Likes
possible they might be updated over at sonik ?
1 Like
TLE Update
RTU MIREA1
1 98894U 24324.84179881 .00000000 00000-0 50000-4 0 01
2 98894 97.4000 190.2146 0017065 222.3573 269.8801 15.22710473 02
TUSUR GO
1 98788U 24324.83545000 .00000000 00000-0 50000-4 0 02
2 98788 97.4000 189.8104 0012126 209.2730 249.3400 15.23901209 02
VIZARD-ion
1 98789U 24324.56170000 .00000000 00000-0 50000-4 0 07
2 98789 97.4000 193.7015 0002766 272.4012 193.8762 15.24799255 03
Horizon
1 98793U 24324.88423611 .00000000 00000-0 50000-4 0 06
2 98793 97.4000 193.0828 0009285 154.0139 288.9899 15.25690018 06
Colibri-S
1 98794U 24324.89193287 .00000000 00000-0 50000-4 0 01
2 98794 97.4000 191.2064 0002174 256.0622 215.2734 15.24966766 05
5 Likes
I try to post any updates here. So all current info we have about satellites and transmitters are same in sonik and in satnogs
8 Likes
Finally able to get several decodes for Horizon. Running almost 15 minutes ahead of the currently available TLE. Fortunately using the omni helix.
Good hunting all.
Bob
N6RFM
6 Likes
Colibri-S and TUSUR GO turned on CW Beacon
https://network.satnogs.org/observations/10614361/
https://network.satnogs.org/observations/10614981/
4 Likes
Hi Bob,
What freq was it operating on ?
Hi Jan,
435.430 MHz
GL es 73,
Bob
Thanks, trying to create better TLE
RS67S CW
2024-11-20 21:02:45 RS67S RS67S vb83 ib0 is0 tbp0 id13 tmp20 tsp0 qs0
2024-11-20 21:05:45 RS67S RS67S vb83 ib0 is0 tbp0 id13 tmp18 tsp0 qs0
2024-11-20 21:08:45 RS67S RS67S vb82 ib0 is0 tbp0 id13 tmp17 tsp0 qs0
RS78S CW
2024-11-20 21:21:00 RS78S RS78S vb83 ib0 is0 tbp0 id13 tmp22 tsp0 qs0
2024-11-20 21:24:00 RS78S RS78S vb83 ib0 is0 tbp0 id13 tmp19 tsp0 qs0
2024-11-20 21:27:00 RS78S RS78S vb83 ib0 is0 tbp0 id13 tmp19 tsp0 qs0
5 Likes
Maybe you can give these a try, they are also added to the SatNOGS network.
HORIZON
1 98793U 24325.90261574 .00000000 00000-0 50000-4 0 08
2 98793 97.4000 190.7177 0006482 135.4731 132.1729 15.24896660 06
3 Likes
Thanks Jan. Will happily do so and report back.
1 Like
from FN41iq, new TLE predicted near overhead pass with AOS at 0211Z. Using omni helix, first decode see at 0147Z.
3 Likes
