Data mark

[swatson999]

While looking at plots in Savvy Analysis to try to correlate my XPDR failure with anything (at all), it occurred to me that a nice feature to have would be a "data mark" capability...some way to insert a mark or indication in the data manually to tag events rather than having to rely on either written notes or guesses at times.

Wouldn't have to be complex...even a single "mark" flag in a field would work...0 usually, 1 for a mark (or > 0 for subsequent marks) would work.

 

[dabear]

You could create that using a switch on GP input. It would show up in your user data. On (grounded), off not.

At least I believe that would work, I'm gong to try in later in April.

 

[dynonsupport]

The transponder failure will show up in the data log by itself, so you don't need a mark for this. The problem is that Savvy Analysis only show you a few of the 100+ things we record. So you wont be able to see when this happens. So even if we added "mark", you wouldn't see that either. Did you know the datalog even stores your current CDI deflection, the force the autopilot servos are exerting, and the position of your controls?

If you open the file in Excel or another spreadsheet, you can look at the transponder status.

As Bear says, you can hook a button to a GP input on the EMS. This will cause that input to either be 0V or 5V, which can be graphed against in some tools (Again, not Savvy Analysis).

We've considered a "mark" button somewhere in SkyView but haven't had a lot of customer requests, plus we don't have a great place in the button structure to put it.

 

[swatson999]

Yep, I looked at the data in Excel...big file . I was impressed with the myriad of data fields you're outputting.

Oh, and yeah, I see where the transponder went off-line (basically dropped out of the data entirely, leaving blank cells in the spreadsheet until it was reset).