All three satellites have different identifiers in the data segment.
I’ll see what we can do regarding decoding the data. Will have to check with the software team to see if we can give you software to do it your self.
Or if you want to try yourself the radio is based of the OpenLST, so we use the depaketiser structure used by that (CC1110 structure). The data is then cobs encoded into a data stream. If you want to try it yourself I can get you a list of which bytes correspond to which value (battery voltage, Sat ID, battery temperatures, etc.)
And I see that there are OpenLST blocks available for GNU Radio at:
… unfortunately, they require GNU Radio version 3.10 (which I don’t have installed). But if someone else wants to give those blocks a try, I would love to hear if they decode the sample file for the Binar sats.
Would be good to have your software to see what we should expect while playing with OpenLST.
And to build a decoder for a dashboard we would also need a list of which bytes correspond to which value and of course to see which byte (or bits) identifies the satellite.
My name is Tristan and I am a Software engineer at Binar.
You are correct on the 9600 baud and the sample rate of 19200. The modulation is GFSK. I should have shared this in the document. The three satellites transmit at 437.7, 437.85 and 437.925 MHz.
Sorry we do not have a decoder ready to share with you as we would need to make some changes to it before we can release it to the amateur community. I will see if I can get it done before deployment but that seems unlikely.
As you can see, the OpenLST board has a Hardware ID at the end of the packet and it is unique to each satellite. For the test data we shared with you, the hardware id at the end of the packet is the 02 01 bytes in position 5th and 6th from the end. We also have our own ID in the data field, the data is cobs encoded, the first 11 bytes will be your satellite identifier when converted into a string. Also in the data field, we have the Callsign message. Callsign starts at byte 22 and it is 38 bytes long.
Hope this helps for now. I will get more information once other priorities have been completed. I will monitor this chat if you have any questions. Hope I can be of more help soon.
