Thanks for it, from tomorrow that I’ll schedule for the next 48h, I’m going to schedule only GMSK transmitter for Erminaz!
Thank you both of you! I’m going to open a thread about SIDLOC later today and move your messages there, so we have them separately.
If you or any one else needs storage to upload IQ for SIDLOC, feel free to send me a pm here or contact me in email to fredy@libre.space.
Useful to know that this is another satellite. Thanks!
Dear members,
We have two 3U CubeSats that were onboard the OSSIE-D (BEECON-A and PRISM-A). OSSIE-D informed us of the following:
OSSIE-D State at the Start of the Deployment Sequence
Epoch: 2026-10-01T21:03:09.950Z
r_ecef_m: [5342430.221, 803466.453, 4274232.095]
v_ecef_m_per_s: [-4366.809, -2326.286, 5877.407]
But no further information related to our satellites. Each pf the two satellites should be sending a beacon msg (UHF: 401.025 MHz +/- 200 KHz, half duplex).
The UHF radio chip used onboard is the AT86RF215
–GMSK at 50kbps, BT=0.5, NRZL
–Beacon msg duration is 163.68 msec
–We beacon for 10 sec then pause for 30 sec
–During the 10 sec beaconing period: Every 217 msec we send 163.68 msec beacon message (1,023 Bytes)
Example from factory-generated IQ File:
[RX #1] 17:30:16 UTC len=1023B (PSDU 1019+FCS) CRC=OK SNR=59.5dB SCID=0x6A08 VCID=20
a6a082868a40608aa692a68a9cf703f07b7b7a6500450000000000000000000000000000000000000000f10000000200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000005c378f9930581b89
============================================================
What is the question here?
There are telecommands that are protected, digipeater usage is not one of them!
Hello there,
I suggested another satellite that was ejected from UARX. Its BEECON-A. Could someone have a look on that one, please? SatNOGS DB - BEECON-A
There is no temporary NORAD-ID assigned now. Could we have followed that one by one of the other UARX-Sats?
Hi,
This is Wael Ibrahim from Ethereal Space (owner and operator of the two satellites BEECON-A and PRISM-A) that were hosted onboard the UARX OTV OSSIE-D. I posted a msg above with more details about our UHF beacon DL_ed msgs.
TLE based on OSSIE-D by celestrak post launch TLE:
BEECON-A
1 98200C 26227BL 26274.81462064 -.00012609 00000-0 -12652-2 0 9998
2 98200 97.4462 344.3315 0003041 135.4993 228.5794 15.17406584 17
PRISM-A
1 98199C 26227BL 26274.81462064 -.00012609 00000-0 -12652-2 0 9995
2 98199 97.4462 344.3315 0003041 135.4993 228.5794 15.17406584 14
Note: all the UARX satellites that use the OSSIE-D TLE should be ±3min inaccurate.
I’m going to schedule some observations for these two satellites by doing some changes on the already scheduled observations.
So, in total from OSSIE-D are expected to be deployed 19 satellites, in DB we don’t have:
And we have:
You may use ERMINAZ-1U.yml for ERMINAZ-2* but you have to remove frame size: 128.
Hi Fredy, what empirical evidence confirms that all 19 satellites have actually been deployed from OSSIE-D?
Being listed in the SatNOGS database or in the OSSIE-D manifest does not by itself confirm deployment. Likewise, assigning temporary NORAD IDs or using TLEs derived from the OSSIE-D orbit only helps schedule observations; it does not prove that each satellite is flying independently.
For some payloads, we only know that the deployment sequence was initiated. Do we have individual confirmation from UARX, deployer telemetry, received beacons, optical evidence, or separately tracked orbital objects for all 19 satellites?
I believe some of the satellites currently shown as deployed may not yet have been physically ejected. Until independent evidence is available, it might be more accurate to mark them as “deployment reported/commanded — confirmation pending.”
You are right, I’ve changed the wording to “expected to be deployed” in my initial message.
To be honest with all this secrecy it’s difficult to understand what happened and if the deployment sequence includes all the satellites or not.
Until now, I haven’t checked all the observations in Network, but for sure I know that the 4 SIDLOC PQs, NIS-PQ and the 3 ERMINAZ have been deployed.
Let’s gather evidence for the rest of the satellites.
Is Erminaz-2U expected to transmit CW beaconing ?
It seems statistically very unlikely that several satellites built by independent institutions would all fail at the same time “after deployment”.
For example, even assuming a relatively high independent failure probability of 10% for each satellite, the probability of four simultaneous failures would be:
P = 0.10⁴ = 0.0001 = 0.01%, or approximately 1 in 10,000.
However, when several independently built satellites associated with the same OTV remain unheard despite monitoring by multiple ground stations, a common cause—such as a pending or incomplete deployment sequence—should be seriously considered.
For now, we suggest continuing to monitor their published frequencies using the latest available OSSIE-D orbital elements. Any reception report, waterfall or IQ recording could be extremely valuable.
