[aprssig] Software identifiers (was: Re: Yag Tracker)
Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.toMon Jan 9 23:54:31 UTC 2012
- Previous message: [aprssig] Software identifiers (was: Re: Yag Tracker)
- Next message: [aprssig] Software identifiers (was: Re: Yag Tracker)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
That comes from a merge of the following sources (at a minimum): http://www.aprs.org/aprs11/tocalls.txt - APxxxx toCalls http://aprs.org/aprs12/mic-e-types.txt - Mic-E types (not all of which are actually implemented) http://www.aprs.org/aprs12/mic-e-examples.txt - Some Mic-E examples And throw in a liberal sampling of observing "unidentified" platforms and looking for commonalities (like the fact that UI-View seems to force some variation of "{UIV...}" into the beacon comments. It would be nice if there was a simple way to tabularize it, but it requires inspection of packets by type to start with. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 1/9/2012 6:26 PM, Andrew P. wrote: > Actually, I was wondering if there was a list of prefix to make/model of radio/TNC/tracker/??? device mappings, such as Lynn has so thoughtfully coded into APRS/CE? > > ------Original Message------ > From: Lynn W. Deffenbaugh (Mr) > To: aprssig at tapr.org > Sent: Jan 9, 2012 5:57 PM > 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 > > > Sent from my Verizon Wireless BlackBerry > > _______________________________________________ > aprssig mailing list > aprssig at tapr.org > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig >
- Previous message: [aprssig] Software identifiers (was: Re: Yag Tracker)
- Next message: [aprssig] Software identifiers (was: Re: Yag Tracker)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
