Howdy Fellas'
I am a newbie to FlightGear and am impressed by its performance. My greetings to all the developers and everyone associated with the projects development.
I have a few queries about the generic I/O protocol. A quick Google search informed be that the protocol can now take input as well (the readme file of my installation still mentions output only). This is
Eh, you might be right.
Keep in mind that the <format> tag is ignored for input, the value is just converted to <type>.
wonderful news but how can the same protocol work as both input and output (dir = bi) simultaneously? Is it possible to mention in the XML file as to which chunks are meant for output and which chunks are input? Else what sense would it make to take input and give an output of the same thing?
You have to specify the input chunks within an <input></input> section and the output chunks within an <output></output> section (this is also done in the playback.xml configuration file located in FlightGear/data/Protocol).
Currently i wish to have some property values outputted out of the serial port and have some other property values inputted through the same serial port. How do i do that? Have two separate protocol files and configure them as in and out respectivesly to work over the same serial port?
Hmm, I never had that in mind. I don't think that would be possible, at least not in an interactive way. The generic protocol just sends data to the output port at regular intervals or reads data from the input port at regular intervals.
Another thing i would like to know is what are the minimal set of data i need to provide to allow me to define the state of the aircraft (these are my input values). Currently i can only input 6DOF (lat, lon, alt, roll, pitch, heading/yaw). Will this set of minimal input be sufficient to simulate the aircraft in GUI?
I don't have an instant answer to this one, it would be nice to have this specified somewhere. To see which properties are available you could take a look at README.properties in the docs-mini directory of the source tree or the Docs directory of the base package. But be warned this is still work in progress and not all properties are listed.
Erik
_______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
