APRS Without the Confusion

APRS is usually described as “ham radio GPS tracking”, which is both true and the reason it gets misunderstood. It is a general-purpose, one-to-many, real-time data network that happens to carry position most of the time. It also carries text messages, weather telemetry, bulletins, objects on a shared map, and emergency traffic — all on a single shared channel.

In North America that channel is 144.390 MHz, 1200 baud AFSK, and effectively every APRS station in the continent shares it. Understanding that one fact — everyone is on one frequency — explains every rule in this guide.

The pieces

Stations transmit short bursts: position, call sign, an icon, and optionally a comment. There is no connection and no handshake; packets are broadcast into the air and anyone in range hears them.

Digipeaters listen for packets and repeat them, extending range far beyond line of sight. They are the reason a 5 W handheld can be tracked across a county.

IGates are Internet Gateways. They hear packets on RF and forward them to APRS-IS, the global internet backbone of the network. This is how your position ends up visible on aprs.fi within seconds, anywhere in the world.

APRS-IS ties every IGate together. Some IGates are bidirectional and will transmit messages back onto RF for stations in their coverage area — which is how you can message a friend’s handheld from a web browser.

Paths: the part that matters

Every packet carries a path — instructions for which digipeaters should repeat it and how many times. This is the single most important setting on your radio, and the one most often wrong.

The modern scheme uses two aliases:

• WIDE1-1 — asks fill-in digipeaters (typically home stations covering a local dead spot) for one hop.
• WIDE2-1 — asks wide-area digipeaters, usually on hilltops with real coverage, for one hop.

The digit after the dash is a hop counter. It decrements at each digipeater, and when it reaches zero the packet stops.

SSIDs

Your call sign carries a numeric suffix from -1 to -15 identifying which of your stations is transmitting. The conventions are informal but widely followed, and using them lets people read your intent at a glance:

So N4LLZ-9 is a car and N4LLZ-7 is an HT, and both are obviously the same operator.

Beacon rate

Transmit only as often as your movement justifies. Every unnecessary packet is channel time taken from someone else.

• Fixed stations — every 20 to 30 minutes. Your house is not moving. Beaconing a stationary position every two minutes is the most common form of APRS rudeness.
• Mobile stations — use SmartBeaconing if your tracker supports it. Rather than a fixed interval, it beacons faster when you are moving quickly and at corners, and slowly or not at all when stopped. It produces a better track with fewer transmissions, which is the whole point.
• Fixed-rate mobile fallback — 2 to 3 minutes while moving, and stop beaconing when parked.

Building a station

The simplest tracker

A radio with a built-in TNC does everything in one box. The Kenwood TH-D75 handheld and TM-D710 mobile are the reference designs: GPS, TNC, and APRS firmware integrated, so you enter your call sign and path and you are on the network. Yaesu’s System Fusion radios with APRS support are similar.

Radio plus phone

A Mobilinkd Bluetooth TNC between any radio’s data jack and a phone running APRSdroid (Android) or a comparable iOS app. The phone supplies GPS and the map; the TNC handles the modem. Considerably cheaper than a dedicated APRS radio and, for messaging, considerably nicer to use.

Receive-only IGate

The most useful thing you can contribute, and it needs nothing you probably do not have: an RTL-SDR dongle, a 2 m antenna, and a Raspberry Pi running an IGate package. It puts every packet your location hears onto APRS-IS and fills in coverage for everyone around you. No licence privileges are even required to receive.

Messaging

APRS messages are up to 67 characters and — unlike position beacons — they are acknowledged. The sending station retries until it receives an ack, so you know whether a message actually landed.

This makes APRS genuinely useful for coordination during public service events and emergencies, where you need short, confirmed, infrastructure-independent text between people who are moving around. It is not a chat system, and a long conversation clogs the channel for everyone; keep exchanges short and move to voice when there is more to say.

Bidirectional IGates will gate messages from APRS-IS back onto RF for stations recently heard locally, which means a web page or a phone can reach a handheld in the field.

Common mistakes

• Excessive path length. WIDE3-3 and beyond. Covered above, and it is the big one.
• Beaconing a fixed station every minute. Nothing has changed. Slow it down.
• Using the wrong frequency outside North America. 144.390 is North American. Most of Europe uses 144.800, Japan 144.640, Australia 145.175. Check before travelling.
• Leaving a tracker running unattended for weeks. If it is not doing anything useful, it is only consuming channel time.
• Treating APRS as private. Every packet is public, permanently archived, and searchable by call sign on several websites. Your track history is on the internet. This is worth thinking about before you put a tracker in your daily driver.
• Digipeating without understanding it. Running a digipeater badly configured — repeating everything it hears, including packets that have already been repeated — actively harms the network. Set one up only after talking to the people already running them locally.

Next — the technical series. This page is the practical overview; these go to the byte level:

• APRS Packet Anatomy: AX.25, TNC2, and Data Types — the frame on the air, field by field.
• Decoding APRS Position Reports — compressed base-91 and Mic-E, decoded by hand.
• APRS-IS: Servers, Filters, and Gateways — the login protocol, q constructs, the full filter language, and IGate rules.
• APRS Weather Stations — the weather packet format and feeding CWOP.