I’m not familiar w/ the framing used by uHETSat, but I do get a 38k4 decode from my I/Q recording using ‘Mobitex’ framing.
However, that could easily be a false positive.
I’m not familiar w/ the framing used by uHETSat, but I do get a 38k4 decode from my I/Q recording using ‘Mobitex’ framing.
However, that could easily be a false positive.
Beat me by two hours…haha. well played
TLE update for M-SEL/CORTEZ
M-SEL/CORTEZ
1 98648U 00000A 25083.31968904 .00000000 00000-0 16393-4 0 02
2 98648 97.7394 338.8360 0002339 101.2000 37.7273 15.16743437 08
Due to some technical issues, I didn’t manage to get TLE earlier for this satellite, so this one may not be fully accurate due to not using many extracted points, however it is much better than the old one which was the post launch TLE from celestrak.
Hi Scott,
Looking at a previous observation and corresponding IQ recording it seems the signal you received is uHetSat.
There is no confirmation but it seems this ESA satellite is also using CCSDS.
Here the yaml I created some time ago:
name: UHETSAT
norad: 98969
data:
&tlm Telemetry:
unknown
transmitters:
38k4 CCSDS Uncoded downlink:
frequency: 401.500e+6
modulation: FSK
baudrate: 38400
framing: CCSDS Uncoded
frame size: 2048
data:
- *tlm
38k4 CCSDS Solomon downlink:
frequency: 401.500e+6
modulation: FSK
baudrate: 38400
framing: CCSDS Reed-Solomon
frame size: 2048
RS basis: dual
RS interleaving: 5
data:
- *tlm
This is producing data, but again no idea if it makes sense.
All the data I saved can be found at this location.
Jan - PE0SAT
Looking at this mornings STRF obs on 400 - 404 MHz one can get the impression HERMES H1 and UHETSAT are in a similar orbit. All passes (12 hours) they are showing the same as the example below.
This evening 21:50 UTC HERMES H1 will pass Europe and I will check if there is activity.
TLE update for Sphinx/Frazier
Sphinx/Frazier
1 98621U 25052S 25083.37070288 .00000000 00000-0 30122-5 0 09
2 98621 97.4477 335.3502 0002900 328.4921 85.1506 15.16880029 02
Similar to M-SEL/CORTEZ TLE set, this also was affected by the technical issue, so this TLE is based on a limited sample of points, thus it is not fully accurate.
Hi everyone, here below you can find the foreseen TLE for HERMES H2, to be released from ION on 2025/03/25 at 06:49:25 UTC.
1 99999U 25000XX 25084.35029752 .00004178 00000-0 -28770-5 0 9994
2 99999 97.4424 339.4970 0004879 231.2892 129.1555 15.17705173 59107
We are still looking for HERMES H1, we hope to have some good news in the next hours!
Ciao
Yuri for the HERMES Team
Yup, now seeing 4K8 GMSK OTP-2 , after a brief 9K8 GMSK interlude of call showing up as OTP-7 and ABCDEF as Mineo-san points out. But now music!
link to audio
ok Rob, - so what;s the tune?
Bob N6RFM
Here is the TLE set, changed to use the temporary NORAD ID in DB:
HERMES H2
1 98614U 25000XX 25084.35029752 .00004178 00000-0 -28770-5 0 9997
2 98614 97.4424 339.4970 0004879 231.2892 129.1555 15.17705173 59100
Really proud of this one - sought out the permission from the original maker of that little tune and of the game that inspired me to get into astrodynamics - Felipe Falanghe from Kerbal Space Program!
New TLE for ION SCV-017:
ION SCV-017
1 98635U 25052X 25084.36195521 .00000000 00000-0 56372-3 0 05
2 98635 97.4434 339.5253 0004588 342.2991 81.5095 15.16695388 09
sites.txt (10.4 KB)
ion17_084_v1.dat (1.3 KB)
TLE update for the two groups (1-6 and 7-9) of TEVEL2 satellites:
TEVEL2-1
1 98647U 25052B 25083.91327697 .00000000 00000-0 30253-3 0 09
2 98647 97.4482 342.6206 0005205 328.8574 158.1514 15.17697871 09
TEVEL2-2
1 98646U 25052B 25083.91327697 .00000000 00000-0 30253-3 0 08
2 98646 97.4482 342.6206 0005205 328.8574 158.1514 15.17697871 08
TEVEL2-3
1 98645U 25052B 25083.91327697 .00000000 00000-0 30253-3 0 07
2 98645 97.4482 342.6206 0005205 328.8574 158.1514 15.17697871 07
TEVEL2-4
1 98644U 25052B 25083.91327697 .00000000 00000-0 30253-3 0 06
2 98644 97.4482 342.6206 0005205 328.8574 158.1514 15.17697871 06
TEVEL2-5
1 98643U 25052B 25083.91327697 .00000000 00000-0 30253-3 0 05
2 98643 97.4482 342.6206 0005205 328.8574 158.1514 15.17697871 05
TEVEL2-6
1 98642U 25052B 25083.91327697 .00000000 00000-0 30253-3 0 04
2 98642 97.4482 342.6206 0005205 328.8574 158.1514 15.17697871 04
TEVEL2-7
1 98641U 25052B 25084.24623343 .00000000 00000-0 31109-3 0 08
2 98641 97.4482 333.2067 0005205 328.8574 170.4811 15.17784156 04
TEVEL2-8
1 98640U 25052B 25084.24623343 .00000000 00000-0 31109-3 0 07
2 98640 97.4482 333.2067 0005205 328.8574 170.4811 15.17784156 03
TEVEL2-9
1 98639U 25052B 25084.24623343 .00000000 00000-0 31109-3 0 05
2 98639 97.4482 333.2067 0005205 328.8574 170.4811 15.17784156 01
Thank you!
Once again today (25-Mar) I monitored 401.500 for Hermes-H1 and as before, was greeted by a signal likely from another satellite.
The one data packet appearing about half-way through the pass “appeared” to possibly be 38k4 in Inspectrum
If anyone would like to formulate a TLE for this object, my entire I/Q file is at:
https://www.qsl.net/k/k4kdr//iq/2025-03-25-unk/
… and as the standard GQRX naming convention indicates, the recording start time (UTC) was: 20250325_145122, and the sample rate was 375000.
Additionally, my location is:
37.78 N, 77.61 W
Awesome! Thanks Rob
TLE update for JINJUSAT-1B
JINJUSAT-1B
1 98650U 14900A 25084.68007144 .00000000 00000-0 29377-3 0 05
2 98650 97.4529 333.3487 0002930 200.7175 204.8531 15.18470205 09
Note: the TLE is not very accurate, will need more observations to improve the accuracy.
TLE update for UVSQ-SAT NG
UVSQ-SAT NG
1 98638U 14900A 25080.30193324 .00000000 00000-0 29364-3 0 08
2 98638 97.7477 325.5931 0003498 302.8189 112.3068 14.92080437 09
Note: TLE may not be accurate as the observations that used were 4 days old, as the satellite hasn’t been received since ~2025-03-21 22:00.
Updated TLE for BOTSAT-1:
BOTSAT-1
1 98636U 25052G 25084.76857898 .00000000 00000-0 29619-3 0 06
2 98636 97.4386 341.3159 0001336 131.8788 25.1149 15.17670876 06
Note: It will need some fine tuning to be more accurate when we have more observations
Indeed this is another satellite, it is uHETSat, it is also visible in many Network’s observations.
Unfortunately no signal from either HERMES H1 and H2 is received in Network observations, but we will keep tracking.
Signals visible in these observations have been verified to be from uHETSat, Outpost Mission 2, several Connecta satellites. Two examples: