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

2018-10-23 Thread Tom Henderson
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

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

2018-10-23 Thread Bill Vodall
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

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

2018-10-23 Thread Tom Henderson
Sorry I forgot to replay on the list: 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

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

2018-10-23 Thread Jason KG4WSV
Maybe I've missed something, but I don't know how your packet is getting from xastir to the receiver that's connected to direwolf. This is the packet that direwolf (allegedly :) received, which may or may not be the packet that xastir actually sent. when I look at raw data from aprs.fi there are

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

2018-10-23 Thread Tom Henderson
OK, that explains what a third party packet is. What I still don't understated s why xastir is generating a third party packet as its beacon, and a malformed one at that. Is anyone else experiencing this from the beacons xastir transmits? Tom Henderson On 10/23/18 3:17 PM, Jason KG4WSV

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

2018-10-23 Thread Curt, WE7U
On Tue, 23 Oct 2018, Tom Henderson wrote: Can you explain what you mean by "third party packet?" The packet I'm showing here is generated by xastir when I go to the interface menu and click "transmit now." Look up "APRS101.pdf". Third-party packets are explained in there. If you want to

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

2018-10-23 Thread Jason KG4WSV
On Tue, Oct 23, 2018 at 2:44 PM Tom Henderson wrote: > Can you explain what you mean by "third party packet?" Short answer, it's packet that's embedded in another packet. Usually (only?) seen on-air when an Igate takes a packet from the network and transmits over RF. from

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

2018-10-23 Thread Curt, WE7U
On Tue, 23 Oct 2018, Tom Henderson wrote: [0.6] KW4TOM>APX211,WIDE2-2:KW4TOM>APX211,TCPIP*:=3023.43NT08705.80W<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

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

2018-10-23 Thread David Brooke G6GZH
On Tue, Oct 23, 2018 at 05:52:49AM -0500, Tom Henderson wrote: > > And with no comment at all: > > KW4TOM audio level = 44(22/9)   [NONE]   | > [0.6] > KW4TOM>APX211,WIDE2-2:KW4TOM>APX211,TCPIP*:=3023.43NT08705.80W<0x0d> I may be misinterpreting the output format of direwolf but it

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

2018-10-23 Thread Tom Henderson
On 10/23/18 7:29 AM, Jason KG4WSV wrote: -Jason On Oct 23, 2018, at 6:49 AM, David Brooke G6GZH wrote: On Tue, Oct 23, 2018 at 05:52:49AM -0500, Tom Henderson wrote: And with no comment at all: KW4TOM audio level = 44(22/9) [NONE] | [0.6]

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

2018-10-23 Thread Jason KG4WSV
-Jason > On Oct 23, 2018, at 6:49 AM, David Brooke G6GZH wrote: > > >> On Tue, Oct 23, 2018 at 05:52:49AM -0500, Tom Henderson wrote: >> >> And with no comment at all: >> >> KW4TOM audio level = 44(22/9) [NONE] | >> [0.6] >>

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

2018-10-23 Thread Tom Henderson
I had changed it so the comment didn't start with a number. didn't make any difference. I just added the space, also no change. Here's the direwolf (v1.5 now) output: KW4TOM audio level = 43(20/9)   [NONE]   ___|| [0.5] KW4TOM>APX211,WIDE2-2:KW4TOM>APX211,TCPIP*:=3023.43NT08705.80W Gulf