if only it put that data into expedition on the fly...

I would like to be able to log which sail is in use and have that show up in the log file....but do it in a way where any sailor could do it, so no setting an event, or using a web page to pick the sail...you know something a SAILOR could use. For a while, I had built a web server which sent out XDR sentences and I stored then in one of the user fields. Nobody but me used it so I'm onto using physical buttons that the pit person can press after the drop. Now that you understand my problem, here's my question: What's the best data structure to use to get it into expedition? I see the log fields like Solent,J1,J2,reacher etc which seem like the right place to set an "active" flag, OR should I just keep using the User fields through NMEA0183? The only limitation is that the data would be coming in serial. Of course IF the answer is that I should use those fields, what does the inbound data look like? (could I use the expedition format for example?)  Any guidance would be appreciated.
 

you would think it would be that easy, but...... 
The fields that they pass the data in are basically "comments" and then VIRB edit decodes them. Problem has been that I can not find any documentation on this, so I bought a used 360 and connected it to a garmin chartplotter at my local marine store to make a FIT file with all the data in it. So now I have a FIT file full of marine data, Hopefully I'm good enough to create one just like it from exp logs, as we won't have a garmin chartplotter onboard. 
 

I cleared the ENC database and the issue went away. Thanks!

that's why its a new "feature" ..The actual track and data is irrelevant, just the fact that there is data is all that matters.