I personally have never tested the generic protocol over a serial port on
windows. I'm not sure I have tested any IO over a serial port on windows
since the very early days of the project back when we were building with
cygwin. I do recall at the time being (this is maybe 10 years ago at
least?) being confused between using COM1 vs. COM1: (with a colon at the
end.) I honestly don't remember which one worked and which one didn't.
Have you tried it both ways?
Personally I run Linux 99% of the time, so anything I've done with serial
ports and FlightGear (in recent memory) has been under Linux.
Perhaps you could also try sending nmea out instead of the generic protocol
to see if that work?
Maybe someone here or on the forum has done serial port coms with windows
recently and can speak up???
For what it's worth, my UAV autopilot has an ethernet interface so I've been
doing my HIL sensor/control surface interface through the network ...
Regards,
Curt.
2011/8/3 Derrick Washington <[email protected]>
> ---------- Forwarded message ----------
> From: "Derrick Washington" <[email protected]>
> Date: Aug 2, 2011 12:49 AM
> Subject: Generic Protocol Error --> Error opening serial device "COM27" The
> system cannot find the file specified.
> To: <[email protected]>
>
>
> Hi Curt
>
> I have been trying for a few weeks now to get FG to transmit data to a
> serial port COM27 via the generic protocol, and for some reason unknown to
> me the simulator simply will not comply. I have several other programs
> which use this port with out a problem, I am using a usb to serial cable
> "GigaWare" I'm not sure what exactly is going on but I really could use
> some developer insight on this one. I had planned to use FG as a the
> simulation platform for my autopilot design. I have the hardware and
> software already to go, just need to get FG talking to the serial port.
>
>
> 3 - 'C:\Program Files\FlightGear\terrasync'
> C:\Program Files\FlightGear\bin\Win32\terrasync.exe -S -d "C:\Program
> Files\Flig
> htGear\terrasync" -p 5500
> Airports/K ... Error opening serial device "COM27" The system cannot find
> the file specified.
> Error opening device: COM27
> Error opening channel communication layer.
> I/O Channel config failed.
>
>
> C:\Program Files\FlightGear\bin\Win32\fgfs.exe
> --fg-root=C:\Program Files\FlightGear\data
> --fg-scenery=C:\Program Files\FlightGear\data\Scenery;C:\Program
> Files\FlightGear\scenery;C:\Program Files\FlightGear\terrasync
> --airport=KMDW
> --runway=13L
> --aircraft=f-14b
> --control=joystick
> --enable-random-objects
> --enable-ai-models
> --enable-clouds3d
> --fog-disable
> --bpp=32
> --texture-filtering=16
> --timeofday=noon
> --atlas=socket,out,5,localhost,5500,udp
> --generic=serial,out,5,COM27,9600,FlightGear_GPO
>
>
> ------------------------------------------------------------------------------
> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> The must-attend event for mobile developers. Connect with experts.
> Get tools for creating Super Apps. See the latest technologies.
> Sessions, hands-on labs, demos & much more. Register early & save!
> http://p.sf.net/sfu/rim-blackberry-1
> _______________________________________________
> Flightgear-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
--
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts.
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
