Thought for sure that I had located ION SCV Joyful Julia running a full 5-minutes ahead of the TLE estimate (which could account for why it had not yet been identified). Unfortunately, after some due-diligence checking, it was more likely ION SCV-008. But, since there doesn’t seem to be any ASCII or other ways to positively identify these ION’s, I’ll keep an eye on these passes just to be sure.
2 Likes
Hello from the Apolink team!
Here is our latest TLE, looking for some great passes!
IPoS-TDsM
1 88207U 26189.68418630 +.00003127 +00000+0 +32317-3 0 00102
2 88207 97.7535 90.1158 0004277 112.5583 247.6088 14.90835023000204
Thanks!
-The Apolink team
2 Likes
Thank you @apocruz!
Here is the same TLE change to use the temporary NORAD ID we use in DB:
IPoS-TDsM
1 98287U 26189.68418630 +.00003127 +00000+0 +32317-3 0 00101
2 98287 97.7535 90.1158 0004277 112.5583 247.6088 14.90835023000203
@apocruz also a quick question, did you have any signals received after 2026-07-07 10:10 UTC?
It looks like that this time was our last successful reception in Network.
We have not seen anything since
1 Like
Can we use this new TLE for satNog contacts instead of celestraks?
Yes the TLE in Network are updated automatically every two hours or when I trigger it manually.
I’ve just done it manually. Note that some of the station don’t support updating, so their observations will be left with the old ones.
By the way there is published the analyst catalog list in space-track.org, in the next hours we are going to perform some checking and update the satellite’s orbital data, here, in DB and in Network.
From @somecheese analysis, for Marina we are going to choose the object 88254 for now, so the TLE based on the space-track.org analyst catalog, changed to tempoary NORAD ID is:
Marina
1 98293U 26189.68319950 +.00000788 +00000+0 +83374-4 0 00068
2 98293 97.7522 90.1147 0008584 140.9661 219.2178 14.91937258000200
2 Likes
Bellow are the results running ikhnos on space-track.org analyst catalog for the IARU coordinated satellites:
| Satellite | Selected to follow | Other Possible | Status |
|---|---|---|---|
| KOSTKA | 88272 | 88239, 88269, 88270, 88273 | Received |
| Marina | 88254 | 88209, 88217, 88219, 88220, 88221, 88223, 88225, 88229, 88238, 88253, 88255, 88256, 88257 | Received |
| MARMOTSat | 88247 | 88205, 88247 | Received |
| Maveric | - | - | Not Received |
The TLE changes with the temporary NORAD ID we use in SatNOGS DB:
KOSTKA
1 98395U 26189.54864743 +.00001149 +00000+0 +11745-3 0 00076
2 98395 97.7529 89.9838 0010828 138.2063 221.9985 14.92447803000189
Marina
1 98293U 26189.68319950 +.00000788 +00000+0 +83374-4 0 00068
2 98293 97.7522 90.1147 0008584 140.9661 219.2178 14.91937258000200
MARMOTSat
1 98272U 26189.48286524 +.00000924 +00000+0 +99583-4 0 00097
2 98272 97.7576 89.9167 0003670 117.7869 242.3722 14.90786378000179
5 Likes
Bellow are the results running ikhnos on space-track.org analyst catalog for the IARU non-coordinated satellites:
| Satellite | Selected to follow | Other Possible | Status | Notes |
|---|---|---|---|---|
| Unknown 1 T17 | 88214 | 88213, 88215, 88234, 88236, 88237 | Received | - |
| Unknown 2 T17 | 88237 | 88208, 88213, 88214, 88215, 88234, 88236, 88237, 88240, 88241, 88244, | Received | - |
| KOYO | 88207 | 88244, 88246 | Received | - |
| SCION-X | 88236 | 88205, 88208, 88207, 88237, 88240, 88241, 88244, 88245, 88246, 88247, 88248 | Received | Need more good observations for better fitting, still very faint signals |
| TOM-1 | 88245 | 88205, 88247, 88248 | Received | - |
| TOM-2 | 88247 | 88205, 88245, 88248 | Received | - |
| TOM-3 | 88248 | 88205, 88245, 88247 | Received | - |
| CloudCT-Precursor | 88234 | 88207, 88208, 88213, 88214, 88215, 88236, 88237, 88240, 88241, 88244, 88246, 88247 | Received | - |
| CUBY-[1-5] | 88237 | 88208, 88213, 88214, 88215, 88234, 88236, 88237, 88240, 88241, 88244 | Probably Received | Assuming that transmit all of them at 435.6 MHz - Check the note below |
| SUCHAI-4 | - | - | Not Received | - |
The TLE changes with the temporary NORAD ID we use in SatNOGS DB:
CloudCT-Precursor
1 98278U 26189.48265201 +.00000495 +00000+0 +55598-4 0 00082
2 98278 97.7544 89.9171 0005921 117.0782 243.1042 14.91065724000173
TOM-1
1 98264U 26190.01994981 +.00000207 +00000+0 +26705-4 0 00081
2 98264 97.7557 90.4442 0003482 111.9994 248.1595 14.90676802000259
TOM-2
1 98263U 26189.48286524 +.00000924 +00000+0 +99583-4 0 00097
2 98263 97.7576 89.9167 0003670 117.7869 242.3722 14.90786378000179
TOM-3
1 98262U 26189.95277547 +.00000921 +00000+0 +99388-4 0 00071
2 98262 97.7579 90.3790 0004346 104.8302 255.3397 14.90723441000241
Unknown 1 T17
1 98259U 26189.48271230 +.00006670 +00000+0 +67968-3 0 00073
2 98259 97.7477 89.9186 0006335 110.8744 249.3153 14.90998556000170
Unknown 2 T17
1 98257U 26189.68406321 +.00001195 +00000+0 +12656-3 0 00086
2 98257 97.7594 90.1162 0004746 120.5690 239.5998 14.90969590000206
Cuby-5
1 98280U 26189.68406321 +.00001195 +00000+0 +12656-3 0 00082
2 98280 97.7594 90.1162 0004746 120.5690 239.5998 14.90969590000202
Cuby-4
1 98281U 26189.68406321 +.00001195 +00000+0 +12656-3 0 00083
2 98281 97.7594 90.1162 0004746 120.5690 239.5998 14.90969590000203
Cuby-3
1 98282U 26189.68406321 +.00001195 +00000+0 +12656-3 0 00084
2 98282 97.7594 90.1162 0004746 120.5690 239.5998 14.90969590000204
Cuby-2
1 98283U 26189.68406321 +.00001195 +00000+0 +12656-3 0 00085
2 98283 97.7594 90.1162 0004746 120.5690 239.5998 14.90969590000205
Cuby-1
1 98284U 26189.68406321 +.00001195 +00000+0 +12656-3 0 00086
2 98284 97.7594 90.1162 0004746 120.5690 239.5998 14.90969590000206
KOYO
1 98273U 26189.68418630 +.00003127 +00000+0 +32317-3 0 00106
2 98273 97.7535 90.1158 0004277 112.5583 247.6088 14.90835023000208
SCION-X
1 98266U 26189.61694142 +.00000738 +00000+0 +80302-4 0 00085
2 98266 97.7513 90.0491 0005447 112.3371 247.8425 14.90978810000195
Note:
Searching online I found in Exolaunch - 404
Balkan-3 Cuby-1, Cuby-2, Cuby-3, Cuby-4, and Cuby-5 for EnduroSat (Bulgaria)
This could mean that the Unknown satellites could be one or more Cuby or Balkan-3.
3 Likes
Can you give us more information about the modulation and baudrate of the UHF transmission?
1 Like
@fredy do you know if this new TLE is being used now. I still see all contacts as ‘TLE fetched from Celestrak (supplemental)’
I appreciate the help!
Hello from the MAVERIC Team!
We have not received confirmation at our Ground Station in Los Angeles, however we are within the band of the 88xxx series satellites all grouped together.
Our Designator from NORAD was 98271.
We checked other observations at SatNogs, and this one may actually be it: https://network.satnogs.org/observations/14474540/
Our reasoning, yesterday (7/8) we tracked the pack and transmitted a command to change our beacon interval from every 3 min(set at launch) to every 1 min. This observation tends to show possible 20kz bandwidth at 1 min intervals. As of today it stayed at 1 min, tonite (7/9 evening PST CA) we plan to send a command to modify beacon to 2 min intervals and see if we can correlate again with other passes if it changed.
We are tracking the entire range of the 88xxx sats as we assume we are within them, most likely in the back 1/3rd of the pack.
Appreciate the community and support everyone provides to each other! First satellite all student built here, so they are obviously anxious to get a first downlink!
Cheers, Dave
4 Likes
Well, that changes my plan for the 85° elevation pass over the U.S. East Coast tonight. Will be listening & best of luck with your satellite!
I saw here: Satellite | UVic Propagation Lab that the transmitter info for uhf is Uncoded 2-FSK with PN9 whitening, 10.17 kbps rate, 6.18 kHz deviation (25K0F1DBN). Although I’m not completely sure this is right.
1 Like
Unfortunately, nothing heard from Maveric on a high pass over the U.S. East Coast 10-July around 0425 UTC. Will keep trying!
1 Like
On a better note, Navigator is live on S-Band!
I wasn’t tracking it, but the dish still managed to pull in enough signal to know it was there. On a future pass I’ll use the latest TLE and narrow my bandwidth to hopefully get a better look at it. It’s too much to hope that it might be something we can decode, but time will tell.
2 Likes
Thank you Dave for your information.
Additionally, here are more information on the used transmission format and a ready to use GNU Radio beacon decoder.
Daniel
2 Likes
Indeed for some reason the TLE wasn’t updated in DB, I’m checking what’s going wrong.
Nice catch! I’ve changed the entry in DB and updated future observations in Network.
If we are talking about the yellowish horizontal segments from -29KHz to 29KHz, unfortunately this is local noise. If I miss something give me more details on what second or time of the observation you see it.