[aprssig] Voice Repeater Frequency Objects

[Joseph M. Durnal]

The altitude really isn't necessary information, especially when you
include the range.  When you see R95m you are going to know it is
quite a bit higher than average terrain.  I would lieave it out for a
shorter packet, or add another bit of information that might be more
useful.

Repeater objects should really be beaconed from a digipeater.  These
look like wide coverage repeaters, so it may be appropriate to have
the object beaconed from more than one digipeater.  It looks like
there is a digipeater UCAPK very close to your repeater object, which
would be the ideal place to originate it.

73 de Joseph Durnal NE3R

On Sun, Sep 14, 2008 at 1:43 PM, AC7YY - Kim <ac7yy at comcast.net> wrote:
>
> 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
>