Order Tray | Contact Us | Home | SIG Lists

[aprssig] Yag Tracker

Greg Dolkas ko6th.greg at gmail.com
Wed Jan 4 04:30:53 UTC 2012


ok, thanks for clarifying.  It would be interesting to know what's actually
in use.

But the other side of the question was what currently is implemented on the
server side.  Is there existing software out there that has all three
characters wildcarded?  If so, then we can re-define to our heart's
content, but the new allocations will be mis-decoded until the software
changes (if it's still supported).

Greg  KO6TH


On Tue, Jan 3, 2012 at 7:28 AM, Bob Bruninga <bruninga at usna.edu> wrote:

> > If APY*** is already given to Yaesu, then APYT**
> > can't be given to the YAG Tracker,
> > What does Yaesu "own"...
>
> TOCALLs are assigned on an equitable basis with sharing where needed.  A
> decade ago APKxxx, APIxxx  and APYxxx were listed for Kenwood, Icom and
> Yaesu long before they ever had any radios.  Those were only placeholders.
> Over time there have been so many applications written, that we have found
> it necessary to share many such large blocks. Kenwood does not even
> exclusively have APK, only APK#xx where # is numeric.
>
> If someone will capture for me all of the existing APYxxx packets currently
> seen, then we can see if there is an obvious sub block.
>
> Jason suggests: "OK, lets go with APRYTx"
>
> I wonder though, if APRRYx would be better since RPC electronics already
> has
> APRRxx?
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20120103/af145590/attachment.htm>


More information about the aprssig mailing list