Thank you Jan for the TLE! We are seeing some deviations with this TLE and calculated a new one based on station 2410 - GAO UHF observatios. It seems to be a very good fit and we already used it for our passes:
InnoCube
1 98709U 25029.51021302 .00000000 00000-0 10880-2 0 07
2 98709 97.4389 111.9013 0007295 359.8410 120.5456 15.16575659 07
HYDRA-T TLE Update
HYDRA-T
1 98655U 25009BY 25036.56259560 .00000000 00000-0 33749-2 0 04
2 98655 97.4429 118.7979 0003354 352.9277 122.4398 15.17701918 01
HADES-R TLE Update
HADES-R
1 98710U 25009BY 25036.56316744 .00000000 00000-0 -14212-2 0 09
2 98710 97.4429 118.6121 0003354 352.9277 121.3443 15.17285902 00
Checked against one of my latest obs and these TLE are ok.
Hi Jan!
Here is a Ikhnos Plot from one of the last observations with high elevation (11042298). Am I interpreting the tool wrongly? We donβt have much experience with tle creation. The waterfall uses the current satnogs tle, ikhnos our tle.
Cheers
Tom
That looks spot on, these will be useful for the coming days.
While Iβve added your TLE set in DB and as you noticed with ikhnos it fits better the observations, Network didnβt use it as the epoch of the TLE is older than the one of @PE0SAT.
Iβve propagated below yours to a later epoch, this will fit better than the current but it will may need some extra fit. This extra fit I could try to make it later today.
Innocube
1 98709U 25033.48444098 .00000000 00000-0 00000-0 0 00
2 98709 97.4389 115.7996 0007960 328.6771 237.0910 15.16744923 03
Regarding HYDRA-T, I have analyzed the short recording that @PE0SAT shared earlier in this thread and realized that it uses the same modulation, coding and telemetry format as HADES-R. More info in this blog post. The AMSAT-EA telemetry parser will refuse to parse HYDRA-T packets because it checks the satellite ID, but this check can be commented out to obtain a valid parse. As with other commercial satellites transmitting in amateur spectrum, please use this information responsibly.
Thank you Dani @EA4GPZ !
Bob
Thanks for the info about the epoch. I used strf and found the option to reset the epoch. We used this TLE for our current pass and it worked fine:
InnoCube
1 98709U 25037.42998394 .00000000 00000-0 52834-2 0 05
2 98709 97.4389 118.9698 0007295 359.8410 136.6045 15.16981986 09
Hi @laith_me,
Iβm the operator of Waratah Seed-1, launched on Transporter 11 last year. Weβre seeing a signal on 400.65 MHz that correlates to your orbit. Can you confirm you are also transmitting on 400.65MHz?
I tried Danielβs decoder, but no decoded frame came out, only
correlate_access_code_tag_bb :debug: Access code: bf35
correlate_access_code_tag_bb :debug: Mask: ffff
correlate_access_code_tag_bb :debug: writing tag at sample 1080
Daniel,
Some tools and an example here including modified HADES-R decoder.
Step 1 - Collect IQ (example IQ in folder; 50K sps) using your desired grc.
Step 2- Run through grc in folder to obtain frame. Will have to adjust BFO to obtain frame. HydraT.grc. (Use Hades-R satyaml file found in in updated gr-satellites)
Step 3 - change resulting frame to all UPPER CASE
3A 14 35 15 00 14 35 15 00 01 00 FF 0A 00 05 10 00 01 00 00 FF FF FF FF FF FF 00
Step 4 - run txt file containing frame through decoder (see example photo)
β¦ did it, thanks.
Hi all,
I am looking for some updated TLEs for some objects on this launch, namely Lyra-1, Centauri-7,8 and Winnebago-2. Turning to this forum due to lack of tracking on open source platforms. Not sure if this is an appropriate forum, so apologies in advance!
Thank you and appreciate the work this community does.
Welcome,
I can have a look with my STRF monitoring,
Please share details on frequencies and type of transmission.
Jan - PE0SAT
Hi Jan,
Appreciate your response - the details I have are from transmitters listed on the SatNOGS DB, so confidence is low.
Winnebago-2 - S-Band Tx 2272.5MHz
Centauri-7 - UHF 400.22MHz
Centauri-8 - UHF 400.22MHz
Lyra-1 - Potential 401.2MHz, based on previous launches by the operator.
I appreciate this is a long shot so any results are greatly appreciated.
Jack
