[aprssig] Voice Repeater Frequency Objects

[Robert Bruninga]

If XASTIR is placing the altitude field in the front of position
text, I think that is a mistake.  There are a few fixed fields
that can go -only- there, so the altitude should be palced on
the end.  This preserves all parsing of the other fields, and
also preserves the formatting we use for may objects.

I hope XASTIR will correct this in future releases if this is
indeed how it works.?
Bob, WB4APR 

> -----Original Message-----
> From: aprssig-bounces at lists.tapr.org 
> [mailto:aprssig-bounces at lists.tapr.org] On Behalf Of AC7YY -
Kim
> Sent: Sunday, September 14, 2008 1:44 PM
> To: TAPR APRS Mailing List
> Subject: [aprssig] Voice Repeater Frequency Objects
> 
> 
> I don't have a D710, so I am unable to test this.
> 
> One of my objects is currently set as:
> ;145.470- *111111z4658.87N/12308.42WrT100 R95m Net Su8PM
> 
> With the help of kd7dvd we found this works with the
auto-tuning
> function of the D710.
> 
> However, I found that when I entered altitude in xastir the
object was
> sent as:
> ;145.470- *111659z4658.87N/12308.42Wr/A=002165T100 R95m Net
Su8PM
> 
> The altitude information placed prior to Tone messed up the
> auto-tuning on the D710 according to kd7dvd.
> 
> My question is, does the D710 display altitude (as a field) or
just as
> comment text like the D700?
> 
> If it does display as a field, where should the altitude 
> information be
> placed in the object packet?  
> 
> Would this work?
> ;145.470- *111111z4658.87N/12308.42WrT100 R95m Net Su8PM
/A=002165
> 
> 73
> kim - ac7yy
> 
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>