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.5
Wind 385.0 km/s
Aurora 1
Updated 13: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 on 144.390: how beacons, digipeaters, iGates and Direwolf fit together (and common setup mistakes)

ci_cover.jpg

This is a technical overview for people building their first APRS setup or debugging one that "works but doesn't show up on aprs.fi." It covers the signal path from a handheld or tracker to the map, and the settings that most often cause trouble.

The basic chain. APRS sends AX.25 unnumbered information (UI) frames, with no connection and no handshake. In North America the shared frequency is 144.390 MHz, at 1200 baud AFSK (Bell 202) on FM. Other regions use other frequencies. Europe and Africa commonly use 144.800 MHz, for example, so check your local band plan before transmitting. A station sends a packet and any digipeater that hears it may repeat it according to the path in the header. An iGate that hears it on RF can forward it to the APRS-IS network over the Internet, and sites such as aprs.fi display what APRS-IS receives. If nobody within RF range is running an iGate, your packet can be perfectly valid and still never appear online.

Paths. The path controls how far a packet is repeated. A common mobile path in the US is WIDE1-1,WIDE2-1. WIDE1-1 lets fill-in digipeaters (often low-power or small-footprint sites) pick it up first, and WIDE2-1 lets a wide-area digipeater send it one more hop. Long paths such as WIDE2-2 or WIDE3-3 multiply traffic on a shared channel, so use the shortest path that gets you into an iGate. A fixed station with good coverage may need only a single hop or no digipeating at all. Local practice varies, so check what your area's digipeater operators recommend.

Handhelds. The Kenwood TH-D74 and TH-D75 have a built-in TNC, GPS and APRS functions. The Yaesu FT5D also has built-in GPS and APRS. For all of them, the details that matter are:

  • the callsign and SSID in the radio's APRS settings
  • the beacon path
  • the data band and frequency, which must be 144.390 (or your region's frequency)
  • the packet squelch or data-band settings
  • the beacon type: manual, automatic interval, or a speed-based option

Menu names and supported baud rates differ by model and firmware, so confirm specifics in the current manual instead of relying on a forum summary. A common mistake is setting the radio's main band to the right frequency but leaving the data band on a different one.

Mic-E. Many radios and trackers transmit position in Mic-E format. It packs latitude into the destination address field and puts longitude, speed and course in the information field, along with a status code such as In Service or Emergency. It is compact, which is why it suits mobile use. If a decoder shows a strange "destination" callsign, that is usually Mic-E and not an error.

SmartBeaconing. Instead of a fixed interval, SmartBeaconing adapts to movement. It beacons less often when you are slow or stopped, more often at speed, and sends an extra beacon when you turn (corner pegging). The usual parameters are a slow speed and slow rate, a fast speed and fast rate, a minimum turn angle, a turn slope and a minimum time between turn beacons. Values that suit highway driving are too aggressive for walking, so adjust them for how you travel. Over-beaconing from a handheld wastes airtime for everyone on the channel.

Direwolf. Direwolf is a software TNC. It decodes from a sound card, can talk KISS to other software, and can act as a digipeater and an iGate. A minimal receive-only iGate needs an audio device, MYCALL, a MODEM 1200 line, and an IGSERVER and IGLOGIN pair for an APRS-IS server with your callsign and the passcode for that callsign. Two practical points:

  • Watch the audio level that Direwolf prints for each decoded packet. If it is far too low or too high, decoding suffers. Adjust receiver audio output or the sound-card input until levels are reasonable, and check the Direwolf documentation for the target range.
  • Be deliberate about gating from the Internet back to RF. Many operators run RX-only iGates and enable Internet-to-RF only when they have a clear local reason and they understand the traffic implications.

Objects, items and messages. An object is a position report sent on behalf of something else, such as an event, a repeater, a storm report or a checkpoint. It has a name of up to nine characters and can be marked live or killed. Items are similar, but with shorter names and less overhead. Messages are addressed to a callsign (the addressee field is padded to nine characters), carry a short text, and use a message number so the receiving station can acknowledge it. Retries continue until an ack arrives or the sender gives up. Keep message text brief, because the format limits its length.

Weather stations. APRS can carry weather data either in a position report with a weather symbol or as a positionless weather report. The fields include wind direction and speed, gust, temperature, rainfall and pressure. The station itself usually needs separate software or a logger to turn sensor readings into APRS packets, which Direwolf or another TNC then transmits. Beacon weather at modest intervals. Weather rarely changes fast enough to justify frequent packets.

Troubleshooting checklist when you can't see yourself on aprs.fi:

  • Is the radio on the right data frequency, and is it actually transmitting the beacon? Many radios show a TX indication or log.
  • Is the GPS locked? Some radios send no position without a fix.
  • Is there a digipeater or iGate within reach, and does your path match what it responds to?
  • Is the SSID what you expect? aprs.fi searches by the full callsign-SSID.
  • Is the packet being decoded as Mic-E, compressed or plain format? Compare with the raw packet view on aprs.fi.

Which parts of this chain are giving you trouble? Post your radio, path and the raw packet if you have it, and other readers can compare it against the above.

  • Replies 2
  • Views 14
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

One addition on paths, since that is where mobile setups usually go wrong. If you are in an area where fill-in digipeaters answer WIDE1-1, putting only WIDE2-1 in the path may skip them, and you will then depend on wide-area digipeaters hearing you directly. A handheld with a rubber duck at street level often cannot do that. WIDE1-1,WIDE2-1 covers both cases, but it is the maximum most people should use. Some regions request different conventions, such as specific aliases or lower hop counts, so check local digipeater operators' published guidance before copying a path from a blog.

For debugging, look at the raw packet on aprs.fi and read the path field. Entries with an asterisk show which digipeaters actually repeated the packet, and the name after the last asterisk is usually the last digipeater that handled it before an iGate heard it. If you see your own callsign with no digipeater asterisks and the packet still reached APRS-IS, a nearby iGate heard you directly.

  • Moderators

On the Direwolf side, I'd separate three roles, because they get mixed up. Decoding and KISS output let other software use the TNC. Digipeating repeats RF packets according to rules you configure. iGating moves packets between RF and APRS-IS. You can run only the first, or the first and third, without ever digipeating, which is often the right choice for a home station that just wants to improve coverage for the area's data on aprs.fi.

For a handheld like the TH-D74, TH-D75 or FT5D, remember that its built-in TNC is not a Direwolf replacement. It handles beaconing and messaging, but it does not give you the audio-level reporting, logging or iGate functions that a PC or Raspberry Pi running Direwolf does. Many operators use the radio as the mobile tracker and keep a separate receiver and Direwolf instance at home as the iGate.

One last caution on weather: a wrong callsign or SSID on a weather station will make the data look like it comes from a different or nonexistent station. Give the weather station its own SSID, and keep the position and symbol consistent so it displays as a weather station and not as an unknown object.

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.