[aprssig] Software identifiers (was: Re: Yag Tracker)

[Bob Bruninga]

OK, I can guess the APY008 is the VX-8R, though, I would have thought they
would have 3 versions for the 8R, 8DR and 8GR?  And then the APY350 for the
FTM-350R...

So, what is the "APY" without any additional version number?

Bob, WB4APR


-----Original Message-----
From: aprssig-bounces at tapr.org [mailto:aprssig-bounces at tapr.org] On Behalf
Of Lynn W. Deffenbaugh (Mr)
Sent: Monday, January 09, 2012 5:57 PM
To: TAPR APRS Mailing List
Subject: Re: [aprssig] Software identifiers (was: Re: Yag Tracker)

 From the .CSV containing ALL toCalls attached to the original message:

APY,1439
APY008,1120
APY05N,1
APY350,561
APYS,1

Remember, those are PACKET counts over 7 days of a full feed...

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

On 1/9/2012 5:36 PM, Bob Bruninga wrote:
>> Did a definitive list of software prefixes (toCalls)
>> ever get posted? Or are we still swirling on this?
> I'm still waiting on a dump of all APYxxx callsigns.  The data provided by
> Lynn was just what I wanted, but for the wrong group.  What we needed was
> all the APYxxx TOCALLs (he provided all the APK calls)..  Then we can
decide
> how to best fit in the YAGtracker...
>
> -----Original Message-----
> From: "Lynn W. Deffenbaugh (Mr)"<ldeffenb at homeside.to>
> Date: Wed, 4 Jan 2012 13:59:50
> Subject: Re: [aprssig] Yag Tracker
>
> Based on about 7 days of full feed, here's the following packet counts for
> APK toCalls.
>
>   APK001 64
>   APK002 96
>   APK003 1164
>   APK01 1
>   APK101 3869
>   APK102 58024
>   APK-2 1
>   APK391 1
>   APKALL 8
>   APKD70 1
>   APKPC3 3003
>   APKRAM 8413
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>


_______________________________________________
aprssig mailing list
aprssig at tapr.org
https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig