Ticket #460 (closed enhancement: wontfix)
Customizing fireing event from nmea..
|Reported by:||Jantar||Owned by:|
What about an additional type of input for events?
What if XCSoar could react on certain nmea-sentences? (I know it does, but also in a customizable way)
Imagine you are climbing a thermal and is about to leave in half a turn,
you flip the climb/netto switch on the stick, and XCSoar immediately goes from climb to cruse mode.(Your Flight-computer sends its mode on nmea).
Or, imagine you have a remote, on your stick or somewhere else, some switches and perhaps a turntable knob, capable of controlling most aspects of XCSoar, enabling you to run the software on devices with no touch-screen..
I'm thinking about building a small device, using a pic, to be placed on the serial data-cable, reading the data fed and appending some nmea-data reflection the state of some hardware... switches dials etc.. ..
I don't know how this feature is to be implemented, one approach of course is to use a special nmes-sentence, something like "$XCSOAR,1... " however this comes with a big disadvantage, Glide computers might send data about the "state"
Another way is to use regular-expressions on nmea input data, this would be
very configurable, but I think this might be too cpu-consuming and hence not a smart thing to do..
Anyway, what I have in mind, what I would like to see, is an option to
customise the way an nmea-source can trigger events.
mode=default type=nmea data=XCSOAR,141 event=StatusMessage Dropped marker event=MarkLocation