[aprssig] Voice Repeater Frequency Objects

[Robert Bruninga]

>> There is not a single tracker that places 
>> Tnnn "anywhere in the comment".
> 
> No, but there are many (practically all, 
> I would guess)  that put the altitude 
> immediately after the position.

Again, that is no conflict... Everything decodes it there...

> If the altitude is not immediately after 
> the position, it breaks D700 and D7 
> altitude parsing.  (D700/D7 don't meet spec!)

But the /A=xxxxxx does not need any parsing.  It is the human
readable form of altitude.  So on a D7 or D700, then A=000123
means the user is at 123 feet. 

> The only problem here is either a broken spec 
> for the Tnnn designation, or broken firmware 
> in the D710 (or maybe both).

It is neither.
But we have learned that the D7 and D700 do not "parse"
/A=XXXXXX altitude, they simply display it.  If the D710 does
not parse it, then apparently they decided that humans can read
/A=xxxxxx as meaning xxxxxx feet.

What needs to be fixed is any device that forces /A=xxxxx into
the first bytes if the result of such a forcing offsets all
other comment text to the right and violates the intent of the
user who put his comment text expecting it would go where it was
supposed to go. 

So far, the only problem that I can see is that XASTIR should
not do that.

Bob, WB4APR
> -Jason
> kg4wsv
>