[aprssig] Yag Tracker

[Jason Rausch]

> If APY*** is already given to Yaesu...

OK, lets go with APRYTx and put this to rest!  I can assure you there will be no more than ten major "versions" of the YagTracker firmware for this model.

Jason Rausch - KE4NYV
RPC Electronics, LLC
www.rpc-electronics.com

--- On Mon, 1/2/12, Greg Dolkas <ko6th.greg at gmail.com> wrote:

From: Greg Dolkas <ko6th.greg at gmail.com>
Subject: Re: [aprssig] Yag Tracker
To: "TAPR APRS Mailing List" <aprssig at tapr.org>
Date: Monday, January 2, 2012, 7:38 PM

I didn't see an answer to the earlier qustion...  If APY*** is already given to Yaesu, then APYT** can't be given to the YAG Tracker,  What does Yaesu "own", either by being assigned the block, or by clients software wild-carding the 4th character?


Greg  KO6TH


On Mon, Jan 2, 2012 at 3:54 PM, Lynn W. Deffenbaugh (Mr) <ldeffenb at homeside.to> wrote:

On 1/2/2012 2:37 PM, Jason Rausch wrote:


We're looking at going with APYTxx (YT for YagTracker) and that gives us up to 99 revisions :o)




36*36 = 1,296 if you use all possible alphanumeric combinations.  Versions don't have to be user recognizable, but at least user differentiable.



Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32



_______________________________________________

aprssig mailing list

aprssig at tapr.org

https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig




-----Inline Attachment Follows-----

_______________________________________________
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://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20120103/46dba3d0/attachment.html>