TLE update for KOYO satellite, is not fully accurate as it is difficult to find the center of the wide signals, but it is definitely better than the current we use:
KOYO
1 98273U 26156AC 26189.35902256 .00000000 00000-0 30421-3 0 03
2 98273 97.7451 88.7121 0007318 148.7649 267.2944 14.90957425 09
sites.txt (13.5 KB)
koyo_189_v1.dat (1.8 KB)
Status for the the IARU non-coordinated satellites (except the german ones):
| Satellite | Reception |
|---|---|
| KOYO | received |
| SCION-X | received |
| SUCHAI-4 | not-received |
SCION-X signals are very faint. Also the current TLE used is good for now.
SUCHAI-4 hasn’t been received, we are going to use the current TLE for now, may be we are going to change it using as reference TLE from another satellite in a couple of days. Note here that the transmitter is unconfirmed, so the satellite may not transmit at this frequency or frequency band.
One more update for Marina TLE
MARINA
1 98293U 26189.35741442 .00000000 00000-0 32990-3 0 06
2 98293 97.7424 77.8186 0013355 90.3955 318.0767 14.32178368 06
# 20260708.35-20260708.36, 19 measurements, 0.497 kHz rms
After checking with ikhnos tool, unfortunately this is not very accurate. So, here is my attempt that seems to fit the recent Network observations:
MARINA
1 98293U 26189.42381585 .00000000 00000-0 29864-3 0 08
2 98293 97.7424 89.9613 0013355 90.3955 317.5196 14.91631018 06
marina_189_v1.dat (1.4 KB)
sites.txt (13.7 KB)
We have an updated TLE from the Satellite Team for RAFS satellite:
RAFS
1 98268U 26188.34207133 .00873878 00000-0 89030-1 0 00006
2 98268 097.7389 088.7722 0007032 114.2946 247.2158 14.90755938000012
Best of luck for the mission. Can’t wait to receive the HF signals.
We have Radio JOVE antenna array at the campus that hopefully can receive the beacon/downlink. It’s a very interesting mission 
For now the TLE for the IARU non-coordinated german satellites look good, so we keep them as they are. As the Unknown 1 T17 satellite is probably one of them, I’ll keep present it here too and I’ll note that also the TLE set used is pretty accurate.
| Satellite | Reception |
|---|---|
| Unknown 1 T17 | received |
| TOM-[1-3] | received |
| CUBY-[1-5] | received |
| CLOUDCT-PRECURSOR | received |
It is not clear as we don’t have clear decodings, but it seems that we have received if not all at least some of them.
What we have managed to decode, it is CloudCT-Precursor with callsign DP2CTP and we have in its observations 3 other satellites DP2TOA, DP2TOB and DP2TOC. These belong respectively to TOM-1, TOM-2 and TOM-3 according to Rufzeichen (thanks @dl7ndr for linking it previously).
So, with the above, it looks like that all the TOM satellites transmit at least at 435.600 MHz with the same modulation with CloudCT-Precursor and they are the wide ones.
Thus we remain with the narrow long transmissions which expected to be one or more CUBY satellites. As we haven’t decode these narrow signals we are not say for sure more.
Another note is that these narrow signals seem to be transmitted around 435.595 MHz instead 435.600 MHz, so I’m going for now to change this in DB. Another change is the modulation and baudrate of TOM satellites.
cc @db2os that’s probably is interested in this analysis
EDIT:
PS There isn’t any signal received at the other expected frequency at 437.800 MHz
Received and decoded CloudCT-Precursor, the signals are FSK 9k6 G3RUH AX.25
name: CLOUDICT-PRECURSOR
norad: 98278
data:
&tlm AX.25 Telemetry:
telemetry: ax25
transmitters:
9k6 FSK AX.25 downlink:
frequency: 435.600e+6
modulation: FSK
baudrate: 9600
deviation: 2400
framing: AX.25 G3RUH
data:
- *tlm
-> Packet from 9k6 FSK AX.25 downlink
Container:
header = Container:
addresses = ListContainer:
Container:
callsign = u'DO0ZFT' (total 6)
ssid = Container:
ch = False
ssid = 0
extension = False
Container:
callsign = u'DP2CTP' (total 6)
ssid = Container:
ch = False
ssid = 0
extension = True
control = 0x03
pid = 0xF0
info = b'J\\0\x00g\x9a\x0bRK\x1e\x01\x08\x03\x01e\x02dF\xc2\xbb\xfb\xb0\x9f\x01\x02Hi`K\xec\xcd\xb5\xc9' (total 33)
Jan | PE0SAT
Okay thanks I’m not to familiar with satellite commissioning so thanks for telling me
Thanks Jan.
Good signals here as well.
73,
Bob N6RFM
Discussing with @PE0SAT in the satnogs chat, I’ve realized the narrow signal is the default music transmission from endurosat comms. Thus probably don’t belong to CUBY satellites, a similar one at 435.5470 MHz for the “Unknown 1 T17”.
So, probably we are looking for the 5 CUBY sats and to find out which one are the satellites with endurosat transmissions at 435.595 MHz and 435.5470 MHz.
Examining https://network.satnogs.org/observations/14461227/
There are more signals present then what we thought, and I also see multiple AX.25 ID’s
DP2CTP, DP2TOA
-> Packet from 9k6 FSK AX.25 downlink
Container:
header = Container:
addresses = ListContainer:
Container:
callsign = u'DO0ZFT' (total 6)
ssid = Container:
ch = False
ssid = 0
extension = False
Container:
callsign = u'DP2CTP' (total 6)
ssid = Container:
ch = False
ssid = 0
extension = True
control = 0x03
pid = 0xF0
info = b'J\\0\x00g\x9am\x95T\x1e\x03\x1e\x01\x08\x03\x01e\x02\x87\xa3=15A\x9f\x01\x02OKT\x8d\x9b\x84\x06\x03' (total 35)
-> Packet from 9k6 FSK AX.25 downlink
Container:
header = Container:
addresses = ListContainer:
Container:
callsign = u'DO0ZFT' (total 6)
ssid = Container:
ch = False
ssid = 0
extension = False
Container:
callsign = u'DP2TOA' (total 6)
ssid = Container:
ch = False
ssid = 0
extension = True
control = 0x03
pid = 0xF0
info = b'D,0\x00%\x82v\x95\x0f\x01\x01\x00\x0e\xb0\x1f\x00\x05\xaf\xa5f\xad5A\x9f\x01\x00\xf0\x00\x00gm\x01\x00\x12@\x14\xfa\xff\xff\x00d\xffdL\x10\x95\xfe\x17\xfah\x10\xff\xff\xfd\xff\x01\x01\n\x16\x10\x00\x08\x80\xba\xf6\x19\x03\x03\x01\xc6h\x1f?]\xce:\xad\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xc0\x12\x86\xea8#\xca\xbf\x80rs\xec\xf4\xbe\xc7\xbf`)\x1a*\x1b\xdd\xe1?\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x00\x00\x00\x00\x00\x00\x00\x1cl1\x14\xb1m' (total 196)
It seem we have four satellites.
name: CLOUDCT
alternative_names:
- DP2CTP
norad: 98278
data:
&tlm AX.25 Telemetry:
telemetry: ax25
transmitters:
9k6 FSK AX.25 downlink:
frequency: 435.600e+6
modulation: FSK
baudrate: 9600
deviation: 2400
framing: AX.25 G3RUH
data:
- *tlm
name: TOM-1
alternative_names:
- DP2TOA
norad: 98264
data:
&tlm AX.25 Telemetry:
telemetry: ax25
transmitters:
9k6 FSK AX.25 downlink:
frequency: 435.600e+6
modulation: FSK
baudrate: 9600
deviation: 2400
framing: AX.25 G3RUH
data:
- *tlm
name: TOM-2
alternative_names:
- DP2TOB
norad: 98263
data:
&tlm AX.25 Telemetry:
telemetry: ax25
transmitters:
9k6 FSK AX.25 downlink:
frequency: 435.600e+6
modulation: FSK
baudrate: 9600
deviation: 2400
framing: AX.25 G3RUH
data:
- *tlm
name: TOM-3
alternative_names:
- DP2TOC
norad: 98262
data:
&tlm AX.25 Telemetry:
telemetry: ax25
transmitters:
9k6 FSK AX.25 downlink:
frequency: 435.600e+6
modulation: FSK
baudrate: 9600
deviation: 2400
framing: AX.25 G3RUH
data:
- *tlm
Jan | PE0SAT
We can confirm that KOSTKA is communicating in both directions. We have just successfully executed our first commands.
Hey guys, does anyone have spare bandwidth to generate a Doppler-fitted TLE for Replicator-2 ? We’d love to refine our tracking.
I’m on it in the next hour.
Here you are, TLE update for Replicator-2:
Replicator-2
1 98267U 26156AP 26189.75656971 .00000000 00000-0 29972-3 0 09
2 98267 97.7563 90.1589 0009250 148.8823 246.5050 14.92234045 09
repl2_189_v1.dat (945 Bytes)
sites.txt (13.7 KB)
It seems also there is a drift in the transmitted frequency, something between 0 and 4k8, thus I’m going to add a drift at 2k4.
Great work by everybody working on decode parameters, TLEs, and everything else around this deployment.
I certainly don’t mind copy/pasting as improvements are made to individual TLEs when we have these mass deployments… but out of curiosity, is there a list anywhere that’s updated & could be re-downloaded once or twice per day? If not, no problem - just wanted to ask.
Thanks!
Here is a status list of all the satellites we track and some notes. For the ones that we haven’t created TLE set, for now we are ok with the current.
| Satellite | Reception | Notes |
|---|---|---|
| Received | ||
| KOSTKA | received | - |
| MARINA | received | Transmits only in UHF now |
| MARMOTSat | received | Transmits only over mission’s groundstation |
| KOYO | received | |
| SCION-X | received | faint signal |
| Unknown 1 T17 | received | - |
| Unknown 2 T17 | received | - |
| TOM-[1-3] | received | wide signal GFSK9k6 |
| ANDURIL-216(LA3) | received | |
| IPoS-TDsM | received | no reception the last hours |
| RAFS | received | |
| Replicator-2 | received | |
| Kita-36 | received | |
| Kita-53 | received | |
| FOSSASAT-2E26 | received | by tinygs |
| Navigator | received | only one observation we need more to fully verify |
| Not-Received | ||
| Maverick | not-received | - |
| SUCHAI-4 | not-received | unconfirmed transmitter |
| Oasis Alpha | not-received | |
| Centauri-9 | not-received | unconfirmed transmitter |
| BRO-31 | not-received | |
| ION SCV Joyful Julia | not-received | |
| Sentinel-1 (Osiris-A) | not-received | |
| CyberCUBE | not-received | few observations we need more to be sure |
| CUBY-[1-5] | not-received | not sure if we track the right frequency in the expected wide range from ITU Entry |
One more update, I’ve created the Unknown 2 T17 satellite in DB to track the endurosat signal at 435.595 MHz.
Here is a TLE for it, copied from Unknown 1 T17:
Unknown 2 T17
1 98257U 26156AC 26188.48555653 .00000000 00000-0 30030-3 0 09
2 98257 97.7451 90.1526 0007318 148.7649 262.2128 14.89467368 06
You can always get the latest TLE directly from DB at https://db.satnogs.org/api/tle/?format=3le
If you need specific satellites you can filter with the sat_id parameter using comma separator of the satellite IDs (comma “,” becomes %2C in the request), for example for T17 launch satellites:
PS The TLE I post usually are updated 1-2 minutes after the post, for the other ones they are updated when I have “liked” the post.
PS 2 Hopefully in the future there will be a way for users/teams update the orbital data directly in DB without my intervention.
Hello from the Apolink team!
Here is our current TLE, we’re trying to confirm our TLE so many passes would be awesome!
Here:
1 88207U 26189.48283291 +.00003883 +00000+0 +39990-3 0 00083
2 88207 97.7531 89.9169 0004185 112.3807 247.7855 14.90833510000171
Thanks,
The Apolink Team!