Curtis L. Olson wrote:
Have a look at docs-mini/README.IO for starters. You can pass control inputs into FlightGear by creating an FGNetCTRLS (src/Network/net_ctrls.hxx) packet and sending it over to FlightGear. You can then have FlightGear send back an FGNetFDM packet (src/Network/net_fdm.hxx) which will include all the position, velocity, orientation type data. Yes, you'll eventually have to create a model of your airplane, but you can certainly iron out all the interface issues while using an existing aircraft model. I don't know how well our FDM engines scale to R/C or UAV scales, but I'd think with some fiddling around you could get something to work. I'm an R/C pilot myself, and involved in a UAV project here at the University of Minnesota, so I'll be interested to hear what you come up with.
Regards,
Curt.
That is helpful. Somehow I missed that file. I have gotten the generic ASCII interface working enough to pass data back and forth. Is there any reason to switch to the binary format (CTRLS and FDM) now that I'm already started on the generic?
One issue I'm curious about: It seems that the IO system will only read one message per period (as specified in the packet rate option). So, if I send the messages just a little too fast, a delay will keep building up indefinitely? Is this true with all the IO interfaces?
-Jeff
_______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
