1,089
edits
Generic protocol: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 12: | Line 12: | ||
There is the native_fdm protocol to control FlightGear using an external FDM and there is the generic protocol that uses the XML configuration files. | There is the native_fdm protocol to control FlightGear using an external FDM and there is the generic protocol that uses the XML configuration files. | ||
The ''generic'' communication protocol for FlightGear provides a powerful way of adding a simple ASCII based or binary input/output protocol, just by defining an XML encoded configuration file and placing it in the [[$FG ROOT]]/Protocol/ directory. | The ''generic'' communication protocol for FlightGear provides a powerful way of adding a simple ASCII based or binary input/output protocol, just by defining an XML encoded configuration file and placing it in the <code>[[$FG ROOT]]/Protocol/</code> directory. | ||
The generic protocol can be easily set up for both input and output. And it supports not just a single medium, but can be easily made to use files, FIFOs, sockets etc. The generic protocol is really good for things like exporting to a delimited ASCII file for import into spreadsheet for instance. | The generic protocol can be easily set up for both input and output. And it supports not just a single medium, but can be easily made to use files, FIFOs, sockets etc. The generic protocol is really good for things like exporting to a delimited ASCII file for import into spreadsheet for instance. | ||