Howto:Port I/O from Nasal: Difference between revisions

Jump to navigation Jump to search
m
Line 23: Line 23:
</syntaxhighlight>
</syntaxhighlight>


Obviously, you need a matching [[Generic Protocol]] that picks up the corresponding properties, marshals them into the required format and sends them to their destination.
Obviously, you need a matching [[Generic Protocol]] that picks up the corresponding properties, marshals them into the required format and sends them to their destination. The connection details are entirely handled by FlightGear, so they need to be specified during start up time.


Setting up and using a [[Generic Protocol]] is very easy, just a simple XML file defining the property values you want to send and/or receive...with optional formatting. FlightGear can then use this protocol with various end points from simple logging to file, across the network, directly to/from a serial device, etc...via a simple command line option.
Setting up and using a [[Generic Protocol]] is very easy, just a simple XML file defining the property values you want to send and/or receive...with optional formatting. FlightGear can then use this protocol with various end points from simple logging to file, across the network, directly to/from a serial device, etc...via a simple command line option.

Navigation menu