Hi All
Regarding the logging options, these are _really_ there for developer assistance, but I guess they are useful to others.
There is a big gaping hole regarding documentation of the software when running, that is a big TODO on my part.
Ian Fallon has done a great job of documenting the installation procedure, and once the software starts to settle from the current churn, I will set about documenting.
Regarding storage of data, this is something I have been thinking about, but let me describe the potential issue here.
I configure the disk of PilotAware to be in a non-persistant (safemode) state, there is a very good reason for this, a will known issue with SD cards, if you pull the power without having flushed the filesystem correctly, then you can trash the disk, and make it unusable.
This is VERY undesirable, and hence the design decision above to use safemode.
However, I can see the requirement for being able to record information persistantly, and I am thinking of two potential solutions here:-
1. Have an option in the web interface to instantaneously save the recorded flight data, effectively this would put the disk into a mode which can be written, save the flight data, then flip back to safemode.
2. Have an option on the web interface to 'download' the flight data to another device, tablet, PC etc, the downside to this, you MUST ensure PAW is powered until this option is complete. This could work with (1) above.
Thx
Lee