According to the flightgear wiki, I see that Telnet Connection is now deprecated?
I'm trying to use Flightgear as a visualizer for a *pre-existing* instance of JSBSim that's outputting Mavlink Packets (to MavProxy as part of the Ardupilot SITL stack). I've written a program that properly parses the Mavlink into Flightgear and is ready to send it to a localhost port, but can never seem to get the right Flightgear commandline parameters in order to actually launch flightgear with no FDM and update it exclusively through the property set commands.
This is my command line so far:
fgfs ^ --native-fdm=socket,in,10,,5505,udp ^--telnet=5501 ^ --fdm=jsb ^ --aircraft=Rascal110-JSBSim ^ --fg-aircraft=%AUTOTESTDIR% ^ --disable-anti-alias-hud ^ --disable-hud-3d ^ --disable-horizon-effect ^ --timeofday=noon ^ --disable-sound ^ --disable-fullscreen ^ --disable-random-objects ^ --disable-ai-models ^ --fog-disable ^ --disable-specular-highlight ^ --disable-anti-alias-hud ^ --wind=0@0 ^pause
Most of the time flightgear will start and allow connections over the 5505 port (according to netstat). But netstat shows no opening on 5501. Connections will happen on 5505, but no flight properties will be set.
One alternative that I've tried with no success is to start flightgear with the "MavLink" protocol and connect it directly to my local pre-existing JSBSim instance (which again, is outputting Mavlink for MavProxy). However, I have not gotten that to work either.
Since the wiki is kind of lacking on this sort of interface, I'm not really sure whether I should persue if my Telnet isn't working or if Telnet is deprecated and I should be focusing on some other aspect of my command line parameters.
Anybody have any tips?