[Xastir-dev] OpenTRAC errors - cutting off part of SSID

[Curt, WE7U]

On Tue, 13 Apr 2004, J. Lance Cotton wrote:

> I just got my OpenTracker built and when it sends the OpenTRAC protocol,
> Xastir receives it, but it seems to cut off the last character of the
> callsign-ssid. I haven't done further testing yet, but when I have my
> callsign at KJ5O-11, Xastir shows it as KJ5O-1.
>
> When the OpenTracker is sending APRS protocol, xastir shows the callsign as
> KJ5O-11, correctly.
>
> The AX.25 'listen' command shows that the incoming packet does have the full
> proper callsign-ssid of KJ5O-11.
>
> Also, does Xastir take advantage of OpenTRAC's increased position precision
> or does it just convert to standard APRS... Now that we support the
> higher-precision NMEA strings in Xastir, can it also support this for
> OpenTRAC as well?
>
> (I will file SourceForge bug reports...)

Please do so.  OpenTrac protocol support in Xastir is very
preliminary.  So far it just converts to standard APRS packets and
throws it into the standard decoding.  I don't recall whether it
does the higher precision, it might if I converted it to
compressed-mode posits.  I can't use the normal NMEA strings because
we lose other information that way.

Eventually we need to do full-blown OpenTrac decoding, and not
create APRS packets out of them.

--
Curt, WE7U			    archer at eskimo dot com
Arlington, WA, USA		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!"