Regarding Observation 14944223 …
something seems to be wrong with the TLE
stefan/oe6isp
This is just an effect of two different TLEs, the first one was used during scheduling and defined the start and end time of the observation. In between scheduling and actual observation there was a TLE update in SatNOGS DB which was pulled by the station in the beginning of the pass. This TLE drastically changed to the first TLE and therefore the new azimuth/elevation path and Doppler correction is much different from what was intended to be scheduled.
1 Like
Thanks for your answer. I took this into Account, deleted the observation and re-scheduled, but the trajectory was different, but still strange. When you look at the recently submitted #14942074, there is no trajectory at all. Some others looking ok. So still open questions.
Stefan/oe6isp
1 Like
When SatNOGS Network - Observation 14942074 was scheduled?
There were 3 significant changes in TLEs the last 48hours, so it may be affected by that.
From the future passes in the station page that use the current TLE set, it looks like that at this time there isn’t any pass, there is one at 20:00 - 20:11 and one at 21:34 - 21:46.
So, it seems that you need for one more time to delete and re-schedule the observation.
Thanks Fredy, I will do!
I know this tle-challenge after deployment very well.
2 Likes
It seems, there is a signal now from STS-1 - 6KHz low, but looking reasonable.
1 Like
Thanks for sharing this information, going over my STRF run at that specific time over Europe, this seems to be HUNITY-1
The search continues.
Jan | PE0SAT
2 Likes
Mny thx for quick analysis!
stefan/Oe6isp
1 Like
STS-1 team just confirmed, there is no signal. Most likely battery empty because spent too much time in the deployment-container.
Stefan/OE6ISP
2 Likes
Thanks Stefan,
A well known challenge, lets hope she will recover.
Jan | PE0SAT
3 Likes