Update on this - I’ve since fully reverse-engineered the FUNcube Whole-Orbit telemetry format (with the official FUNcube Nayif-1 Dashboard as reference, decompiled, and validated against 70,368 real records from SatNOGS-archived frames). Since JY1Sat carries the same FUNcube payload and uses the same protocol (ext-id byte 0x10 vs Nayif-1’s 0x08), the same 25-byte WO record format should apply to JY1Sat:
-
Verified 25-byte WO layout + reassembly + conversions: https://github.com/mod-linux/nayif1-wo-decoder
-
gr-satellites tracking issue (23-byte → 25-byte fix, wrong HR parser): https://github.com/daniestevez/gr-satellites/issues/845
-
Full writeup in a separate post: Verified Whole-Orbit telemetry format for Nayif-1 (FUNCube) — 25-byte records, decoded from official Dashboard + 70k real records
One thing that stands out for JY1Sat specifically: its SSDV frames at ft 32/33 are still reported as “unknown frame type” by gr-satellites, so the 6-bit frame-type enum for JY1Sat is incomplete. If anyone here (@bali) has JY1Sat telemetry documentation or WO/SSDV archives, I’d love to confirm the 25-byte layout carries over and define those frames properly.
Thank you!
73!