[Xastir] Position data from Xastir not accepted by Yaesu FTM-400 or Direwolf

[Curt, WE7U]

On Tue, 23 Oct 2018, Tom Henderson wrote:

>>>> [0.6]
>>>> KW4TOM>APX211,WIDE2-2:KW4TOM>APX211,TCPIP*:=3023.43NT08705.80W&PHG7100<0x0d>
>>> I may be misinterpreting the output format of direwolf but it looks to
>>> me like there's an extra set of addresses represented as text in the
>>> body of the message.
>>> 
>>> Thus the body starts with the 'K' of KW4TOM whereas it should start with
>>> the APRS data type ID of '='
>> Yeah, looks like a corrupt third party packet. I think there should be a } 
>> after the first :
>> That matches the error message, too.
>> 
> Hmm, interesting. So that means Xastir is generating a corrupt packet. Any 
> idea why?

I think I've come to that conclusion as well. Saw this:

   http://amsat.org/pipermail/amsat-bb/2017-October/064877.html

Which looks like Direwolf is complaining about the first character after the first ':', which is a 'K' in this case.

It looks like a third-party packet that is malformed.

-- 
Curt, WE7U.        http://we7u.wetnet.net
Babysitting your tracker:  http://info.aprs.net/index.php?title=ControlOperator
Coordinate Converter (Android): http://www.sarguydigital.com