khorton
New Member
Currently, the official Dynon program to update firmware only runs on Windows. Given that most people run Windows, and it costs money to develop software, this is not surprising. But, there are a number of current and future customers who don't own a computer that has Windows on it.
I request that Dynon release the specs that describe the communciations that occur between the firmware uploader program and the Dynon EFIS and EMS. Then, users could create an open source program that would backup settings, backup current firmware, load new firmware, etc. It shouldn't be rocket science to create a perl or python program that did the communication, and then once it was working on the command line create a GUI for it using Tk, GTK, or wxWidgets, etc. This should work on OS X and Linux laptops, in principle.
The cost to Dynon would be low (the cost to clean up the documentation of the communication specs). The technical risk should be low (assuming the EFIS and EMS run some sort of CRC on the firmware to check for corruption). The usefulness to users would be high. Dynon gets more sales to Mac and Linux users Everybody wins.
I request that Dynon release the specs that describe the communciations that occur between the firmware uploader program and the Dynon EFIS and EMS. Then, users could create an open source program that would backup settings, backup current firmware, load new firmware, etc. It shouldn't be rocket science to create a perl or python program that did the communication, and then once it was working on the command line create a GUI for it using Tk, GTK, or wxWidgets, etc. This should work on OS X and Linux laptops, in principle.
The cost to Dynon would be low (the cost to clean up the documentation of the communication specs). The technical risk should be low (assuming the EFIS and EMS run some sort of CRC on the firmware to check for corruption). The usefulness to users would be high. Dynon gets more sales to Mac and Linux users Everybody wins.