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 on 144.390: Direwolf iGate/fill-in digi plus handheld tracking with SmartBeaconing, paths, and messaging

ci_cover.jpg

I'd like to collect practical notes on a common APRS setup: a fixed Direwolf station at home acting as an iGate (and possibly a fill-in digipeater), plus a handheld or mobile radio such as a Kenwood TH-D74/TH-D75 or Yaesu FT5D doing tracking and messaging. Most problems with this setup come from a handful of settings, so here is the basic picture, then some questions.

The RF side. In North America, APRS runs on 144.390 MHz at 1200 baud AFSK (Bell 202), carrying AX.25 UI frames. Other regions use different frequencies. Europe and Africa are generally on 144.800, and Australia and New Zealand use 145.175 and 145.225. Check your local band plan before programming a radio. The channel is shared and simplex, with CSMA-style listen-before-talk, so every extra beacon costs everyone airtime. That is why beacon rate and path length matter.

Paths. The usual mobile or handheld path in the "new-N" model is WIDE1-1,WIDE2-1. WIDE1-1 lets a fill-in digi near you pick up a low-power signal. WIDE2-1 lets a wide-area digi carry it one more hop. Long paths such as WIDE5-5 mostly create duplicate traffic. A fixed station with good coverage often does better with a single hop or no digipeating at all. If your own iGate hears you directly, the packet reaches APRS-IS without any digipeater.

Direwolf as an iGate. Direwolf is a software TNC and sound-card modem. It can decode, digipeat, iGate, and talk to other software over KISS or AGWPE. A minimal receive-only iGate config looks roughly like this (placeholders, not real values):

ADEVICE plughw:1,0
ACHANNELS 1
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"

The passcode is the APRS-IS passcode derived from your callsign, and the server should be the regional rotate for your area. Using sendto=IG keeps the station beacon on the internet side only, with no RF transmission. For a TX iGate or digipeater you also need PTT control, a sensible via path on the beacon, and a deliberate decision about what gets gated from the internet to RF. A TX iGate should only pass messages to stations it has recently heard on RF, not general traffic. Otherwise it floods the channel.

Handhelds. The TH-D74, TH-D75, and FT5D all have a built-in GPS and APRS function, and both Kenwoods can also act as a KISS TNC. They typically encode position as Mic-E. Mic-E packs latitude into the destination address field and puts longitude, speed, course, and a status code into the information field, so a position report is short. A shorter frame is a shorter transmission on the shared channel. Menu names and supported baud rates differ by model and firmware, so check the manual for your radio. For 144.390, use 1200 baud.

SmartBeaconing. A fixed interval is wasteful. At 5 km/h you don't need a position every 60 seconds, and at highway speed once a minute is too coarse. SmartBeaconing adjusts the rate by speed and sends extra beacons when you turn. The main parameters are:

  • slow speed and slow rate
  • fast speed and fast rate
  • minimum turn time
  • minimum turn angle
  • turn slope

Defaults are usually a reasonable start. If you see clusters of points in town, raise the minimum turn time or angle before shortening anything.

Weather, objects, messaging. A weather station sends a position report with the weather symbol and fields such as wind direction (c), wind speed (s), gust (g), temperature in Fahrenheit (t), rain (r, p, P), humidity (h), and barometric pressure (b). Ten minutes or longer between reports is plenty. Objects (the ';' packet type) let one station place a named item on the map, such as an event or a shelter. The name is padded to nine characters, and '*' marks it live while '_' kills it. Messages use the ':' type, with the addressee padded to nine characters, text limited to 67 characters, and an optional message number after '{' for acknowledgement.

To verify things, look up your callsign-SSID on aprs.fi and open the raw packets view. The path shows whether you were heard directly or via digipeaters, and which iGate injected the packet. If your handheld's packets never appear, the problem is usually RF coverage, deviation or audio level, or a bad path rather than the radio.

Questions for everyone: what path do you recommend for a handheld that is mostly stationary? And how do you decide between RX-only iGate, TX iGate, and fill-in digi when an area already has some coverage?

  • Replies 2
  • Views 46
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On the stationary handheld question: if a digipeater or iGate hears you directly, extra hops add little. A reasonable starting point is a single WIDE1-1, or a longer interval with a modest path. The rule is that the path should only be as long as the number of hops you need. Anything that gets repeated by three digis shows up as three copies on everyone's receiver.

For RX-only versus TX, the safest order is to run the iGate receive-only first and watch aprs.fi for a few days. That shows which stations you actually hear and whether the sound card levels are sane. Direwolf logs audio level per decoded packet, so aim for decode levels in a healthy middle range instead of clipping. Only turn on TX iGating once you understand local activity, and keep the internet-to-RF gating limited to messages for stations you've heard locally. A fill-in digi is only worth adding where a hill, a valley, or a building leaves an obvious hole that you can verify with test beacons. Otherwise you add duplicate traffic without adding coverage.

  • Moderators

Two details that cause confusion on handhelds. First, APRS on a dual-band radio usually means one band is the data band, so voice monitoring on a second frequency may be limited depending on the model and settings. Check how your radio behaves when it receives a packet on the APRS side. Second, power and antenna matter more than people expect. A stock rubber duck inside a car gets a weak, inconsistent path. A mag-mount on the roof usually helps more than any beacon setting.

For SmartBeaconing, one practical way to tune it is to drive or walk a known route, then look at the track on aprs.fi. If corners are cut off, lower the minimum turn time or angle. If you see packet bursts at intersections, raise them. Also set the comment and status text sparingly. Each extra character lengthens the packet. For messaging, remember the 67-character limit and don't expect instant replies. Retries and acks make delivery slower than SMS, especially on a busy 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.