[Xastir] findy trails

[Curt, WE7U]

On Wed, 9 Jun 2004, Curt, WE7U wrote:

> On Tue, 8 Jun 2004, soldering fun wrote:
>
> > My question is, what would cause findy data to show on findu.com
> > but not xastir?
>
> > I really appreciate any suggestions.. I am stumped.  Does xastir
> > pull this data from findu on the web or via telnet? I haven't had time
> > to read thru the src as of yet.
>
> This is an example packet:
>
> N4YLC-1>APT311,W6CX-3*,wIDE2-2,qAR,AA6VN-5:/230323h3746.27N/12223.84Wk349/042/A=000052/soldering fun!
>
> I'd have to look at the spec to see what's going on, but perhaps
> somelse with a keen eye will see a problem.
>
> Here's what I see so far though:
>
> Path:  Looks ok to me.
>
> Payload:
> --------
> /230323h3746.27N/12223.84Wk349/042/A=000052/soldering fun!
>
> It starts with a '/'.  That seems wrong.

Nope, that's perfectly valid.


> Time/date stamp seems ok, as does the lat/long and the symbol/symbol
> table.

Anything after the lat/long/symbol won't affect whether you see the
station, just whether the additional info gets parsed.

I ran it through Xastir as a log file in debug mode.  Got this:

decode_ax25_line: start parsing
N4YLC-1>APT311,W6CX-3*,wIDE2-2,qAR,AA6VN-5:/230323h3746.27N/12223.84Wk349/042/A=000052/soldering fun!
valid_path: Bad Path: Anti-loop stuff from aprsd
decode_ax25_line: invalid path: APT311,W6CX-3*,wIDE2-2,qAR,AA6VN-5
decode_ax25_line: exiting

So..  There's a problem with the path, not the payload.  Change the
small 'w' to a capital 'W' made Xastir parse it properly.  Since the
AX.25 packet cannot contain lower-case charactes in these positions
in the header, perhaps it was an igate that corrupted it?

--
Curt, WE7U			         http://www.eskimo.com/~archer
"Lotto:    A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"