In conjunction with that FlightGear has had support for a generic ASCII only input-output protocol handler for a number of years now. It is called 'generic' because it allows handling of just about any information in any form by altering a user modifiable xml configuration file. The functionality has been extended further by the possibility to define an offset and a multiplication factor. This approach might not cover every possible scenario but it will probably be good enough for most cases.
With the help of Anders Gidenstam the generic protocol has recently been extended to also support binary input and output. The data will be tightly
acked in a packet that contains the requested data described in the configuration file. Supported types are: boolean values (8-bit), integer values (32-bit), floating point values (32-bit) and double precision floating point values (64-bit). Andes also added the option to support network byte ordering (big-endian) or system native byte-ordering which will save some processing time when only one type of system is used. To make it easier to see how the packet will be handled by FlightGear a utility called generic-protocol-analyze has been created which can be found in FlightGear/utils/xmlgrep. It outputs the data offset and size along with it's description.
==New Wiki Articles ==