On my Slackware setup I didn't have any troubles but have
to "watch my ports". I don't plug anything in until I login
and the first device, the USB GPS, is /dev/ttyUSB0 and the second is the D72A
on /dev/ttyUSB1. If I run Xastir without the GPS, I have to change the port in
the device setup to /dev/ttyUSB0. One just has to keep track of where the ports
are.
I find the script for the D7 works for the D72 but was wondering if
anyone is considering a different one as I guess there were some
limitations with it?
One of these days I'm going to try plugging in my TNC-X with a generic H/T, D72
or D7A(g) and two USB GPS receivers and try running Xastir in one window and
aprsis32 in another with WINE. Already have full success with aprsis32 running
in one window while connected to the internet and had the D72 working with
Xastir. Next step is to have both running under Rf. :-) What use is it?
Well, I like to track amateur rockets and if there was an occasion
where there were two flights going at once with one on 2m and the other on
70cm, I could track both on the same program or have one in Astir and one in
aprsis32. I've already tracked two different
frequencies on the same instance of Xastir. Both 2m and 70cm trackers where
successfully tracked on the same Xastir map.
Kurt KC9LDH
--- On Sat, 1/8/11, Curt, WE7U <[email protected]> wrote:
> From: Curt, WE7U <[email protected]>
> Subject: Re: [Xastir] TH-D2A xastir com port issue
> To: "Xastir - APRS client software discussion" <[email protected]>
> Date: Saturday, January 8, 2011, 5:49 PM
> On Sun, 9 Jan 2011, Scott Evans
> wrote:
>
> > So get the ID from the usb device by typing lsusb and
> you will get the device/vendor, then modify the text above
> and place the file into the directory quoted above, then
> restart udev plug in the serial adapter and give it a go.
> Should you still have trouble check to see if you are listed
> in the dialout group...
>
> Common problems with serial ports on Linux/Unix ("Unix"
> includes Mac OSX) with Xastir include:
>
> *) Specifying the wrong device or device path in Xastir's
> interface dialog.
> *) Wrong serial port settings in Xastir's interface
> dialog.
> *) Incorrect ownership, group ownership, or permission for
> the device
> *) Group membership for the user doesn't match group for
> the device
> *) Wrong startup/shutdown scripts for Xastir's interface,
> for devices that need setup commands.
> *) Probably other things I can't think of right now...
>
> See the docs distributed with Xastir, the www.xastir.org
> Wiki, and mailing list archives for discussions about all of
> these. Feel free to ask again on the list if you don't
> get satisfaction.
>
> NOTE: Running Xastir as the "root" user is _not_ a
> solution to any of the above, but a serious problem in its
> own right. Don't do it. Friends don't let
> friends run as root!
>
> -- Curt, WE7U.
> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
>
_______________________________________________
Xastir mailing list
[email protected]
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
