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

[Tom Henderson]

Thank you Brett! I have changed that and no longer transmit on that 
interface.

Tom Henderson

On 10/22/18 7:33 PM, Brett Friermood wrote:
> Rather than using the 'm/' filter for distance from your station, you can
> also use the 'r/' range filter from a specified point. Just use the
> location of your station as the lat/long arguments and you could get the
> same result by only maintaining a connection without having to send a
> position.
>
> Brett KQ9N
>
> On Mon, Oct 22, 2018 at 7:19 PM Tom Henderson <Tom at henderson4.us> wrote:
>
>> I do have a feed from CWOP that I use with a filter for distance. If I
>> don't send a position beacon, I don't get anything back because distance
>> can't be calculated.
>>
>> Tom Henderson
>>
>> On 10/22/18 3:16 PM, Gerry Creager - NOAA Affiliate wrote:
>>> I'm also wondering why it seems to be going through cwop1.aprs.org... We
>>> shouldn't be getting it; we filter for weather packets. That's certainly
>>> NOT a weather packet.
>>>
>>> gerry
>>>
>>> On Mon, Oct 22, 2018 at 2:35 PM Curt, WE7U <curt.we7u at gmail.com> wrote:
>>>
>>>> On Mon, 22 Oct 2018, Tom Henderson wrote:
>>>>
>>>>> I had noticed that the position information for my Xastir digi wasn't
>>>> showing
>>>>> up in my mobile (FTM-400). Today I was playing around with DireWolf and
>>>>> noticed the "Unknown message type K" error. Is this something I have
>> set
>>>>> wrong in my Xastir config?
>>>>>
>>>>> Strangely enough, when i create map objects and transmit their
>> location,
>>>> the
>>>>> location info works just fine.
>>>>>
>>>>> Here's the error message I saw in DireWolf
>>>>>
>>>>> KW4TOM audio level = 45(22/9)   [NONE]   ____|||||
>>>>> [0.6]
>>>>>
>> KW4TOM>APX211,WIDE2-2:KW4TOM>APX211,TCPIP*:=3023.43NT08705.80W&PHG810073
>>>> to
>>>>> all! Gulf Breeze Digi/iGate<0x0d>
>>>>> Unknown message type K, Xastir
>>>> The unusual things I see are the 'T' where the '/' or '\' should be
>>>> between latitude and longitude (didn't consult the spec to see whether
>> that
>>>> was valid or what it means), and the "PHG" is too long... I think you
>> need
>>>> a space between the PHG numbers and the comment. I don't know why it
>> says
>>>> "Unknown message type K", as the only K's I see are in the callsigns.
>>>>
>>>> Ah, consulted the spec: 'T' is an alpha overlay, so that part should be
>>>> good.
>>>>
>>>> --
>>>> Curt, WE7U.        http://we7u.wetnet.net
>>>> "Debating an anti-gunner is like debating an arachnophobe about the
>>>> importance of spiders in the ecosystem." -Stephen Wright
>>>> Coordinate Converter (Android): http://www.sarguydigital.com
>>>> _______________________________________________
>>>> 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
>>
> _______________________________________________
> Xastir mailing list
> Xastir at lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir
>