On Wednesday 20 Apr 2005 1:48 pm IST, Erik Hofman wrote: > > 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).
Oops! My apologies. I had not noticed this. > > 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. I have not tried the serial port yet but soon i am going to build hardware to interface over the serial port. I am wondering how the system can read the port at predefined intervals of time when my external hardware is not perfectly synchronized in time with my PC? Is the data buffered and the buffer accessed at the frequency specified by us? Where can i get more info on serial port communication and i see not other setup for the serial port except for baudrate. This is sufficient as other parameters are more or less standardized 8N1, yet i would like to know more on serial port communication. > > 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. About this, i just tried logging my data to a file; just the minimum set of data (6-DOF) at 4 hz and then used it as input for playback. This went on fine. As expected the system was jerky (4 Hz only) but followed path. It failed if "--fdm=external" was not specified. It would still follow the path but only on ground and refused to take off. I understand this as it cannot take off at apparent zero velocity but i was hoping that it would make the sim a little smoother even at 4 hz update rate. Alas! -- Cheers! Kitts _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
