Confirming EU1SAT’s observation for CatSat.
2k4 signals only 3 dB over noise at zenith pass at 19:5x utc.
3 Likes
We now have dashboard for CatSat:
https://dashboard.satnogs.org/d/1b1zIkuIz/catsat?orgId=1
From the dashboard, the EPS uptime value, if there wasn’t any reset and if I do right calculations, places the deployment around 2024-07-15 15:45 UTC.
3 Likes
Replayed the SatNogs audio from CatSat observation
https://network.satnogs.org/observations/9877435/
… just to be sure I had all my settings correct and it’s always nice to see some ASCII Text in one of the packets!
5 Likes
There is a new TBA TLE for the launch that fits CatSat orbit:
0 TBA - TO BE ASSIGNED
1 60246U 24125J 24198.68755259 .00037208 00000-0 17068-2 0 9997
2 60246 97.3064 52.5632 0053597 170.9140 276.8737 15.19027249 14
I’ve set it to follow it in Network and DB and when it will be assigned we are going to identify it.
2 Likes
Sounds good, thank you! Quick question - the TLE here has 60246 as the satellite’s number, and the TLE I’m looking at on Celestrak has 60264 as the NORAD catalog number (I’m looking at this page: https://celestrak.org/NORAD/elements/gp.php?INTDES=2024-125&FORMAT=tle). Where was the TLE with the 60246 identification number found?
This might be an error on my end, but I wanted to ask about it just in case!
This TLE set comes from the space-track.org, which is the official interface for the NORAD catalog. As far as I know celestrak uses this catalog to populate its lists. The object 60264 doesn’t exist in space-track’s catalog.
Not sure why celestrak choose to use this NORAD ID. Maybe it has to do with some missing from(not published yet) catalog objects. By the way, the NORAD ID may change during the TBA status, this is why we don’t proceed to identification for now.
1 Like
#60246 has made it into Celestrak & is showing (for now) as a Starlink sat:
OOV-CUBE
1 60240U 24128F 24199.21332627 .00004277 00000+0 39274-3 0 9997
2 60240 61.9976 136.1461 0010183 263.2370 96.7559 14.96321599 1102
2024-128G
1 60241U 24128G 24199.21034847 .00006748 00000+0 60002-3 0 9999
2 60241 61.9943 136.1255 0009949 283.2249 76.7729 14.96941922 1108
2024-128H
1 60242U 24128H 24198.94829338 .00010431 00000+0 94239-3 0 9999
2 60242 61.9849 137.0540 0013311 264.7284 95.2284 14.95873379 1068
ROBUSTA 3A
1 60243U 24128J 24199.21658423 .00009383 00000+0 85351-3 0 9995
2 60243 61.9917 136.1487 0012855 254.8588 105.1077 14.95696328 1107
STARLINK-11214 [DTC]
1 60244U 24129A 24198.53421304 .22208332 12564-4 21394-3 0 9996
2 60244 53.2936 35.7088 0005292 150.3844 302.4407 16.50887656 1508
STARLINK-11202 [DTC]
1 60245U 24129B 24199.26926309 .02053709 11835-4 67668-3 0 9991
2 60245 53.1134 32.3982 0070588 85.8926 85.4390 16.18615777 1615
STARLINK-11212 [DTC]
1 60246U 24129C 24198.68755259 .00037208 00000+0 17068-2 0 9990
2 60246 97.3064 52.5632 0053597 170.9140 276.8737 15.19027249 14
2024-125J
1 60264U 24125J 24198.68755259 .00037208 00000+0 17068-2 0 9996
2 60264 97.3064 52.5632 0053597 170.9140 276.8737 15.19027249 14
1 Like
Here is the current status for this launch after latest updates:
| Temporary NORAD ID | Satellite | NORAD ID to follow | Other NORAD IDs | Identified | Deployed | Last Update |
|---|---|---|---|---|---|---|
| RECEIVED AND DEMODULATED | ||||||
| MESAT-1 | 60209 | - | YES | YES | Identified, here are the ikhnos results | |
| 99164 | CatSat | 60246 | - | NO | YES | Received, Change to follow 60246 |
| NOT RECEIVED | ||||||
| 98884 | TechEdSat-11 (TES-11) | 60205 | All (except identified) | NO | YES | Not Received, randomly assinged to follow 60205, other possible All (except identified) |
| 98888 | KUbeSat1 | 60210 | All (except identified) | NO | YES | Not Received, randomly assinged to follow 60210, other possible All (except identified) |
| 98886 | Serenity | 60206 | All (except identified) | NO | YES | Not Received, randomly assinged to follow 60206, other possible All (except identified) |
| 98887 | SOC-i | 60204 | All (except identified) | NO | YES | Not Received, randomly assinged to follow 60204, other possible All (except identified) |
| 98883 | R5-S4 | 60207 | All (except identified) | NO | YES | Not Received, randomly assinged to follow 60207, other possible All (except identified) |
| 98885 | R5-S2-2.0 | 60208 | All (except identified) | NO | YES | Not Received, randomly assinged to follow 60208, other possible All (except identified) |
2 Likes
Given that 60210 is identified in space-track.org as the rocket body, I’ve changed KUBeSat1 to follow 60203 in DB and Network. This also included re-scheduling some observations.
3 Likes
Hello, I am the PM for KUbeSat-1, we suspect our satellite to be 60203/A. We used an Endurosat transceiver, so without some modified GNU radio blocks you won’t be able to decode the message. If you or anyone receives anything from it, would you be able to save the raw data file? We are listening for it but have not heard anything from it with our ground station.
Thanks!
Zach
2 Likes
Greetings, Zach!
Has the KUbeSat-1 downlink been received at all, by anyone?
Thanks!
1 Like
Unfortunately no reception since the deployment. Feel free to take a second look on KUbeSat-1 observations in SatNOGS Network and let us know if you spot anything.
Also please confirm that the signal we expect is GMSK 9k6 at 437.085 MHz.
1 Like
Here is the current status for this launch after latest updates:
| Temporary NORAD ID | Satellite | NORAD ID to follow | Other NORAD IDs | Identified | Deployed | Last Update |
|---|---|---|---|---|---|---|
| RECEIVED AND DEMODULATED | ||||||
| MESAT-1 | 60209 | - | YES | YES | Identified, here are the ikhnos results | |
| CatSat | 60246 | - | YES | YES | Identified, here are the ikhnos results | |
| NOT RECEIVED | ||||||
| 98884 | TechEdSat-11 (TES-11) | 60205 | All (except identified) | NO | YES | Not Received, randomly assinged to follow 60205, other possible All (except identified) |
| 98888 | KUbeSat1 | 60203 | All (except identified) | NO | YES | Not Received, randomly assinged to follow 60203, other possible All (except identified) |
| 98886 | Serenity | 60206 | All (except identified) | NO | YES | Not Received, randomly assinged to follow 60206, other possible All (except identified) |
| 98887 | SOC-i | 60204 | All (except identified) | NO | YES | Not Received, randomly assinged to follow 60204, other possible All (except identified) |
| 98883 | R5-S4 | 60207 | All (except identified) | NO | YES | Not Received, randomly assinged to follow 60207, other possible All (except identified) |
| 98885 | R5-S2-2.0 | 60208 | All (except identified) | NO | YES | Not Received, randomly assinged to follow 60208, other possible All (except identified) |
PS Note that TLE for CatSat is 3 days old and it doesn’t describe accurately the satellite orbit but still good for tracking. The rest TLE sets are 2 days old and they may also be not fully accurate.
I only know of “good” observations that were tracked by users on SatNOGS, there were a few of those on the 18th of July that I saw.
1 Like
That is the signal that should be recieved
Looking at CATSAT observations we see that the current TLE provided (5 days old) aren’t good enough for decoding the data, therefor we created new ones.
Below the one is currently also active in the SatNOGS network.
CATSAT
1 60246U 24203.28193287 .00000000 00000-0 17068-2 0 06
2 60246 97.3064 56.4483 0053404 154.8811 201.6991 15.19369173 06
We will keep an eye on regular updates via Space-Track or otherwise update them manually.
4 Likes
Hello everyone - I am the former lead of the SOC-i team at UW and I’ve been trying to verify that it is alive on orbit. It should be beaconing at a rate of approximately once per 8 seconds (sometimes more intermittent) at frequency 437.125 MHz with GMSK 4k8 modulation. It is tumbling and its Endurosat UHF II antenna is not deployed, but a sufficiently high-gain tracking antenna should be able to receive it.
I’ve been listening for signs of life using a simple handheld home setup. So far, I believe I have narrowed it down to either 60207/E or 60208/F. This is based on some very faint signals I was able to observe on two separate passes. However due to the limitations of my home setup and the age of the TLEs when I observed it’s hard to be absolutely sure. SOC-i is currently assigned to 60204/B on SatNOGS though which I am reasonably confident is not correct, given that it has not been seen in any SatNOGS tracks and that Nanoracks told us that 60204/B was confirmed to be R5-S4.
Could I ask for some assistance in trying to verify that SOC-i is indeed alive? I’m looking for at least secondary confirmation of the signals that I observed with my handheld setup, and ideally a strong enough SNR that we could actually decode the alive message it’s currently sending out.
Thank you all in advance!
Charlie
4 Likes