[aprssig] Interpeting packets on findu

AE5PL Lists HamLists at ametx.com
Fri Apr 7 06:03:09 CDT 2006

The findU server only sees data passed to APRS-IS via other servers.  In
other words, no one connects to the findU server to feed data (it
connects to the APRS-IS servers).  IGate<->APRS-IS servers->findU
database.  Therefore, if the IGate is connected to a limited feed port
on an APRS-IS server, all of its gated packets will appear to findU as
qAo since the server it is connected to has set the gated packets q
construct to qAo.  Only the server that the IGate is connected to sees
the qAR or I construct in this case.  The server then sends the packet
to the rest of APRS-IS with the qAo construct.

This effect is the same as with the I construct.  You don't see ,I on
APRS-IS.  The servers convert it to a qAR (or qAo) construct before the
packet gets distributed to the rest of the APRS-IS.

Don't make it more complicated than it is.  IGates may only generate qAR
or I constructs for _gated_ packets.  _No_ other constructs are
generated by APRS clients including IGates.  _All_ other q constructs
are generated by the _servers_ (qAI is a diagnostic construct which
should not be used except under the direction of a server sysop).

Hope this clears it up for you.


Pete Loveall AE5PL
mailto:pete at ae5pl.net 

> -----Original Message-----
> From: Stan - N0YXV
> Posted At: Thursday, April 06, 2006 9:52 PM
> Subject: RE: [aprssig] Interpeting packets on findu
> Ok I guess I'm confused then. If I understand you correctly 
> then you should never be able to see a qAO or qAo in 
> findu.com data. If the server (APRS-IS
> Server?) changes qAR to qAo then why do I see qAO and qAo as 
> well as qAR on findu.com data strings? Please help me get unconfused.

More information about the aprssig mailing list