HERMES H5 update: the satellite has not been released yet. We will promptly update you on the new release opportunity as soon as the launch service provider informs us.
Francesco from HERMES team
HERMES H5 update: the satellite has not been released yet. We will promptly update you on the new release opportunity as soon as the launch service provider informs us.
Francesco from HERMES team
HERMES H5 new release attempt is foreseen for today at 18:47 UTC.
Updated TLEs from the service provider:
HERMES H5
1 99999U 25000XX 25099.84861111 .00004178 00000-0 -54969-5 0 9996
2 99999 97.4508 354.7199 0005560 205.8432 157.9528 15.17474674 59106
Cheers
R
There are 4 more objects for this launch, probably satellites deployed by the ION deployer:
0 TBA - TO BE ASSIGNED
1 63489U 25052BK 25098.93149022 .00009747 00000-0 50316-3 0 9993
2 63489 97.4458 353.7941 0005540 238.3671 121.7022 15.16508911 3886
0 TBA - TO BE ASSIGNED
1 63490U 25052BL 25097.66745474 .00037499 00000-0 17833-2 0 9998
2 63490 97.4393 352.5807 0010906 224.1675 135.8689 15.19032878 3694
0 TBA - TO BE ASSIGNED
1 63491U 25052BM 25097.66707447 .00063990 00000-0 30001-2 0 9994
2 63491 97.4395 352.5812 0011097 225.0015 135.0321 15.19375027 3694
0 TBA - TO BE ASSIGNED
1 63492U 25052BN 25097.66853268 .00034903 00000-0 16718-2 0 9999
2 63492 97.4403 352.5793 0011204 229.1531 130.8733 15.18797281 3690
Thanks @PE0SAT for pointing it out.
Changed in DB to follow these new Objects as described bellow:
HADES-ICM β 63492
HYDRA-W β 63490
HERMES H6 β 63489
While the fits are good for all of them they may not be the right ones, so we can not move to identification, we need to keep checking the next days to fully confirm them.
Especially for HADES-ICM and HYDRA-W, according to the booklet for their mission https://www.dorbit.space/media/6/0.pdf it looks like that there were 3 more pocketqubes (UNICORN-2O, 2P & 2Q) which we donβt know when and if they have been deployed, so one or all of them may be one of the 4 new objects published by space-track.org.
So, letβs keep trackingβ¦
PS @ea4gqs if you have any info you can share for the UNICORN satellites deployment that will help on the identification, please let us know.
We confirm the deployment of HERMES H5, which has been received and decoded by at least one SATNOGS observation (#11378056). Thank you very much!
The deployment of the next HERMES satellite, HERMES H4, is foreseen for tomorrow April 10, at 05:52:00 UTC (yes, a short while from now!)
Preliminary post-deployment TLEs that were provided to us are:
HERMES H4
1 99999U 25000XX 25100.31041667 .00004178 00000-0 -13495-4 0 9995
2 99999 97.4404 355.1732 0002726 313.1573 50.5636 15.15959465 59101
Cheers
Riccardo for the HERMES team
HERMES H5 and HERMES H4 have both been received and demodulated by several SATNOGS observation and also by our ground station.
Once again we are grateful for your support!
The deployment of the last HERMES satellite, HERMES H3, is foreseen for tomorrow. As soon as we will get a precise deployment time and TLE we will update you.
Thanks
Riccardo on behalf of the HERMES team
Decoding HERMES-H5 observation
gr_satellites HERMES-H5.yml --rawint16 iq_11383164_100000.wav --samp_rate 100000 --iq
name: HERMES-H5
norad: 98611
data:
&tlm Telemetry:
unknown
transmitters:
25k CCSDS downlink:
frequency: 401.500e+6
modulation: FSK
baudrate: 25000
framing: CCSDS Concatenated
frame size: 223
RS basis: dual
RS interleave depth: 1
scrambler: CCSDS
convolutional: NASA-DSN
syncword threshold: 2
data:
- *tlm
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 25k CCSDS downlink) (rs_errors . 0))
pdu length = 223 bytes
pdu vector contents =
0000: 2d 87 02 02 18 00 08 14 ea be 00 69 20 03 19 00
0010: 00 00 39 09 eb aa e4 b3 08 87 00 95 00 0b 01 39
0020: 01 97 00 8f 00 ae 01 c8 23 ef 21 6a 11 93 22 83
0030: 16 86 16 68 01 a4 01 86 01 70 3e 01 00 00 00 8d
0040: 00 00 00 11 00 82 00 9c 01 6a cb 00 00 09 29 03
0050: 00 06 00 05 00 d8 01 04 00 aa 00 a4 00 03 00 00
0060: 00 e0 00 a1 01 82 81 40 40 40 40 78 6a ba c2 50
0070: b1 40 00 00 78 34 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0
0080: e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0
0090: e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0
00a0: e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0
00b0: e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0
00c0: e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0
00d0: e0 e0 e0 e0 e0 e0 e0 e0 e0 01 0c c0 00 73 13
************************************
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 25k CCSDS downlink) (rs_errors . 0))
pdu length = 223 bytes
pdu vector contents =
0000: 2d 87 03 03 18 00 08 14 ea d3 00 69 20 03 19 00
0010: 00 00 39 09 eb aa fa 7e 08 1c 01 62 01 59 00 a3
0020: 01 e2 00 2b 01 ae 01 0d 24 a9 23 c4 10 7f 23 a1
0030: 18 52 19 42 05 74 01 86 01 70 3f 01 00 00 00 8d
0040: 00 00 00 11 00 8a 00 9c 01 7f cb 00 00 f4 28 03
0050: 00 06 00 08 00 1a 03 04 00 aa 00 1e 00 06 00 00
0060: 00 e3 00 a1 01 83 01 40 40 40 40 7d aa ba c2 55
0070: f1 40 00 00 e0 cf e0 e0 e0 e0 e0 e0 e0 e0 e0 e0
0080: e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0
0090: e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0
00a0: e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0
00b0: e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0
00c0: e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0
00d0: e0 e0 e0 e0 e0 e0 e0 e0 e0 01 00 c0 00 cf 2e
************************************
Deployment of the final HERMES cubesat, HERMES H3, is foreseen for tomorrow, April 11, at 05:37:00 UTC.
As usual, we are grateful for any observation!
Preliminary post-deployment TLE are:
HERMES H3
1 99999U 25000XX 25101.29930556 .00004178 00000-0 -33999-4 0 9998
2 99999 97.4390 356.1456 0007796 198.3722 162.5978 15.17928878 59109
Cheers
Riccardo on behalf of the HERMES team
Unicorn 2Q was deployed at the same time as HADES-ICM and HYDRA-W.
FΓ©lix
@rcampana was the deployment successful? I see some observations like this SatNOGS Network - Observation 11386587 that have signals but not sure if belong to HERMES H3 or maybe it is close to H4 and we see its data.
Hi Fredy,
yes we confirm the deployment of HERMES H3 and we have received and decoded several beacons both on SATNOGS observations and on our ground station.
H3, H4 and H5 are very close together so there is a certain overlap of beacons in a given passage.
With all the HERMES sats on the same freq & still close together, Bob (N6RFM) had a great idea - configure GNU Radio / gr-satellites to upload to the proper SatNogs ID based on the 1st two bytes of each frame!
63233 Lizziesat on 2201.200 MHz give or take some kHz.
3 obs in strf so going to suggest to DB
HERMES H2 is now identified as OBJECT AK 63243, here are the ikhnos results.
Hi all,
Thanks again for all of your support in tracking Buccaneer after launch! In preparation for payload operations we will be disabling UHF beacon transmissions, so going forward Buccaneer signals will only be observable when in communication with our ground station in Adelaide, South Australia.
Thanks again!
73
Mark VK5QI
Thanks letting us know Mark.
Best Wishes to the Buccaneer team.
Bob
N6RFM
Hi everyone,
I wanted to provide a brief update on the status of the Hermes mission. As of today, we are regularly receiving beacons from satellites H3, H5, and H6, with occasional signals from H2 and H4. We are currently able to communicate with H3 in uplink through our Ground Station. To improve our coverage, weβve developed a SatNOGS audio decoding pipeline, which has been extremely helpful in gathering telemetry data from around the world.
As you may understand, your support has been essential for us in this phase and we will be really glad if the community could continue to support the Hermes mission with observations, which will help us to carry out a successful commissioning of the satellites.
Thank you in advance for your help!
Francesco on behalf of Hermes team
A status update, most of the TEVEL2 sats are now identified. Also no it looks like that the objects for HYDRA-W and HADES-ICM work fine for the last 10 days, so itβs almost impossible to belong to the other deployment of UNICORN satellites expected from ION deployer. Additionally UNICORN-2Q, which was on the same pod with them, has been identified as the third object between those two in space-track.org. And also we donβt have any evidence that the satellites from the other pod, the other UNICORN satellites, have been deployed.
Finally we still expect several OBJECTS, at least four for the deployed HERMES H3-6.
Temporary NORAD ID | Satellite | NORAD ID to follow | Other NORAD IDs | Identified | Deployed | Reception | Last Update |
---|---|---|---|---|---|---|---|
RECEIVED & DEMODULATED/DECODED | |||||||
- | OTP-2 | 63235 | - | YES | YES | Received | Identified, here are the ikhnos results |
- | ION SCV-017 | 63230 | - | YES | YES | Received | Identified, here are the ikhnos results |
- | BOTSAT-1 | 63216 | - | YES | YES | Received | Identified, here are the ikhnos results |
- | UVSQ-SAT-NG | 63251 | - | YES | YES | Received | Identified, here are the ikhnos results |
- | JINJUSat-1B | 63210 | - | YES | YES | Received | Identified, here are the ikhnos results |
- | NUSHSat1 | 63211 | - | YES | YES | Received | Identified, here are the ikhnos results |
- | Al-Munther | 63240 | - | YES | YES | Received | Identified, here are the ikhnos results |
- | TEVEL2-1 | 63217 | - | YES | YES | Received | Identified, here are the ikhnos results |
98646 | TEVEL2-2 | 63218 | 63219 | NO | YES | YES | Received, continue to follow 63218, other possible 63219, removed 63217 |
98645 | TEVEL2-3 | 63219 | 63218 | NO | YES | YES | Received, continue to follow 63219, other possible 63218, removed 63217 |
- | TEVEL2-4 | 63213 | - | YES | YES | Received | Identified, here are the ikhnos results |
- | TEVEL2-5 | 63214 | - | YES | YES | Received | Identified, here are the ikhnos results |
- | TEVEL2-6 | 63215 | - | YES | YES | Received | Identified, here are the ikhnos results |
- | TEVEL2-7 | 63238 | - | YES | YES | Received | Identified, here are the ikhnos results |
- | TEVEL2-8 | 63239 | - | YES | YES | Received | Identified, here are the ikhnos results |
- | TEVEL2-9 | 63237 | - | YES | YES | Received | Identified, here are the ikhnos results |
98613 | HERMES H3 | - | - | NO | YES | YES | Received, waiting for new objects |
98612 | HERMES H4 | - | - | NO | YES | YES | Received, waiting for new objects |
98611 | HERMES H5 | - | - | NO | YES | YES | Received, waiting for new objects |
98610 | HERMES H6 | - | - | NO | YES | YES | Received, waiting for new objects |
- | HADES-ICM | 63492 | - | YES | YES | Received | Identified, here are the ikhnos results |
- | HYDRA-W | 63490 | - | YES | YES | Received | Identified, here are the ikhnos results |
- | Buccaneer MM | 63245 | - | YES | YES | Received | Identified, here are the ikhnos results |
- | HERMES H2 | 63243 | - | YES | YES | Received | Identified, here are the ikhnos results |
RECEIVED | |||||||
- | M-SEL/CORTEZ | 63231 | - | YES | YES | Received | Identified, here are the ikhnos results |
- | Sphinx/Frazier | 63232 | - | YES | YES | Received | Identified, here are the ikhnos results |
UNKNOWN STATUS | |||||||
98615 | HERMES H1 | 63242 | all | NO | YES | NO | Changed to follow 63242(per team request), other possible all |
98737 | NILA | 63236 | all | NO | YES | NO | Continue to follow 63236(random choice), other possible all |
98630 | HYVRID | 63252 | all | NO | YES | NO | Continue to follow 63252(random choice), other possible all |
- | SOAP-1 | 63263 | - | YES | YES | - | Identified in space-track.org |
- | Clarity-1 | 63227 | - | YES | YES | - | Identified in space-track.org |
- | AEROCUBE-18 A | 63220 | - | YES | YES | - | Identified in space-track.org |
- | AEROCUBE-18 B | 63222 | - | YES | YES | - | Identified in space-track.org |
- | DROID.002 | 63223 | - | YES | YES | - | Identified in space-track.org |
- | IOD-1 | 63212 | - | YES | YES | - | Identified in space-track.org |
- | YAM-8 | 63254 | - | YES | YES | - | Identified in space-track.org |
98625 | EZIE-A | - | all | NO | YES | NO | |
98624 | EZIE-B | - | all | NO | YES | NO | |
98623 | EZIE-C | - | all | NO | YES | NO | |
98632 | ARVAKER I | - | all | NO | YES | NO | |
98629 | Firesat-0 | - | all | NO | YES | NO |