Pardon me for asking, but what do you need all this logging for? i.e. for what purpose?
Trev
Maybe it’s just me, but I like to know what’s going on with my engine. I also believe in predictive maintenance and learning of a potential problem before it becomes a real problem.
I used to have a Blue Mountain EFIS-One and I downloaded the log file after every single flight. I would always load it into Excel and make a quick graph of pressures, temperatures, volts and amps. I found unusual things going on more than once. It only took a few minutes to do this.
I also used data graphs to troubleshoot and tune engine cooling problems. It was important to know OAT, climb rate, power settings, fuel flow and density altitude to do this. The flight data has to be logged at the same time as the engine data so you can correlate the different readings. Seeing a change in CHT is not very useful unless you know that you initiated a climb or just leaned you engine. It’s the only way to really know what’s going on.
I would also use the GPS and altitude data to record memorable trips and analyze my pattern work. I loaded the data into Google Earth to see my flight path. These are just a few of the many advantages you can get out of logged data.
Here’s a picture of a flight to Chicago I took a few years ago.
This system will not allow me to upload a picture for some reason, so here are a few links to some screen shots I made…
http://www.flickr.com/photos/50445804@N05/6535317889/in/set-72157628478132683
http://www.flickr.com/photos/50445804@N05/6535291897/in/set-72157628478132683/
http://www.flickr.com/photos/50445804@N05/6535324379/in/set-72157628478132683/
http://www.flickr.com/photos/50445804@N05/6535291245/in/set-72157628478132683/