|
From: Curtis L. O. <cu...@fl...> - 2001-08-31 20:54:37
|
I don't know if this is helpful, but here is what I have in the
comments of options.cxx:
// Parse I/O channel option
//
// Format is "--protocol=medium,direction,hz,medium_options,..."
//
// protocol = { native, nmea, garmin, fgfs, rul, pve, etc. }
// medium = { serial, socket, file, etc. }
// direction = { in, out, bi }
// hz = number of times to process channel per second (floating
// point values are ok.
//
// Serial example "--nmea=serial,dir,hz,device,baud" where
//
// device = OS device name of serial line to be open()'ed
// baud = {300, 1200, 2400, ..., 230400}
//
// Socket exacmple "--native=socket,dir,hz,machine,port,style" where
//
// machine = machine name or ip address if client (leave empty if server)
// port = port, leave empty to let system choose
// style = tcp or udp
//
// File example "--garmin=file,dir,hz,filename" where
//
// filename = file system file name
Also, have a look at docs-mini/README.IO
Regards,
Curt.
Cameron Moore writes:
> First, thanks Tony and John for your comments. I've uploaded new
> versions of the man pages to my WTLUG space[1].
>
> Here are the changes to fgfs.1.in:
>
> Added more files to the FILES section
> Fixed --atlas, --garmin, --native, --nmea, --props, --pve, --ray, --rul
> Fixed --vc, --mach
> Changed AUTHORS section
> Fixed --native-ctrls
>
> The only change to fgjs.1.in is the AUTHORS section.
>
> I don't explain what "medium,direction,hz,options,..." means only
> because I can't decide how to do it. :-/ Let me know if you have any
> comments or suggestions. Thanks
>
> [1] http://wtlug.org/~hrothgar/fgfs/manpages/
> --
> Cameron Moore
>
> _______________________________________________
> Flightgear-devel mailing list
> Fli...@li...
> http://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
Curtis Olson Human Factors Research Lab FlightGear Project
Twin Cities cu...@hf... cu...@fl...
Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org
|