I’m not aware if HUCSat is transmitting anything ELSE, but yes, we’re getting 125k LoRa from it on 437.400. ‘Most’ of the time, the sequence is a short packet followed by a longer one.
There were preliminary TLEs provided by (I think) someone affiliated w/ one of the missions, but of course they are getting a little old now. Thankfully I’m using an omni antenna.
These will be far from perfect but should be better then the preliminary.
Also without a way to identify the signal there is not 100% proof this is HUCSAT.
Hello, and thank you for the TLE refinement! I can confirm that these telemetry beacons are from HUCSat.
Additionally, HUCSat has been correlated with NORAD ID 69794, and our HUCSat team has a correlation claim in progress with the Space-Track folks, so that change should be reflected there shortly.
This seems to be incorrect even when manually correcting values, as this would put us in a drastically different (impossibly so over such a time period) orbit than COCONUT’s reported orbit. We are trying to get clarification from our deployment provider with corrected TLE even if out of date.
I’ve checked observations from CubeBel-2 (10 kHz higher) where both satellites were over my horizon (that was on 5th and 10th).
However, no signs of a 1k2 signal 10 kHz lower.
How is the current beacon intervall?
What is the format for the 1k2 FSK? (Line code, scrambler, channel coding, bit stuffing …?)
We just heard back from the launch/deployment provider, and they said the previous TLE they gave us was generated by Claude AI without calculating anything, so I think its safe to say that is meaningless…
@dl7ndr there’s a link to our amateur radio packet on our SatNOGS DB page. We did not expect beaconing to begin from the satellite until the 9th, so the pass on the 5th shouldn’t have heard anything. As to the pass on the 10th, I don’t know… due to the above issue we don’t precisely know where it is right now (Although I expect it to be relatively close to COCONUT) and the beacon is relatively infrequent unfortunately due to power constraints (every 90 secs).
That’s very sad. Usually in such deployment we start with ISS TLE at the time of deployment and start updating them as we receive signals from the satellite. Unfortunately there wasn’t any announcement or messages to letting us know about this deployment, neither from the satellite teams deployed or Voyager (Nanoracks), interestingly it is first time after years that there wasn’t a live stream.
That’s unfortunate as it doesn’t allow us to track the first critical hours/days of the satellites which sometimes giving valuable information about the satellites. Anyway let’s see what we can do from now on. Current status there are 6 objects for the satellites of this deployment, here are their latest TLE:
Except of OBJECT YJ which is close but separated from the other objects, all the other are very close, so I’m going to choose OBJECT YN to follow and track for LEOPARDSat-1. This object has common ground-track with the others and the maximum common ground-track with OBJECT YJ, increasing our chance to get signal from LEOPARDSat-1.
From a quick check on some spectrum observations on 436.980 there wasn’t any signal, but let’s keep watching and observing. @blah43695 from your messages I understand that there is any contact/reception from the satellite from the team or other 3rd party observer, please confirm or correct me if I’m wrong.
EDIT: checked the first post that we have the deployment times and info gathered from various sources, from that, it seems that PROVES - Electra deployed a couple of hours from the rest, so there is big probability that this is OBJECT YJ that is away from the others.
