Order Tray | Contact Us | Home | SIG Lists

[aprssig] qA? Questions

Pete Loveall AE5PL Lists hamlists at ametx.com
Mon Jun 2 10:44:56 UTC 2008

Per http://www.aprs-is.net/q.aspx qAO represents a packet with the source call not matching the login and the client is logged into a client-only port (not an IGate port).  Older server software sometimes would show this on an IGate-capable port, as well.

qAo is the same as qAO except that the logged in client had put an indicator in the path showing the packet has been gated from RF.

qAX indicates that your APRSPoint is not registered and therefore cannot be used as an IGate.  qAC indicates that the client software is registered.  qAX and qAC are not used on gated packets, only on packets inserted directly by the client (like posit, status, and message packets originated from the logged-in client).

The only q code to be created/used by client software is qAR to indicate a packet is gated from RF to APRS-IS.  All other q codes are generated by the server software.

javAPRSSrvr is used by the majority of server sysops and is actively maintained.  It has a fully functional and compliant IGate which restricts its gating to RF based on digi hops.  You can find more information on it at http://www.aprs-is.net/javAPRSSrvr and you can find APRS-IS specifications for your own project at http://www.aprs-is.net

Hope this helps.


Pete Loveall AE5PL
pete at ae5pl dot net

> -----Original Message-----
> From: Patrick Domack
> Sent: Sunday, June 01, 2008 9:37 PM
> To: TAPR APRS Mailing List
> Subject: [aprssig] qA? Questions
> I have noticed on my igate (aprsd), the packets it gates used to
> always be qAR, but lately it's changed to sometimes qAO or qAo. (I
> have also noticed my aprspoint is getting qAX, but this must be a
> different issue)
> I have read up on the q-codes and what they mean, but it doesn't
> really explain the difference between the qAR vs qAO, other than qAR
> is for a special igate port usage, and that doesn't make much sense to
> me.
> -----
> Based on the issues, and the amount of work to track down issues
> (there isn't much consistancy) I think I am just going design a new
> program and start working on bringing it up.
> If anyone has suggestions for me, or general comments, I'm open. Best
> now to ask before it's created and starts getting inflexable :)

More information about the aprssig mailing list