@rblevy appreciate the information.
It frankly leaves me uncomfortable. A crew having to shut down an airplane and let it sit for 5 to 30 minutes to achieve a reboot? That simply does not seem to enhance safety. Anything from weather windows, air traffic density, and more can change in 30 minutes, not to mention the get there pressure.
I would like to better understand the approach the aviation industry is taking towards complex software systems, and also software human factors considerations. As a former software developer, I spent my early career writing software, and was later responsible for large high reliability projects with extensive bug lists, associated CMS and MMS systems, and too many instances where despite us, fixing one bug caused another.
Now, I try to keep up with my iPhone. (This includes its surprising loss of its passcode last year - which despite all the claims of security, was met with a shrug by Apple!)
I fly mostly 1960s era airplanes. I work to help our community fly safe.
The large number of near misses from issues with avionics upgrades led us to set up a meeting with a wonderful and knowledgeable former avionics shop manager, now at a local FSDO. The FAA is finally making reporting of these kinds of avionics unsafe situations mandatory.
Russ, thanks for the efforts to keep us all informed. I don’t know about others, but would appreciate any news you come across on issues with software systems and especially human factors related to software systems. Too many accidents or near accidents in big airplanes seem to me to be related to non-pilot decision making on the software side.