20,741
edits
Property Tree/Native Protocol Slaving: Difference between revisions
Jump to navigation
Jump to search
Property Tree/Native Protocol Slaving (view source)
Revision as of 18:54, 26 March 2013
, 26 March 2013no edit summary
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
In this case, depending on your command line options, FG can be configured to be a telnet server, an http server, a "dynamics" master/server, or a "dynamics" slave/client, and possibly some combination of all of those simultaneously depending on the context and what you are trying to accomplish. | In this case, depending on your command line options, FG can be configured to be a telnet server, an http server, a "dynamics" master/server, or a "dynamics" slave/client, and possibly some combination of all of those simultaneously depending on the context and what you are trying to accomplish. | ||
<pre> | |||
//*** example to slave one copy of fgfs to another *** | |||
// This instructs the first instance of fgfs to send UDP packets in the native format to a machine called seattle.com on port 5500. | |||
fgfs1: --native=socket,out,30,seattle.com,5500,udp | |||
// The second instance of fgfs will accept UDP packets (from anywhere) on port 5500. | |||
// Note the additional --fdm=external option which tells the second instance of fgfs to not run the normal flight model, | |||
// but instead set the FDM values based on an external source (the network in this case.) | |||
fgfs2: --native=socket,in,30,toulouse.net,5500,udp --fdm=external | |||
</pre> | |||