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 384.8 km/s
Aurora 1
Updated 13:30 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 setup sanity check: paths, Mic-E, SmartBeaconing, and getting a Direwolf iGate onto aprs.fi

ci_cover.jpg

I'd like to collect the technical basics of APRS in one thread, because the same questions keep coming up: why a beacon doesn't show on aprs.fi, why a handheld floods the channel, and what the difference is between a digipeater and an iGate. Corrections are welcome. Details vary by region and by network policy, so treat the specifics below as a starting point.

The basics. APRS sends unconnected AX.25 UI frames, 1200 baud AFSK, on a shared simplex frequency. In North America that is 144.390 MHz. Other regions use different frequencies; 144.800 MHz is common in Europe, for example. Because everyone shares one slow channel, every unnecessary packet costs everybody airtime. Most APRS problems come down to too many beacons, paths that are too long, or no one in range to hear you.

Digipeater vs. iGate. A digipeater repeats your packet on RF so more stations can hear it. An iGate listens on RF and forwards valid packets to the APRS-IS internet backbone, and it can also gate messages from the internet back to RF for stations it has recently heard locally. aprs.fi is a viewer for APRS-IS data. If your packet never reaches an iGate, it never appears there, no matter how well it was transmitted. Packets whose path contains markers like TCPIP, TCPXX, NOGATE or RFONLY are not supposed to be gated.

Paths. A common mobile or handheld path is WIDE1-1,WIDE2-1. WIDE1-1 lets a local fill-in digipeater pick you up, and WIDE2-1 lets a wide-area digipeater take one more hop. Long paths, or the old RELAY and TRACE aliases, mostly add duplicate traffic. If you have a good line to an iGate or a wide-area digi, a shorter path such as WIDE2-1 or even a single hop is often enough. Ask local operators what the area expects.

Mic-E. The Kenwood TH-D74 and TH-D75 and the Yaesu FT5D can all send Mic-E position reports. Mic-E packs the latitude into the destination address field and puts longitude, speed and course in the information field. That makes packets short, which matters at 1200 baud. Some decoders show the Mic-E status message (In Service, En Route, Emergency and so on) as a separate field, so don't be surprised if two clients display the same packet differently.

SmartBeaconing. Fixed-interval beacons from a moving station are wasteful. SmartBeaconing adjusts the beacon rate to speed and turning. At low speed it beacons rarely, at high speed more often, and it adds a beacon on sharp turns (corner pegging). The main parameters are the slow and fast speeds, the slow and fast rates, the minimum turn time, the turn angle and the turn slope. Defaults vary by radio and software, so check your menu or config rather than assuming. A stationary station should beacon slowly, with intervals of tens of minutes rather than seconds.

Direwolf. Direwolf can act as a software TNC, a digipeater and an iGate, and it exposes KISS and AGW interfaces for other software. A minimal iGate needs a sound device, a callsign-SSID, a PTT method if you transmit, and an APRS-IS login with your passcode. The relevant config lines look like this: ADEVICE, MYCALL, MODEM 1200, IGSERVER, IGLOGIN. You can also add a PBEACON line for your own position. Use your own callsign and passcode, and pick an SSID that doesn't collide with anything else you run. Audio level matters: an overdriven input or a badly set transmit level will cost you decodes. Direwolf's own logs show decode counts and can help you tune.

Handheld TNCs. The TH-D74 and TH-D75 have a built-in TNC and GPS, and they can be used with an external application through KISS mode. The FT5D also has APRS and GPS features built in. In all of these, check which band is set as the APRS or data band, the packet path, the beacon type and the transmit rate. A radio that's set to beacon every 30 seconds while parked is a classic cause of channel clutter.

Messaging, objects and weather. An APRS message is addressed to a callsign padded to nine characters, and the text is short (up to 67 characters). The message number allows acknowledgment, and a retry that never gets an ack is just more traffic. Objects and items let one station post something else on the map, such as an event or a repeater. An object has a nine-character name and is marked live or killed, and objects should be removed when no longer valid. Weather stations send temperature, wind, rain, humidity and pressure in a standard format, and they usually beacon every 10 to 15 minutes or so. Faster doesn't help anyone.

Questions for the thread: what's your debugging order when a beacon doesn't show on aprs.fi? And what path do you recommend in a sparse area versus a dense one?

  • Replies 2
  • Views 33
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

My debugging order is to check each hop separately, because 'not on aprs.fi' hides several different failures.

First, did the radio actually transmit? Look at the TX indicator and the radio's own beacon log. Second, does the packet look right? A second receiver or a Direwolf log shows the raw frame, including the path and symbol. Third, can an iGate hear you? Look on aprs.fi for nearby iGates and digipeaters, and remember that a handheld with a poor antenna may be heard by a fill-in digi but never reach a wide-area one. Finally, search aprs.fi by exact callsign-SSID, including the raw packet view. A packet that was heard and gated but doesn't appear on the map may have a malformed position, a bad symbol or a filtering issue rather than a radio issue.

On paths, I'd keep it simple. In a dense area a single WIDE2-1 or even no digipeating is often enough, since multiple stations will hear you anyway. In a sparse area WIDE1-1,WIDE2-1 is a reasonable default, but I wouldn't go to WIDE2-2 or higher without a local reason. Each extra hop multiplies the traffic, and that adds up quickly on 144.390.

  • Moderators

On Direwolf, the two things I'd watch for are audio levels and gating rules. If the receive audio is clipped, packets that should decode will be dropped, and then the iGate seems 'quiet' even though the radio is hearing fine. Adjust the receive level until Direwolf's own level readout is healthy, and avoid auto-gain or processing on the sound card.

On transmit, a Direwolf iGate that also beacons is a different job from a receive-only iGate. If you don't need RF transmit, a receive-only iGate is simpler and puts less load on the channel. If you do enable RF gating of messages, keep in mind that it should only send messages to stations that were recently heard directly on RF, and that you are responsible for what goes out under your callsign. Also, don't copy a config from a web page without changing the callsign, passcode and coordinates. A duplicate login or wrong position on APRS-IS makes you look like someone else.

For handhelds, SmartBeaconing is worth setting up, but check the defaults before you drive. A walking pace and a highway pace need different thresholds. If the radio beacons too often at low speed, raise the slow rate. If it's too sparse on turns, check the turn angle and minimum turn time.

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.