Add wireless deployment of charges either for deployment testing or flight termination.
Modify software for SPICA/RIGEL.
Consider doing light encryption of detonate signal (e.g. not plain text that says "detonate", other people use LoRa)
Newest Idea:
When configuring the flash (setting up file lookup table, before the flight program is loaded), load a "flight termination" string for each deployment channel. The ground receiver / ground station should be aware of these preprogrammed codes so they can send them to the flight computer wirelessly.
The string will need to be sent with a special character following it that is guaranteed to not be in the flight termination string, maybe a newline? This way the ISR on the flight computer knows when it has a full buffer to parse. When the flight computer receives the termination string it blows that channel. Consider adding more flight strings representing groups of deployment channels, e.g. a string for both main charges, a string for all charges, etc.
Could also have a single flight termination string that blows everything in a specific order determined by the flight computer and use separate commands for ground testing that incorporate sending a bit mask of which channels to blow. Something like [deployment test string | one byte mask ]. The one byte mask could support 8 distinct channels.
It may be best to let the flight computer decide how and when it wants to blow charges. It may check continuity, blow charges based on altitude, blow everything at once, delay blowing charge caps on the same side, etc.
These decisions could also be left up to the user on the ground sending the command.
The termination strings should be stored in a data file somewhere in the ground software, or just entered by the user?