Performance Snapshot

[Mark_Dickens]

Allow the recording of performance parameters at an instant in time by pressing a button. Each snapshot file (csv) would consist of one data line (and a header line) and include all of the fields normally included in the logs. This capability would allow the pilot to instantly record performance for the purposes of calibrating airspeed, performing engine leaning tests, etc and would eliminate the need to try and write down (or scroll through multitudes of log data to get to) a data point.

 

[Raymo]

Mark,

I like this idea too. It would help when sending logs off to AFP to get the right injector restrictors to aid in LOP operations.

 

[dynonsupport]

As an idea that doesn't require new software from Dynon, if what you are looking for is data that is on the screen (which I assume it is because you mentioned writing it down), you can use the screenshot function for this. Buttons 2&7 at the same time save an image to a USB drive if connected, with a timestamp. Seems like that might work just as well as a single line CSV with just lots of columns of data.

 

[Mark_Dickens]

Mark,

I like this idea too. It would help when sending logs off to AFP to get the right injector restrictors to aid in LOP operations.

That's one good use of the info for sure and one that occurred to me while we were at the class. I also think it would come in handy if you saw something odd happening and didn't have a USB drive handy to snap screen shots.

 

[Raymo]

I remembered the screen-shot capability after posting and I almost always keep a thumb drive attached to my left screen. It would work for my needs when retrieving data to tune injectors. Just need to put a sticky on my panel so I remember the buttons to push. 

 

[gtae07]

I guess the other alternative would be the ability to put an "event marker" in the data file, triggered off a button press.

Does the log give you the ability to record open-closed sensor states? E.g. some builders have a "canopy unlocked" or "wing pins" widget on the EMS page; could you wire up a momentary pushbutton to an input and just have that state in the data file? Then you could just search for lines where the input is closed...

 

[Dynon]

Yes, that's basically what people do. Set up a contact input on an otherwised-unused pin. Hook up to a momentary switch, and then use the state change that happens when it's open vs closed.

 

[airguy]

Yes, that's basically what people do. Set up a contact input on an otherwised-unused pin. Hook up to a momentary switch, and then use the state change that happens when it's open vs closed.

Or even a pin that is infrequently used or changed during flight. I use my Pitot Heat talkback for an event marker, that gets logged in the data file.