[Xastir] Can someone help fix an error in configuration

[Tom Russo]

On Mon, Sep 13, 2010 at 09:26:12PM +0000, we recorded a bogon-computron collision of the <n.heyen at comcast.net> flavor, containing:
> 
> 
> I have Xastir 1.98 running on Ubuntu 9.10 with a TT4. It seems that it works right, I'm sending a lot of packets to APRS-IS and at least a few packets as a digi. But when I look at the raw packets on APRS.FI (my station id is KC9NVN - no SSID used at this point). 
> 
> 
> 
> I set up the TT4 per the Yahoo Group??file Fillin Digi V0.64.pdf - I set it up and let it run for a couple of days without Xastir attached and seemd OK. 
> 
> 
> 
> It looks like I'm getting errors in the digi packets but I'm not sure if the bad packets are from my origin or something that I'm passing along. A sample of the packets is below: 
> 
> 
> 2010-09-13 11:50:00 CDT: KC9NVN>APTT4,KB9WZM-10,WIDE2*,qAR,N9QIP:=4217.27N108940.67W#XASTIR-Linux-Freeport,IL 
> 2010-09-13 12:20:01 CDT: KC9NVN>APTT4,KB9WZM-10,WIDE2*,qAR,W9TMW:MYCALL KC9NVN [Unsupported packet format] 
> 2010-09-13 13:20:03 CDT: KC9NVN>APTT4,KB9WZM-10,WIDE2*,qAR,W9TMW:<0x03>k [Unsupported packet format] 
> 2010-09-13 14:59:55 CDT: KC9NVN>APTT4,KB9WZM-10,WIDE2*,qAR,N9QIP:<0x03>UNPROTO APX199 VIA WIDE2-1 [Unsupported packet format] 
> 2010-09-13 15:00:36 CDT: KC9NVN>APTT4,KB9WZM-10,WIDE2*,qAR,W9TMW:<0x03>k [Unsupported packet format] 
> 2010-09-13 15:20:07 CDT: KC9NVN>APTT4,KB9WZM-10,WIDE2*,qAR,W9TMW:MYCALL KC9NVN [Unsupported packet format] 
> 2010-09-13 15:20:08 CDT: KC9NVN>APTT4,KB9WZM-10,WIDE2*,qAR,N9QIP:<0x03>UNPROTO APX199 VIA WIDE2-2 [Unsupported packet format] 
> 

You don't seem to have your TT4 set to be a KISS TNC, and you're attaching it
to Xastir as a Serial, command-mode TNC.  "MYCALL", "UNPROTO" and so forth are 
serial-TNC commands.  "<0x03>k" is "Control-C" followed by K, which is what
Xastir sends to put the TNC into command mode.

Xastir is sending serial TNC commands to the TT4 and they're being transmitted.
That's wrong.  Those commands are meant to be interpreted by the TNC, not
transmitted.

I don't think the TT4 can function as a serial, command-mode TNC, but as I 
understand it it *can* function as a serial KISS TNC.  So you have to put it in 
KISS mode and tell Xastir to talk to it as a KISS TNC.

The only thing that's going right here is that the TT4 is beaconing on its
own (as evidenced by the APTT4 tocalls).  Everything that Xastir's doing is 
being interpreted wrong and generating bad packets.

Consult the TT4 documentation on putting the tracker into KISS TNC mode instead
of tracker mode.

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236        http://kevan.org/brain.cgi?DDTNM
 "The truth will set you free, but first it will piss you off."