[Xastir] Xastir - ArgentData Tracker3 - DR-135T

[Tom Russo]

On Sun, Aug 19, 2012 at 04:50:09PM -0400, we recorded a bogon-computron collision of the <qrv at kd4e.com> flavor, containing:
> Thanks for the assist!
> 
> When I enter:
> 
> "/usr/sbin/kissparms  -p 2  -t 20  -s 10  -r 32  -l 20  -f n"
> 
> ... the response is:
> 
> "axconfig: port 1 not active"

Weird, since your port is named "2" and you've specified it as 2.  Is kissattach
running already?

Still, if you leave everything at its defaults, does axlisten show traffic
on the port?  If so, then you may not need the kissparms.  If "axlisten -a -c"
shows traffic, then you're probably good to go (btw, some distros have
"axlisten" and others just have "listen" -- debian-based distros use axlisten
because there's some other package that has a "listen" as well, and they're
trying to deconflict them).

Regardless, you need to have Xastir set up with an AX.25 interface, it's not
enough to define one outside of Xastir.

> >> "kisattach /dev/ttyACM0 2 12.34.56.78"
> >>
> >> ... to which the response was:
> >>
> >> "AX.25 port 2 bound to device ax0"
> >>
> >> I then opened Xastir where I had previously set my call,
> >> coordinates, etc.
> >>
> >> I am not seeing any APRS messages nor do I see how to
> >> initiate one - it is unclear if Xastir even sees the
> >> Tracker 3 or if the Tracker 3 sees the DR-135T.
> >>
> >> I can view findu stations on the Xastir map - but that's
> >> the Internet side of things.
> >>
> >> Have I missed a step in setting up Xastir?
> >
> > Did you set up an AX.25 interface in Xastir to talk to the AX.25 kernel
> > interface you configured with kissattach?  kissattach only establishes
> > the port that Xastir can connect to, you still have to tell Xastir to connect
> > to it.
> >
> > If not, you need to do that.  Open Interface->Interface Control and make
> > sure you have an "AX25 TNC" interface defined.  If you don't, click the "Add"
> > button and choose "AX25 TNC" as interface type, then fill in the dialog box.
> > The name of the interface you give in this dialog box is the one you gave
> > the port in the /etc/ax25/axports file, not "ax0".  Looks like you've named
> > your port "2" so that's what you'd use.  You might need to set a few KISS
> > parameters using "kissparms" before you use the port as well.  In my
> > ax.25 set-up I do:
> >
> > /usr/sbin/kissparms  -p aprs  -t 20  -s 10    -r 32       -l 20  -f n
> >
> > (my port is named "aprs" where yours appears to be "2")
> >
> > If you *DO* already have an AX.25 interface defined in xastir, then there
> > may be something else going on.
> >
> > Try running "sudo axlisten -a -c" in a shell window and make sure that
> > the ax.25 kernel interface you've got traffic showing up on your ax.25 port.
> > If not, then you might have something else wrong in your ax.25 configuration
> > that has nothing to do with xastir.
> >
> 
> 
> -- 
> 
> Thanks! & 73, KD4E.com
> David Colburn nevils-station.com
> I don't google I SEARCH! duckduckgo.com
> Network: groups.yahoo.com/group/qrv
> Restored to design-spec at Heaven's gate 1Cor15:22
> _______________________________________________
> Xastir mailing list
> Xastir at lists.xastir.org
> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236        http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
 one trick, rational thinking, but when you're good and crazy, oooh, oooh,
 oooh, the sky is the limit!"  --- The Tick