well I don't know what you say until I read it, so how do I know not to read it ?
Now I know - and will heed your advice
On a more serious and constructive (LOOK ! CONSTRUCTIVE !) note, I don't see why DJI cant put a logging mode in the firmware where data is logged to ...say... the camera card. I guess flytrex data might be helpful is seeing any precursors to flyaway - but there are just so mahny causes, most of which you cant /see/ - that cell phone tower during especially good propagation conditions. Solar activity (ok you can see that before you fly, if you want). Dumping/logging data structures and decision loop exits might be useful - and with 32GB on board, I don't see why it wouldn't be a possibility - of course there are needed machine cycles taken to do the logging/debug, but hell - its not that bad. Perhaps an instrumented firmware version, with logging for different facilities that can be turned on or off...
Now I know - and will heed your advice

On a more serious and constructive (LOOK ! CONSTRUCTIVE !) note, I don't see why DJI cant put a logging mode in the firmware where data is logged to ...say... the camera card. I guess flytrex data might be helpful is seeing any precursors to flyaway - but there are just so mahny causes, most of which you cant /see/ - that cell phone tower during especially good propagation conditions. Solar activity (ok you can see that before you fly, if you want). Dumping/logging data structures and decision loop exits might be useful - and with 32GB on board, I don't see why it wouldn't be a possibility - of course there are needed machine cycles taken to do the logging/debug, but hell - its not that bad. Perhaps an instrumented firmware version, with logging for different facilities that can be turned on or off...