Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 412.9 km/s
Aurora 1
Updated 14:00 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

APRS end to end: handheld beacons, Mic-E, digipeaters, a Direwolf iGate and what shows up on aprs.fi

ci_cover.jpg

I'd like to put the APRS chain in one place, because most problems ("my beacon isn't on aprs.fi", "my messages never get acked", "the channel is clogged") come down to one link in it. Corrections and additions are welcome.

The basic chain. APRS is not a separate mode. It is AX.25 unnumbered information (UI) frames, 1200 baud AFSK (Bell 202) on VHF FM, sent without connection or acknowledgement at the packet level. In North America the shared frequency is 144.390 MHz. Other regions use different frequencies: 144.800 MHz across Europe and Africa, and different ones in Japan, Australia and elsewhere. Check your local band plan before programming anything. A station transmits a position, object, message or weather packet. A digipeater may repeat it according to the path in the header. An iGate that hears it on RF may pass it to the APRS-IS network over the internet, and sites like aprs.fi read from APRS-IS. So "I'm on aprs.fi" really means that someone's iGate heard you and had a working internet connection. It says nothing about whether your radio is configured well.

Paths. For mobile and handheld use, WIDE1-1,WIDE2-1 is the usual starting point. WIDE1-1 lets fill-in digipeaters pick you up, and WIDE2-1 gives one more hop through a wide-area digipeater. Long paths such as WIDE2-2 or WIDE3-3 multiply your airtime in busy areas and are rarely needed. Fixed stations with good coverage can often use a single hop or no digipeating at all. Avoid old-style RELAY and TRACEn-N paths unless local operators have specifically asked for them.

Mic-E. Many Kenwood and Yaesu handhelds and mobiles transmit positions in Mic-E format. It packs latitude into the destination address field of the AX.25 frame, and longitude, speed, course and symbol into the information field. That is why a Mic-E packet's "to" call looks like random characters instead of something like APxxxx. It's compact, which is good for a shared channel. If a tool appears to show garbage for the destination, it's probably decoding correctly and Mic-E is doing its job.

Radios. The Kenwood TH-D74 and TH-D75 and the Yaesu FT5D all have built-in GPS and APRS functions, so you can beacon without a separate TNC. The D74 and D75 can also work as a KISS TNC to a computer or phone over USB or Bluetooth, which is handy if you want an external mapping or messaging app. Menu names and available options differ between models and firmware, so check the manual for your radio's beacon type (manual, auto, PTT, SmartBeaconing), packet path, comment and status text, and callsign-SSID.

SmartBeaconing. Beaconing every 30 seconds while parked is wasteful, and every 10 minutes at highway speed leaves a trail of long straight lines. SmartBeaconing varies the rate with speed: slow speed means a long interval, high speed means a short one. It also adds extra beacons when your heading changes (corner pegging). The usual parameters are slow speed and rate, fast speed and rate, minimum turn angle, turn slope and minimum time between turn beacons. Settings that suit a car on a highway are usually poor for walking or cycling, so adjust them for how you travel.

Direwolf as iGate or digipeater. Direwolf is a software TNC that uses a sound card to decode and generate AFSK. It can also run as a digipeater, an iGate, a KISS or AGWPE server, and a beacon source. A minimal iGate configuration is built from lines like these, with your own callsign, passcode, audio device, PTT method and coordinates:

ADEVICE plughw:1,0
CHANNEL 0
MYCALL N0CALL-10
MODEM 1200
IGSERVER noam.aprs2.net
IGLOGIN N0CALL-10 12345
PBEACON sendto=IG delay=1 every=30 symbol="igate" overlay=R lat=00^00.00N long=000^00.00W comment="RX iGate"

Those are placeholders, not a working config. Use the example configuration shipped with Direwolf for the exact syntax. Start receive-only, confirm your audio level is sane (the decoder reports levels), and only then consider transmitting, whether digipeating or gating internet-to-RF. A passcode lets you log in to APRS-IS, but it does not give you permission to transmit. That still requires an amateur licence and legal operation on your frequency.

Messaging, objects, weather. A message packet has the addressee padded to nine characters, then the text (limited to 67 characters) and an optional message number such as {123. The receiving station replies with an ack carrying that number, and the sender retries until it sees one. Objects (data type ;) let one station place a named item on the map, such as an event, a repeater or a net control point. Each carries a nine-character name and is marked live or killed. Sending objects at a modest rate and killing them when done keeps the map clean. Weather stations send temperature, wind, rain and pressure in a fixed compact format, usually every 5 to 10 minutes at most, with the weather symbol.

Questions to get things going: what's your usual path in your area, and what do you do about duplicate or junk packets from poorly configured digipeaters?

  • Replies 2
  • Views 35
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Good overview. I'd add one thing about the iGate side that trips people up: gating is not "repeat everything." iGates are supposed to skip packets that already have TCPIP, TCPXX, NOGATE or RFONLY in the path, which avoids loops and respects stations that don't want internet exposure. On the internet-to-RF side, the common practice is to send only messages addressed to stations recently heard directly on RF at that iGate, not the whole feed. If your Direwolf config sends everything to RF, you're adding load for no benefit.

For a first iGate I'd run receive-only for a week and compare against what aprs.fi shows for your callsign. If you hear stations that never appear on the map, check the login, the passcode and whether the server accepts you. If they appear but with weird positions, that's a decoding or source-station problem, not an iGate problem. The raw packet view on aprs.fi is the quickest way to tell. It shows the path, so you can see which digipeater or iGate handled the packet. Be aware that Direwolf's own logs show what your station heard, while aprs.fi shows what APRS-IS received, and those can differ.

On the path question: I'd say keep it short and test with the minimum before extending. In sparse areas WIDE1-1,WIDE2-1 is reasonable. In dense areas, ask local operators what the digipeaters are set up for. Some regions have their own recommendations, and the generic guidance isn't always the best fit.

  • Moderators

On the handheld side, a few things I'd check before blaming the network. First, confirm the radio has a GPS fix. Some radios will beacon the last known position or a fixed one if the fix is lost, which looks like "my tracker is stuck." Second, check the callsign-SSID. Two stations beaconing the same call-SSID will fight on aprs.fi and make the track jump around. Conventions like -7 for handhelds and -9 for mobiles are widely used but not a rule, so just keep yours unique to you.

For SmartBeaconing on a TH-D74/D75 or FT5D, start with the defaults and adjust only if the track looks wrong. If corners are cut off, lower the minimum turn angle or the turn-time limit. If you're clogging the channel in town, raise the slow-rate interval or the minimum time between beacons. A walking profile needs a lower fast speed than a car profile, otherwise the radio never reaches its fast rate.

For messaging, remember that 67 characters is the limit and that an ack only means the other station received it, not that anyone read it. If you message through the network rather than direct, the iGate must have heard the recipient on RF recently. If the recipient is only connected through an internet client with no RF presence, the message goes over APRS-IS and never reaches a radio. That explains a lot of "the message went through but nothing arrived on the radio" cases.

One more point on objects: if you create one for an event, set a sensible beacon interval, include a short comment, and kill it afterwards. Stale objects stay on maps for hours and confuse people, and an object transmitted every minute is a poor use of a shared 1200 baud channel.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.