Navigation Menu

Skip to content

Releases: jmason86/MinXSS_Beacon_Decoder

Critical update for battery temperature decode

04 Dec 19:07
Compare
Choose a tag to compare

New decode coefficients for the battery temperature.

We built a new battery pack shortly before delivery and had to use a new part number for the temperature sensors which had a different resistance. This update implements the corresponding coefficients to properly interpret that data.

Compatibility with MinXSS-2

13 Nov 16:38
Compare
Choose a tag to compare

Changes

This release includes some minor changes to the telemetry definition to make it compatible with MinXSS-2. The major changes in code have been just to clean it up and add some testing.

Executables

The executables released here (the attached .app and .exe) have been tested on macOS 10.13 and 10.14.1; and on Windows 10 64 bit. At present, Linux users are still required to run the code from source (see the README for instructions).

App Icon

  • Windows: You can find the .ico file here. I think that you have to create a shortcut of the .exe then right click the shortcut > properties > change icon > select the .ico.
  • macOS: The icon is already embedded in the macOS .app.

CRITICAL UPDATE: New place for data uploads to go

31 Jul 22:09
Compare
Choose a tag to compare

This update deprecates a prior temporary method of uploading data to the MinXSS team and introduces a new long term solution. The old method of upload will no longer work, so please update to this newest version of the application or codebase.

Side note: MinXSS-2 is now scheduled for launch no earlier than 2018 February.

Minor patch for X123 enable decode

02 May 15:56
Compare
Choose a tag to compare

Nearly all of those packets that have been saying "X123 Enabled: No" should've been saying "Yes". This impacts the DK3WN decoder as well, so Mike will need to update that to do
AND 0x0002 >> 1, rather than AND 0x0008 >> 3.

First major release in full working order!

27 Apr 03:37
Compare
Choose a tag to compare

The app has now been robustly tested on several different systems when the source code has been run directly in python. The Windows executable has also been tested once to decode a packet. All telemetry decodes properly, can handle a continuous stream of data, remembers your configuration for input and options, and (if you leave the "Forward data" toggle on) will automatically forward the MinXSS team the binary data when you either click the "Complete pass" button or simply exit the application. It's perfectly fine to click the button and exit and upload twice.. it will simply replace the file on the server on exit. This means there is no longer any need to use the dropbox link provided on our website to send data and we'll be taking that down soon.

If you use the attached windows executable rather than running the source in python, make sure to copy the input_parameters.cfg and MinXSS_Beacon_DecoderWin.exe files to the run directory: C:\Users{username}\MinXSS_Beacon_Decoder'. And that's it!

Flip through the tabs in the app and it should be pretty self-explanatory. If not, or if you find problems, just let me know on twitter (@minxsscubesat) or create an issue here on GitHub. Happy decoding!

Can now decode negative numbers as well

25 Apr 05:56
Compare
Choose a tag to compare

All telemetry points should now decode properly. At least they did in my testing using some data forwarded by ham radio operators. Give it a try!

Now handles KISS special characters by default (optional toggle added) and generates binary output file

24 Apr 17:08
Compare
Choose a tag to compare

With some pointers from Mike Rupprecht (DK3WN) and discussion with Tom Woods (MinXSS Principle Investigator), the decoder now handles special characters in the KISS format. The special characters are 0xC0 (frame start/end) and 0xDB (escape character). The KISS format changes these to 0xDB 0xDC and 0xDB 0xDD, respectively. My code now searches for any instances of these replacements, and converts them back to 0xC0 and 0xDB, as appropriate. By default, the code will do this but there is a new toggle in the GUI to disable it.

The code also now generates a binary output file. That is what will be sent to us when you hit "Complete Pass".
Next step will be making that file get sent to us when you exit the program and/or after 5 minutes have elapsed since the last decoded MinXSS beacon.

More robust telemetry identification

19 Apr 18:24
Compare
Choose a tag to compare

Hopefully the code can now better identify packets and thus decode properly.

Basic real-time decoding for macOS and Windows (64 bit)

29 Mar 14:59
Compare
Choose a tag to compare

Basic functionality of decoding now working and compiled. Some notes from K4KDR on working with the Windows executable:

-was unable to establish a TCP connection to the software modem until copying "MinXSS_Beacon_DecoderWin.exe" and "input_properties.cfg" to the 'C:\users{username}\MinXSS_Beacon_Decoder' folder (which had been auto-created by the app when first run from the download location.

-for the app to show the images, the "assets" folder also had to be copied to the 'C:\users{username}\MinXSS_Beacon_Decoder' folder.