Open mahtin opened 3 years ago
Thanks Martin,
We have fixed the NORAD numbers on the autotune function and updated all the old packets on the database.
Here you have the decoder from Max Holliday: https://github.com/maholli/VR3X-decoder/blob/main/gs_parse_standalone.py
VR3X-A Littlefoot start with --> 33 3A VR3X-B Petrie start with --> 33 3B VR3X-C Cera start with --> 33 3C
The information coming from planet4589 doesn't look accurate, in any case as all the sat share the same radio configuration, the decoder use the second byte to properly identify each satellite.
Please note that VR3X-A entries in the packets API still returns 0
(vs. 47463
). It once did return values correctly. Sadly, that regressed backwards.
Packets have
0
in thenorad
field for VR3X-A (and maybe B & C?). Hence this search for valid numbers ...So they are
47463
,47467
, and47524
. However, I'm wondering if the1
,2
, and3
areA
,B
, andC
orC
,B
, andA
. (see https://tinygs.com/satellites).Sadly (once again) Celestrack does not have the names of the satellites added. ...
BTW: Why VR3X-A on TinyGS vs V-R3X-A? Inquiring minds want to know.
(Update) I see that the
norad
number is correctly listed on https://tinygs.com/satellite/VR3X-A (and -B, -C) pages; however, that isn't reflected in the packet data. But that does not fully confirm the correct order of A, B, and C.