Based on latest TLE set by @PE0SAT for EIRSAT-1, I’ve adjust them a little in order to propagate the epoch and be able to use the TLE set in DB and Network (latest TLE is the one with the biggest epoch):
I am trying to schedule observation of Hayasat 2023-12-02 19:30 to 2023-12-02 19:50 UTC, and getting this error: “Scheduling observation that starts at 2023-12-02 19:41:22 UTC exceeds scheduling limit for the period from 2023-11-30 21:01:59 UTC to 2023-12-02 21:01:49 UTC Reason for scheduling limit: Hayasat(99032) is frequency violator satellite”.
But my observation would be within the scheduling limits, why this error then?
I am new to this, so pardon me if I am missing something obvious.
What are the rules for satellites like this, is it not possible to observe them at all once we move out of certain post-launch window?
Disclosure I am not directly affiliated with the team, just a fan of the project.
EIRSAT-1 was much stronger than I expected for the first U.S. pass because the max elevation wasn’t even 20°! That Team should be very proud of getting off to such a good start. Thanks to everyone who helped identify the best TLE!
A status update, based on the space-track.org TLE sets, note that these TLE sets are still to be assigned and may describe a group of satellites, also we expect at least 18 (25 satellites - 7 objects) more TLE sets:
Has anybody get information about the AX25 frame structure of ENSO ? It would be nice to be able to have frames decoded once gr-satnogs will be setup for good demodulation.
What is the reason for the -1 multiplier ?
the cli tool have at least two options that can take negative numbers to invert, --input_gain -1 and for the fsk modes --deviation -500 (or whatever the deviantion needs to be)
#58470 did indeed track pretty close for EIRSAT-1 doppler correction on the pass over the U.S. East Coast this morning (02-Dec-2023), but at this elevation I didn’t QUITE have enough SNR to decode. Will look forward to higher passes another time!
A status update with the new TLE from space-track.org, that are now assigned. While in some cases we have very good fits, we expect more sets (we have 11 from at least 25 for now), so we are going to delay identification for a couple of days.
Received, demodulated by 3rd parties, changed to follow 58467, other possible 58466(unlikely), 58468, 58470(unlikely), 58471(unlikely), 58472(unlikely), removed 58465
Received, not demodulated there is a chance not to be it. changed to follow 58472, other possible 58465(unlikely), 58467(unlikely), 58468, 58470, 58471
Randomly chosen to follow 58465, all the objects are possible candidates
Note: While the status above is based on ikhnos results, several of them are just confirmations of @PE0SAT more accurate checks using strf observations and tools.
Indeed but it is very close to 58471 and 58472, it will need a couple of days for a better separation.
By the way I’ve seen in nasaspaceflight thread that D-Orbit has published info for this mission of ION
4 cubesats and one alba orbital deployer with 4 pocketqubes, plus some hosted paylaods:
LOGSATS (3U, Patriot Infovention, Thailand)
NanoFF A/B (2x 2U, TU Berlin, Germany)
ALISIO-1 (6U, IACTEC, Spain)
RECS (hosted, Politecnico di Milano, Italy)
Z01™ SuperTorquer (hosted, Zenno Astronautics, New Zealand)
MI:1 (hosted, TRL11, US)
Pono 1 (hosted, Privateer, US)
Albapods (hosted, Alba Orbital, UK) carrying the three Unicorns and MDQubesat-1 by Miota Space (weirdly different to the previously announced MDQUBESAT-2 by Innova Space)