Hi @db2os, team members from the 6GSTARLAB mission have informed us in the matrix chat channel that they haven’t transmitted on that frequency and that they still trying to be coordinated and that they use S-band for TC&C.
Also this was verified from strf and other observations, so this is why we have invalidated the transmitter we had in DB at 433.895 MHz and kept the S-band one until we have further updates.
Hi,
We are now using the following TLE for HUNITY. This gives the best reception right now.
HUNITY
1 71930U 25337E 25338.03628408 +.00046311 +00000+0 +23823-2 0 00065
2 71930 97.4329 49.9450 0007792 343.0607 17.0365 15.16256966000802
Done! Here is the TLE with the NORAD ID changed to the one we use in SatNOGS DB:
HUNITY
1 98537U 25337E 25338.03628408 +.00046311 +00000+0 +23823-2 0 00067
2 98537 97.4329 49.9450 0007792 343.0607 17.0365 15.16256966000804
HCT-SAT 2 TLE update:
HCT-SAT2
1 98470U 14900A 25338.02236688 .00000000 00000-0 30029-3 0 08
2 98470 97.4397 50.0338 0001310 66.2475 224.8575 15.16507086 05
Thanks for reporting I’ll take a look when I finish with the rest!
In Network observations we can see only one signal with bandwidth 4k8, can you confirm if this is Otter or Spin-2? It’s difficult to say as both were and probably still are close to each other,
If you are not sure, can you share what interval is expected from your satellite, if they have different we may match the signals to one of the satellites.
Disclaimer I’m not 100% sure that we see only on of them, so we still may see both of them but the blending of the signals or the absence of them in some observations to create the impression that only one transmits.
Hi all,
The previous SpaceTrack TLE for BlackKite-1 didn’t turn out well, so we generated one from the last good observation. Could this be loaded for the upcoming scheduled observations?
BLACK-KITE-1
1 98527U 14900A 25337.45785880 .00000000 00000-0 30000-3 0 09
2 98527 97.4399 49.3876 0000000 287.9240 164.6776 15.17528736 05
Again, thank you all for the support so far in tracking!
Hi all,
We noticed that after this TLE is loaded into SATNOGS, we are not able to schedule more passes. It always reports that the satellite is below the horizon. TLE seems to be okay to us, could you all help to confirm please?
Thank you!
It is due to the 0 vallue on the eccentricity at the second line, sorry I haven’t noticed it earlier. I’ve used the one of the previous TLE you provided, so it should be ok now. So the TLE Is now:
BLACK-KITE-1
1 98527U 14900A 25337.45785880 .00000000 00000-0 30000-3 0 09
2 98527 97.4399 49.3876 0006629 287.9240 164.6776 15.17528736 08
If you use the propagate of strf tools, it may make it 0, so just change it back to the previous value and re-calculate the checksum. Alternatively in the latest rffit you can use the command/key e to move the epoch to the latest observation (make sure it is the first in the .dat file with the points).
Thanks Freddy!
With the new rffit, does it mean we no longer need to do the propagate step? It can now be done from within rffit itself?
Exactly, in some rare cases you may need to go back to the old method. In these cases the algorithm doesn’t fit properly the points on the new-epoch TLE, but usually it will be ok.
Just to be clear, after hitting the e command, you need to fit again the objects as you did before hitting the e command.
TLE Update for BLACK-KITE-1 based on space-track.org analyst object list.
BLACK-KITE-1
1 98527U 25340.01396725 +.00017352 +00000+0 +88676-3 0 00095
2 98527 97.4484 51.8962 0005079 312.6247 47.4557 15.16725296001104
PHI-1 TLE
PHI-1
1 98512U 25340.55443911 .00000000 00000-0 30041-3 0 05
2 98512 97.4399 52.7067 0001303 68.4740 47.7109 15.19171547 00
# 20251206.42-20251206.56, 24 measurements, 0.113 kHz rms
Jan | PE0SAT
Hello,
We have a new TLE for TMICROSAT-1. Could you please help update it in the SatNOGS DB?
TMICROSAT-1
1 98515C 25276Y 25340.00706164 +.00011731 +00000+0 +57726-3 0 00092
2 98515 97.4390 51.8988 0001906 105.5006 254.6439 15.18151952001107
Thank you!
We receive daily updates of our TLE, but via an unpublished directory from Space Track. We keep it public on our website here. @fredy Can you use this link to regularly update the TLE of HUNITY?
@therman89 if you can change that or have another link with the TLE using the temporary NORAD ID, I can added as source in DB to update it automatically.
Sorry for the late reply. The decoder is the same. I just tested a HUNITY raw file with the mrc100_decoder and it works the same as the hunity_decoder we have.
Decoding HUNITY with gr-satellites.
Please confirm if these are valid frames.
name: HUNITY
norad: 98537
telemetry_servers:
- BMEWS
data:
&tlm Telemetry:
unknown
&signalling Signalling:
unknown
transmitters:
1k25 FSK:
frequency: 437.390e+6
modulation: FSK
baudrate: 1250
deviation: 312.5
framing: MRC-100 RA
frame size: 126
data:
- *tlm
2k5 FSK:
frequency: 437.390e+6
modulation: FSK
baudrate: 2500
deviation: 625
framing: MRC-100 RA
frame size: 126
data:
- *tlm
5k FSK:
frequency: 437.390e+6
modulation: FSK
baudrate: 5000
deviation: 1250
framing: MRC-100 RA
frame size: 126
data:
- *tlm
12k5 FSK:
frequency: 437.390e+6
modulation: FSK
baudrate: 12500
deviation: 3125
framing: MRC-100 RA
frame size: 126
data:
- *tlm
gr_satellites HUNITY.yml --wavfile 12905282.ogg --samp_rate 48e3
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 12k5 FSK))
pdu length = 126 bytes
pdu vector contents =
0000: aa 30 f0 da b6 01 00 68 00 be 21 05 01 df 42 8f
0010: 86 38 17 7e b7 36 69 91 03 81 3b 89 01 91 87 01
0020: 00 51 5a 01 00 c9 87 59 03 51 49 49 01 c9 87 49
0030: 05 41 3e 59 02 b9 86 a9 00 01 1f 21 00 91 87 09
0040: 00 51 5a c1 01 f1 86 01 01 f9 04 41 01 b9 08 e1
0050: 07 e1 13 91 0d 91 27 01 ff 01 ff 01 ff 01 ff 01
0060: ff 01 ff 01 ff 01 ff 01 ff 01 ff 01 ff 01 ff 01
0070: ff aa aa 10 aa 40 f7 09 cc da 3a a9 da 79
************************************
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 12k5 FSK))
pdu length = 126 bytes
pdu vector contents =
0000: aa 80 78 df b6 01 00 68 00 be 21 05 01 df 42 eb
0010: cd 2b 78 9c b7 36 69 a9 03 b1 34 61 01 91 87 01
0020: 00 91 5b 81 00 01 88 51 04 d1 36 19 01 01 88 01
0030: 09 51 49 59 03 31 88 d9 00 b1 23 01 00 69 88 01
0040: 00 29 5b 41 02 81 86 01 01 f9 04 41 01 b9 08 e1
0050: 07 e1 13 91 0d 91 27 01 ff 01 ff 01 ff 01 ff 01
0060: ff 01 ff 01 ff 01 ff 01 ff 01 ff 01 ff 01 ff 01
0070: ff aa aa 94 8a 72 5b d7 67 e9 77 03 e4 11
************************************
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 12k5 FSK))
pdu length = 126 bytes
pdu vector contents =
0000: aa 0c 9e e0 b6 01 00 0f 00 be 21 09 00 60 8b e9
0010: 26 d1 6c 45 04 00 00 00 aa aa aa aa aa aa aa aa
0020: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa
0030: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa
0040: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa
0050: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa
0060: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa
0070: aa aa aa 67 80 7e 7e 3c a5 9d 73 54 34 c5
************************************
Jan | PE0SAT
Hi everybody. I am Birol Keskin from LUNA-1 Team.
This is the TLE that we got from Space-Track unpublished folder. It works well for two days.
@fredy Could we upload this TLE to SatNOGS DB.
1 82040C 25276P 25341.91661852 +.00013968 +00000+0 +67855-3 0 00103
2 82040 97.4485 53.7904 0002786 146.9258 213.2151 15.18557680001393