Hey @fredy, thanks for the TLEs! We calculated our own TLE which is only around 3.5 minutes off from the one you posted. Also, very exciting to see all of the observations scheduled! Thank you for putting those into the system.
1 99402U 14900A 22183.32385405 .00000000 00000-0 00000-0 0 07
2 99402 45.0002 117.5373 0003742 251.3388 076.7673 15.23306609 326
Watching the observations roll in – looks like we caught CSIM (who is still beaconing at our same frequency) on SatNOGS Network - Observation 6161893 since there was a moment when they overlapped in the sky:
Decoding this observation gives BCT as dst call sign
-> Packet from 9k6 FSK downlink
Container:
ax25_header = Container:
dest = Container:
callsign = u'BCT' (total 3)
ssid = Container:
ch = False
ssid = 0
extension = False
src = Container:
callsign = b'\x86\xa6\x92\x9a@@' (total 6)
ssid = Container:
ch = True
ssid = 0
extension = True
control = 0x03
pid = 0xF0
primary_header = Container:
ccsds_version = 0
packet_type = 0
secondary_header_flag = True
AP_ID = 63
sequence_flags = 1
packet_sequence_count_or_name = 446
data_length = 249
secondary_header = Container:
sh_coarse = 570360064
sh_fine = 1024
packet = None
Updated to the new TLE set and re-scheduled some of the observations. The new TLE set fit the signals on several observations at the bottom left corner. In other observations that there is signal at center or the top right is another satellite, usually CSIM.
To be fair you are beaconing at CSIM’s frequency. You don’t follow your IARU coordinated frequency which is 437.325MHz but you transmit at 437.250MHz. Is there a reason behind that? Is IARU informed about this change on the coordinated frequency?
Fair correction! I talk about our frequency on this other thread – Unfortunately the radio we intended to use (transmission at 437.325 MHz) does not function with the power system of our cubesat – we ended up having to use a flight spare that transmits at 437.25 MHz. the radio that we have (Spacequest TRX-U) is delivered with a frequency set. There is a command available enabling a force-feed of the transceiver registers (enabling a frequency change), but there are a few issues with changing our frequency now:
This gives me no joy, especially when we are already out of alignment with the amateur community with our AX.25 header issues. We have someone working on contacting the IARU to have a discussion with them, but that aspect of the mission is out of my hands, personally.
Thanks for the update to the TLE @fredy! We are getting a good amount of data! See, for example, SatNOGS Network - Observation 6164045 (nice, @PE0SAT )
The dashboard is up: Grafana (thanks to @DL4PD for the help)
@afyhrie Congratulations! You have a working satellite flying in space!!
I have received 3 passes using STRF. The signal is strong and easy to measure. For instance:
As you can see 52946 is not a good fit. Here are the measurements on the 3 observations:
I have mesured the top row of the signal, and therefore there is a 5kHz offset shown. If I identify the first observation only, I get 52945 as best fit. For the second and third only I get 52944 as best fit. And when I identify them all 3 at once, I get:
rms limit (kHz): 0.1
99402 0.032 kHz 437.254768 MHz
52944 0.038 kHz 437.254817 MHz
52945 0.081 kHz 437.254951 MHz
Identified 3 candidate(s), best fitting satellite is 99402.
There are only 3 TLEs released at this moment, and there are 7 satellites deployed. It can of course be that the CTIM TLE is not yet published. For now I think we are good with the current TLE (99402) and when it starts to deviate, we can try 52944, or just look again 
With new TBA TLE sets from spacetrack, it seems that CTIM fits 52950, however 52951 is very close. DB and Network will follow 52950 for now.
0 TBA - TO BE ASSIGNED
1 52944U 22074A 22184.24783370 -.00000285 00000-0 00000+0 0 9995
2 52944 44.9948 112.5299 0004100 267.1992 92.8454 15.23194571 149
0 TBA - TO BE ASSIGNED
1 52945U 22074B 22184.24776799 -.00000285 00000-0 00000+0 0 9993
2 52945 44.9934 112.5288 0004003 254.5986 105.4485 15.23304314 141
0 TBA - TO BE ASSIGNED
1 52946U 22074C 22184.24107927 -.00000350 00000-0 00000+0 0 9998
2 52946 44.9932 112.4722 0047016 213.8327 145.9565 15.34441694 132
0 TBA - TO BE ASSIGNED
1 52947U 22074D 22184.24718994 -.00000286 00000-0 00000+0 0 9999
2 52947 44.9849 112.5309 0003995 227.7064 130.7503 15.23777983 148
0 TBA - TO BE ASSIGNED
1 52948U 22074E 22184.24747988 -.00000289 00000-0 00000+0 0 9998
2 52948 44.9829 112.5283 0005315 207.3220 154.3321 15.24259404 148
0 TBA - TO BE ASSIGNED
1 52949U 22074F 22184.24769468 -.00000286 00000-0 00000+0 0 9993
2 52949 44.9904 112.5265 0004828 245.5048 114.5265 15.23425782 141
0 TBA - TO BE ASSIGNED
1 52950U 22074G 22184.24771417 -.00000286 00000-0 00000+0 0 9992
2 52950 45.0007 112.5210 0003993 250.7386 109.2998 15.23392529 140
0 TBA - TO BE ASSIGNED
1 52951U 22074H 22184.05093393 -.00000285 00000-0 00000+0 0 9991
2 52951 44.9843 113.5986 0004271 236.9598 122.7172 15.23372667 111
Hey folks! Thanks for the TLE updates and all of the awesome data going into the dashboard (side note – if there’s other data you’re interested in seeing on the dashboard let me know and I’ll get it on there!).
We successfully made contact with CTIM last night from our ground station and got our first sets of commands up! The spacecraft looks to be behaving nominally, which is very exciting.
CTIM is now identified as OBJECT G(52950), here is ikhnos results on observation observation 6183819.
Also bellow are results of strf analysis by @satcolintel5 posted in #satnogs matrix channel:
rms limit (kHz): 0.5
52949 0.405 kHz 437.246091 MHz
52950 0.038 kHz 437.245582 MHz
52951 0.278 kHz 437.245220 MHz
Identified 3 candidate(s), best fitting satellite is 52950.
Thank you @fredy and @satcolintel5 for that TLE information and calculation!
We have been using 52950 for our ground station operations and have been having good success so far. On the dashboard you can see the temperatures increase when we turned the payload and payload heaters on:
And where we told the spacecraft to leave sun point and enter fine reference point:
