On Feb 13, 2008 2:59 PM, dave perry wrote:
> I have the thread from 2006-08-26 between Curt Olson and Frederic
> Bouvier on this subject. The connection to the 496 is via a db-9 to
> super small usb cable I got from garmin as suggested in the garmin
> user's guide. From a dmesg, I expect that com1 is /dev/ttyS0 on my f7
> system. I use the following option when launching fgfs:
>
> --AV400=serial,out,5,/dev/ttyS0,9600
>
> and I have the garmin in Simulation, Aviation modes and Interface serial
> Data Format is Aviation In (before I launch fgfs).
>
> When I launch fgfs, I get
> Cannot open /dev/ttyS0 for serial I/O
> Error opening device: /dev/ttyS0
> Error opening channel communication layer.
> I/O Channel config failed.
> Segmentation fault
>
> These are the lines from a grep of the dmesg.
> Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
> serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
>
> which makes me think that com1 corresponds to /dev/ttyS0 and com2
> corresponds to /dev/ttyS1.
>
> I also tried under WinXP with com1 replacing /dev/ttyS0 and
> C:\> mode com1 data=8 parity=n
> per the thread. fgfs did ran with no errors but the gps did not respond.
>
> Any suggestions? I would really like to use fgfs to get me familar with
> the gps before I am in the clouds and being vectored by Denver center.
>
First thing I would check would be the permissions on the serial ports. You
may need to add yourself to the uucp group for instance in order to be able
to use them.
Regards,
Curt.
--
Curtis Olson: http://baron.flightgear.org/~curt/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
