Communication time-out for more robust experience

[varosi]

I hit a bug in Dynon D10A (5.1.1.206).
Steps to reproduce:
1. Connect Dynon to PC via RS232
2. Run Dynon software on the PC (on Windows 10)
3. Power on Dynon
4. Start reading process of firmware of EFIS
5. Crash (exception) happen in the middle of firmware READ process
6. EFIS freezed on it's yellow communication screen begging the user not to power-off.
7. After power off - unit frozen on Blue screen

First, if there was a time-out in Dynon unit, it will just disconnect and recover to normal operating mode. (communication with a PC that is not answering more than 10-20 seconds should be considered freezed/crashed) Second, why read operation may fail the unit? Read operations should never fail anything.

 

[Dynon]

When you're in the yellow screen, you're in a bootloader mode. Detecting communications issues in that mode aren't possible with the EFIS-D10A's architecture. If we were redesigning that EFIS today, we'd do certain things differently to make these sorts of operations as robust as they possibly can be. SkyView, for example, has lots of self-recovery capabilities.

All of that said, which exact operation were you performing at the time? A full firmware backup?