20,741
edits
Generic protocol: Difference between revisions
Jump to navigation
Jump to search
→Serial I/O: https://www.mail-archive.com/flightgear-devel%40lists.sourceforge.net/msg33451.html
m (→Serial I/O: https://www.mail-archive.com/flightgear-devel%40lists.sourceforge.net/msg33373.html) |
(→Serial I/O: https://www.mail-archive.com/flightgear-devel%40lists.sourceforge.net/msg33451.html) |
||
| Line 244: | Line 244: | ||
{{Note|Windows:To specify a COM port number greater than 9, use the following syntax: "\\.\COM10". This syntax works for all port numbers and hardware that allows COM port numbers to be specified.}} | {{Note|Windows:To specify a COM port number greater than 9, use the following syntax: "\\.\COM10". This syntax works for all port numbers and hardware that allows COM port numbers to be specified.}} | ||
it doesn't appear that the "generic" interface code | |||
is setup to transmit and receive at the same time. You can't open up the | |||
same device twice, so you two command line options won't work either. As | |||
far as I can tell this will require some code modifications if you want to | |||
use direct serial communcation. | |||
Another option might be to write a thin glue layer that talks to FlightGear | |||
over the network, and talks to your hardware over a serial port and then | |||
does all the appropriate data translation as required. | |||
== Examples == | == Examples == | ||