[Xastir] Position data from Xastir not accepted by Yaesu FTM-400 or Direwolf
Tom Henderson
Tom at Henderson4.us
Wed Oct 24 05:14:39 PDT 2018
Aha! I fixed it! Since the 2nd header was showing TCPIP*, I started
wondering if it was an artifact of the prior interface 0, which was my
APRS-IS interface. So I shut down Xastir and re-arranged the interfaces
so that the serial KISS TNC was the first interface.
Viola! now the transmitted packet doesn't have the second TCPIP header
in it. And my FT1XD reads the packet as valid and shows distance and PHG
info.
Tom Henderson
On 10/23/18 7:38 PM, Tom Henderson wrote:
> Radio 1 is KW4TOM
>
> Radio 2 has no call sign. it is only receiving APRS packets that
> direwolf is decoding.
>
> Radio 3 is KW4TOM-7, but that has nothing to do witht he malformed
> packet it receives ffrom xastir as far as i can tell.
>
> Tom Henderson
>
> On 10/23/18 7:19 PM, Bill Vodall wrote:
>> What are the callsigns for all 3 stations?
>>
>>> Xastir is connected to one radio via a Mobilnkd TNC2 and receives/xmits
>>> through radio 1, and Icom IC-V8000
>>>
>>> Radio 2 is a Yaesu FT-991 with a built-in USB sound card. I'm using
>>> direwolf to ready the APRS packets from this radio
>>>
>>> Radio 3 is a Yaesu FT1XD with built in APRS.
>> _______________________________________________
>> Xastir mailing list
>> Xastir at lists.xastir.org
>> http://xastir.org/mailman/listinfo/xastir
>>
> _______________________________________________
> Xastir mailing list
> Xastir at lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir
>
More information about the Xastir
mailing list