Thank you Isaac for your detailed reply and link to all necessary information.
Would you like me to do a merge request for your .ksy decoder for SatNOGS?
Daniel
I believe this is the launch livestream:
2 Likes
super!
name: CPSAT
alternative_names:
- CPSAT1
norad: 98194
data:
&tlm Telemetry:
telemetry: ax25
transmitters:
9k6 BPSK downlink:
frequency: 437.265e+6
modulation: BPSK
baudrate: 9600
framing: AX.25 G3RUH
data:
- *tlm
gr_satellites CPSAT.yml --wavfile CPSAT_audio_48k.wav --hexdump
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 9k6 BPSK downlink))
pdu length = 184 bytes
pdu vector contents =
0000: 86 a0 a6 82 a8 62 e0 86 a0 a6 82 a8 62 61 03 f0
0010: 09 03 c0 0b 00 a1 57 f7 32 8a 84 bd 00 00 00 00
0020: 01 01 01 00 00 fe 00 00 ff 0c cf 00 00 00 00 80
0030: 00 07 ff ff ff ff ff ff ff ff ff ff ff ff 00 00
0040: 00 00 00 00 0a 01 02 03 04 05 06 07 08 09 0a 00
0050: 00 00 00 00 00 00 00 02 6d 03 21 00 ff ff ff ff
0060: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0070: ff ff ff ff 01 00 00 00 00 00 00 00 00 00 00 00
0080: 00 00 80 05 00 00 00 00 00 00 ff 7f 00 00 00 00
0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00a0: 3b 0b 00 00 ff ff ff 00 00 01 00 00 00 01 00 1f
00b0: 00 00 00 00 00 00 ff ff
************************************
1 Like
name: GBSAT
norad: 98243
data:
&tlm Telemetry:
telemetry: ax25
transmitters:
9k6 GFSK:
frequency: 435.95
modulation: FSK
baudrate: 9600
framing: AX.25 G3RUH
data:
- *tlm
GBSAT
1 98243U 26280.14583333 .00000000 00000-0 50000-4 0 06
2 98243 97.7500 370.4500 0001433 0.0000 145.1000 14.89340176 00
https://forum.nasaspaceflight.com/index.php?topic=65471.0
Naro, Korea:
Latitude: 34.4316,
Longitude:127.5344
launch = 2026-10-07T03:25:00 UTC
not sure if correct, based on previous launch
inclination = 97.75
SSO = ~600km
direction: south
name: GBSAT
norad: 98243
5 menit
faketle -n 370.45 -m 145.1 -q 599 -Q 601 -I 97.75 -t 2026-10-07T03:25:00 -d 300 -i 98243U > fake-gbsat.txt && satorbit -c fake-gbsat.txt -q -t 2026-10-07T03:30:00 -B 34.4316 -L 127.5344
5 Likes
update with latest valid information from @isaac44
faketle -n 370.54 -m 145.1 -q 569 -Q 571 -I 97.6704 -t 2026-10-07T03:25:00 -d 300 -i 98243U > fake-gbsat.txt && satorbit -c fake-gbsat.txt -q -t 2026-10-07T03:30:00 -B 34.4316 -L 127.5344
GBSAT
1 98243U 26280.14583333 .00000000 00000-0 50000-4 0 06
2 98243 97.6704 370.5400 0001439 0.0000 145.1000 14.98996526 07
2 Likes
I am much appreciated for your active support. Can you also add fake TLE for SLEDGE before launch? I’d like to user SATNOGS for initial beacon signal if possible.
Once we have orbital element from the launcher, we’ll post out estimated TLE calculated from orbital element.
2 Likes
This is my take on TLE using all the info I can find online and in this thread, TLE for launch time 2026-10-07T03:25Z:
GBSAT
1 98243U 26280.14444444 .00000000 00000-0 50000-4 0 05
2 98243 97.6704 10.0320 0003597 0.0000 145.0950 14.98187870 08
SLEDGE
1 98241U 26280.14444444 .00000000 00000-0 50000-4 0 03
2 98241 97.6704 10.0320 0003597 0.0000 145.0950 14.98187870 06
UEL-Y-SYS
1 98198U 26280.14444444 .00000000 00000-0 50000-4 0 04
2 98198 97.6704 10.0320 0003597 0.0000 145.0950 14.98187870 07
BEE-1012
1 98197U 26280.14444444 .00000000 00000-0 50000-4 0 03
2 98197 97.6704 10.0320 0003597 0.0000 145.0950 14.98187870 06
SD-1_SAT
1 98196U 26280.14444444 .00000000 00000-0 50000-4 0 02
2 98196 97.6704 10.0320 0003597 0.0000 145.0950 14.98187870 05
DAEJEONSAT-1
1 98195U 26280.14444444 .00000000 00000-0 50000-4 0 01
2 98195 97.6704 10.0320 0003597 0.0000 145.0950 14.98187870 04
CPSAT
1 98194U 26280.14444444 .00000000 00000-0 50000-4 0 00
2 98194 97.6704 10.0320 0003597 0.0000 145.0950 14.98187870 03
PS either using @bali’s ones or mine it should not make any big difference as both are very close for a pre-launch TLE estimation.
4 Likes
Sats are being deployed, so I’m setup for SLEDGE, GBSAT, & CPSAT when they pass over the Eastern U.S. here in a bit.
1 Like
SLEDGE
1 99999U 26280.15383156 .00000000 00000-0 22504-3 0 9991
2 99999 97.6615 16.3360 0011381 84.5637 100.4418 14.97738215 02
This initial TLE generated from separation vector. This shall be used until spacetrack have updated TLE.
1 Like
Ok, nothing from SLEDGE, unfortunately, but GBSAT & CPSat appear to be up & running. I will replay to see about some decodes.
Observed signals were 2 to 3 minutes LATER than the preliminary TLE indicated. Plan accordingly until we see the TLEs recalculated.
4 Likes
This initial TLE generated from separation vector that can be used meanwhile.
CPSAT
1 98194U 26280.15371675 .00000000 00000-0 50000-4 0 06
2 98194 97.6560 16.3340 0021245 100.2531 84.1477 14.95702602 06
1 Like
Changed to use the temporary NORAD ID in DB
SLEDGE
1 98241U 26280.15383156 .00000000 00000-0 22504-3 0 9990
2 98241 97.6615 16.3360 0011381 84.5637 100.4418 14.97738215 01
1 Like
Based on UEL-Y-Sys observation here is the TLE:
UEL-Y-Sys
1 98198U 26280.14444444 .00000000 00000-0 50000-4 0 04
2 98198 97.6704 19.7088 0003597 0.0000 134.9051 14.98187870 03
And here is the same TLE used for the rest of the satellites:
GBSAT
1 98243U 26280.14444444 .00000000 00000-0 50000-4 0 05
2 98243 97.6704 19.7088 0003597 0.0000 134.9051 14.98187870 04
BEE-1012
1 98197U 26280.14444444 .00000000 00000-0 50000-4 0 03
2 98197 97.6704 19.7088 0003597 0.0000 134.9051 14.98187870 02
SD-1_SAT
1 98196U 26280.14444444 .00000000 00000-0 50000-4 0 02
2 98196 97.6704 19.7088 0003597 0.0000 134.9051 14.98187870 01
DAEJEONSAT-1
1 98195U 26280.14444444 .00000000 00000-0 50000-4 0 01
2 98195 97.6704 19.7088 0003597 0.0000 134.9051 14.98187870 00
Not perfect TLE but it follows much better the satellites than the initial.
As the TLE is changed kind of a lot, I’m going to re-schedule some of the future observations.
1 Like
Sorry - while both GBSAT & CPSat appeared to have some packets that should have been strong enough to decode, it’s really tough on replay to be precise enough when such a large sample rate was used (to see both signals in the same waterfall).
So, if they haven’t already, someone else will get to enjoy the first decodes from those sats. But it sure was nice to see what certainly appeared to be downlink packets from both of them. At least for now, I can’t confirm that it actually was packets from those specific sats.
@onbspace unfortunately in observation like this the signal is one of the NANOFF A or NANOFF B satellites. You can see one of their observations here.
I believe this is a good pair of GBSAT decodes:
1 Like
For GBSAT we have some first decodes in https://network.satnogs.org/observations/15142966/.
EDIT:
You got me 
1 Like
So for now we have seen signals from:
GBSAT
CPSat
UEL-Y-Sys and/or BEE-1012 and/or SD-1_SAT
and a big maybe from SLEDGE
About UEL-Y-Sys, BEE-1012 and SD-1_SAT we will need some sample demodulated frames to compare with the ones we have in Network’s observations in order to make clear who is/are the one/ones we received.
2 Likes
This looks the first signal observation of SLEDGE, we’re working on decoding now.
For me it looks like matching frequency and modulation with doppler offset potentially from wrong TLE.
FYI, SLEDGE send beacons every 60seconds by default.
1 Like