Updated TLE for NUSHSAT-1:
NUSHSAT-1
1 98628U 25078.96024621 .00000000 00000-0 -15001-3 0 09
2 98628 97.4529 334.1893 0002930 200.7175 286.9207 15.17715286 05
4 Likes
Updated TLE for ION Deployer:
ION SCV-017
1 98635U 25052X 25079.34746695 .00000000 00000-0 -46985-3 0 01
2 98635 97.4434 333.8792 0002088 342.2991 80.4430 15.16617854 00
2 Likes
New updated TLE set for the Unknown satellite of T13, which as we have said in the previous posts it is almost sure that is Al Munther satellite:
Unknown satellite of T13
1 98616U 25079.34872086 .00000000 00000-0 10655-2 0 03
2 98616 97.4396 334.8733 0006612 339.5368 80.3951 15.16183279 02
2 Likes
Updated TLE for UVSQ-SAT NG, not fully accurate but better than the previous used ones:
UVSQ-SAT NG
1 98638U 14900A 25079.42751508 .00000000 00000-0 29456-3 0 05
2 98638 97.7477 333.4284 0003498 302.8189 100.3321 14.86681747 01
2 Likes
understood, tnx.
NUSHSAT-1 TLE Update
NUSHSAT-1
1 98628U 25080.39689340 .00000000 00000-0 12529-2 0 04
2 98628 97.4529 335.7371 0002930 200.7175 211.7711 15.17796546 07
3 Likes
New TLE for OTP-2 - GNSS based generation
1 98652U 25079.93849266 .00025946 00000-0 13358-2 0 00001
2 98652 097.4377 335.1561 0005879 319.2026 081.5378 15.16350320000823
Waterfall corrected with this TLE (don’t mind the first beacon, it’s an anomaly)
1 Like
NUSHSAT-1 TLE Update, only a small correction
NUSHSAT-1
1 98628U 25081.38643810 .00000000 00000-0 15730-2 0 03
2 98628 97.4529 336.7159 0002930 200.7175 215.6154 15.17900481 01
3 Likes
Updated TLE for Buccaneer MM
Buccaneer MM
1 98648U 00000A 25081.09169108 .00000000 00000-0 98799-4 0 04
2 98648 97.7394 336.1428 0006083 17.6570 309.6422 14.91283612 09
buc_081_v1.dat (1.8 KB)
sites.txt (10.4 KB)
2 Likes
Tracking 98652, expecting OTP-2. 23Mar25 0444Z EM12jw.
Has anyone else noticed this source call sign?
Good hunting all,
Bob
N6RFM
3 Likes
NUSHSAT-1 TLE Update
NUSHSAT-1
1 98628U 25082.44018145 .00000000 00000-0 15910-2 0 08
2 98628 97.4529 337.7567 0002930 200.7175 210.2088 15.17971452 08
2 Likes
I’m um…working on it. I had a typo in my last change. I was really hoping to slip it past you all…should have known better!
Should be updated now
3 Likes
OTP-2 callsign: “ABCDEF”
4 Likes
The first HERMES cubesat should have been deployed this morning from the ION SCV transporter.
Here is the preliminary TLE:
1 99999U 25000XX 25083.36066247 .00004178 00000-0 -40745-4 0 9999
2 99999 97.4421 338.5236 0007104 328.6225 31.3336 15.15647437 59101
The beacon info is:
Frequency 401.5
Band 401.43 401.57
Beacon every 20s for 1 sec
Observations are encouraged!
Thanks,
R. Campana on behalf of the HERMES team
1 Like
Hi @rcampana and welcome in the community!
I’ve added an entry for this HERMES cubesat in DB with the temporary NORAD ID 98615.
I’ve scheduled also some observations for the next 24h, however due to the last minute request the available slots were only passes under 30 degrees which reduces the chance for good observations. Please for the next deployments let us know at least 24h before in order to arrange the DB entry and scheduling on time, even if the deployment isn’t 100% sure.
Now some questions for the mission that will help us track it better:
- How many HERMES cubesats will be deployed? This will help to add them in DB earlier and be prepared for them.
- Do you have any dates for possible deployments?
- What are their names, I’ve named this one as “HERMES 1” but we can change it if it is not correct.
- About the transmission, can you share the modulation and any framing you are using? This may help us to demodulated the frames that satellite is beaconing and identify it with better certainty.
Here is the TLE you share changed to the temporary NORAD ID we use in DB:
HERMES H1
1 98615U 25000XX 25083.36066247 .00004178 00000-0 -40745-4 0 9993
2 98615 97.4421 338.5236 0007104 328.6225 31.3336 15.15647437 59105
2 Likes
Hi Fredy, thanks!
There are six HERMES satellites, named HERMES H1, H2, H3, H4, H5 and H6.
We are still waiting for deployment confirmation for H1, but as a baseline H2 and H3 should be released tomorrow and Wednesday morning (UTC), while the last three on April 7, 8 and 9.
HERMES H1 should be more correct, sorry I should have mentioned that in my previous message.
Modulation:
GFSK
Encoding:
CCSDS 231.0-B-2: TC synchronization and channel coding
CCSDS 232.0-B-2: space data link protocol
CCSDS 131.0-B-2: TM synchronization and channel coding
CCSDS 132.0-B-2: TM space data link protocol
Thanks again for your efforts!
cheers
R
2 Likes
Thanks for all the extra info! I’ll update the entries and future observations accordingly.
I forgot to ask about the baudrate, from the bandwidth I assume it is 9600 but correct me if I’m wrong.
EDIT:
Also I forgot to ask if the rest of the HERMES sats will be on the same frequency.
1 Like
Yes, the baudrate should be 9600.
2 Likes