The Team behind the ET-001 constellation (ET-001 A, B, C, & D) shared RX details in time for the capture of 62k5 LoRa downlinks from -2- of them tonight on 465.500 MHz.
Congratulations, you are the first one for the UHF digipeater!
And thanks for pointing me to this wrong message.
I’ve corrected it on the digipeater dashboard. It now shows your callsign.
As for the UHF digipeater, I’ve tried it many times along with the one from KOSTKA without success.
It seems to be the same for me like with GRBBeta. VHF is very sensitive, but UHF is hard to come by with my capabilities.
Anyway, I’m looking forward to get a contact with you via both digis some day.
Same here… my uplinks decode perfectly w/ an in-house receiver SDR, but no luck w/ 9k6 LEO sats. I’ve made all kinds of audio & RF adjustments but nothing has helped so far.
Thanks Daniel, I tried today KOSTKA digipeater with the same setup, pass, strategy and “technically” success arrived (1 message repeated), but it was not so easy like with MARINA. Also I didn’t receive the repeated message, but (some) other station. However, the digipeater itself could be considered as “verified”. Perhaps it’s time to create KOSTKA’s section in Digipeater dashboard.
73 Brano OM1ATB
Thanks for testing, and again congratulations, Brano!
Looking at your antenna array, I guess I’ll never make it with my simple setup ):
I’m still waiting for an update of KOSTKA’s decoder from @ok2fis .
Currently it decodes only the telemetry beacons (with last digipeater user and last digipeater count).
Once the new version is online, I’ll add KOSTKA to the digipeater dashboard.
I was able to match it’s TLE set:
1 98259U 26194.91865210 +.00001488 +00000+0 +15610-3 0 00163
2 98259 97.7581 95.2617 0005175 106.4647 253.7140 14.91010768000984
to object 88214 in the space-track TLE file 26197_88202-88234_TLE.txt
NORAD
Radial (km)
Along-track (km)
Cross-track (km)
R+N combined
88214
0.102
−0.308
−0.017
0.103
88237
−0.161
−87.538
−0.030
0.164
88215
0.267
37.489
0.107
0.288
88239
−0.164
6.505
0.664
0.684
88236
−0.229
−50.284
0.680
0.718
Propagated the target (98259) and all candidates from the space-track TLE file to the target’s own epoch (2026-day-194.919) via SGP4, then decomposed the position residual into the target’s RTN (or RIC) frame.
I was able to match it’s TLE set:
1 98257U 26194.91878597 +.00000266 +00000+0 +32461-4 0 00160
2 98257 97.7587 95.2617 0004834 107.3192 252.8556 14.90972435000982
to object 88237 in the space-track TLE file 26197_88236-88277_TLE.txt
NORAD
Radial (km)
Along-track (km)
Cross-track (km)
R+N combined
88237
0.155
−0.115
−0.030
0.158
88214
−0.680
87.116
−0.018
0.680
88236
−0.390
37.145
0.668
0.773
88244
−0.772
−128.835
0.300
0.829
88215
−0.984
124.904
0.105
0.989
Propagated the target (98257) and all candidates from the space-track TLE file to the target’s own epoch (2026-day-194.919) via SGP4, then decomposed the position residual into the target’s RTN (or RIC) frame.
I was able to match it’s TLE set:
1 98255U 26195.71723136 +.00001334 +00000+0 +13575-3 0 00177
2 98255 97.7561 96.0597 0010651 125.6582 234.5631 14.92377320001108
to object 88267 in the space-track TLE file 26197_88236-88277_TLE.txt
NORAD
Radial (km)
Along-track (km)
Cross-track (km)
R+N combined
88267
0.085
−0.332
−0.010
0.085
88268
−0.299
74.634
0.002
0.299
88265
−0.971
−126.769
0.261
1.005
88264
−0.994
−154.049
−0.172
1.009
88266
−0.869
−109.351
0.727
1.133
Propagated the target (98255) and all candidates from the space-track TLE file to the target’s own epoch (2026-day-195.717) via SGP4, then decomposed the position residual into the target’s RTN (or RIC) frame.
TLE updates from the latest analyst list, unfortunately due to some time off and traveling I haven’t managed to perform any analysis the last days, if there is any update that I miss, please let me know to update TLE in DB. I’ve added in the latest updates as noted in the previous posts: