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 on 144.390: how the pieces fit together (digipeaters, iGates, Mic-E, SmartBeaconing, Direwolf and handhelds)

ci_cover.jpg

APRS gets confusing because it is several things at once: a packet format, a shared simplex channel, a network of digipeaters, an internet backbone, and a set of conventions for objects, messages and weather. This thread is meant to lay out how the pieces connect and to collect practical settings. Corrections are welcome, especially for regional differences.

The RF side. In North America, APRS runs on 144.390 MHz using 1200 baud AFSK with AX.25 UI (unconnected) frames. Other regions use different frequencies. 144.800 MHz is common in Europe and Africa, and Japan and Australia each have their own. Check your local band plan before programming a radio. Everyone shares one channel and nobody acknowledges position packets, so airtime is the scarce resource. That is the reason for the advice about beacon rates and path length.

Digipeaters and paths. A digipeater repeats a packet if its path contains an alias the digipeater answers to. The common mobile path is WIDE1-1,WIDE2-1. WIDE1-1 is picked up by a nearby fill-in digi, usually a low-site or home station. WIDE2-1 is then used by a wide-area digi. Each hop decrements the SSID, and the digipeater inserts its own callsign and marks it as used. Long paths such as WIDE7-7 flood the channel and are discouraged in most areas. Fixed stations with good coverage often use WIDE2-1 or WIDE2-2, or no path at all. Local convention varies, so ask nearby digipeater operators what they recommend.

iGates. An iGate receives RF packets and forwards them to the APRS-IS servers over the internet. This is how aprs.fi and similar sites get their data. Logging in needs your callsign and an APRS-IS passcode. A receive-only iGate is the simplest and least risky setup. A TX iGate sends certain internet traffic back to RF, mainly messages to stations recently heard locally. It should be configured carefully so it does not add traffic or create loops. Packets with TCPIP, NOGATE or RFONLY in the path should not be gated to the internet.

Direwolf. Direwolf is a software TNC. It uses a sound card or USB audio interface as the modem and can act as a digipeater, an iGate, or a KISS/AGW TNC for other software. The configuration lives in direwolf.conf. The key lines are ADEVICE for audio, MYCALL, MODEM 1200, PBEACON for your own beacon, DIGIPEAT to enable digipeating, and IGSERVER with IGLOGIN for the internet connection. By default it offers KISS over TCP on port 8001 and AGW on 8000. Most problems come from audio levels and PTT control rather than from the configuration file, so use Direwolf's own audio level reports to set the input level.

Handhelds. The Kenwood TH-D74 and TH-D75 have a built-in TNC and GPS and can beacon, digipeat, and send and receive messages without a computer. They can also act as a KISS TNC over USB or Bluetooth for other software. The Yaesu FT5D has built-in GPS and APRS as well. The menus differ between radios, and the beacon, path and Mic-E or standard-format settings are easy to misconfigure. Read each manual and check what your own packets look like on aprs.fi.

Mic-E and SmartBeaconing. Mic-E is a compact position encoding. Part of the latitude is carried in the destination address field, and the information field holds longitude, speed and course. It also includes a status code such as In Service or Emergency. It is efficient for mobile use, so many radios use it by default. SmartBeaconing varies the beacon interval with speed and heading changes. The main parameters are fast speed and fast rate, slow speed and slow rate, minimum turn time, minimum turn angle, and turn slope. The aim is frequent beacons when you are moving fast or turning, and infrequent ones when you are slow or stopped.

Objects, messages and weather. Objects represent things other than the transmitting station, such as an event, a storm, or a repeater location. They have a name of up to nine characters and are sent with a timestamp and position. Messages go to a specific addressee, are limited to about 67 characters of text, and use a message number so the receiver can acknowledge. Weather stations send position plus weather data, usually with the weather station symbol, at intervals of several minutes. Excessive reporting should be avoided.

Questions for the thread: what paths and beacon intervals are working in your area, and what settings have you found sensible for SmartBeaconing on the D74/D75 or FT5D?

  • Replies 2
  • Views 31
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

One point on paths: the right path depends on your local digipeater network, not on a global rule. Where WIDE1-1 fill-in digis exist, WIDE1-1,WIDE2-1 works well for mobiles. In places with dense coverage, a single hop may be enough, and extra hops only add duplicates. A fixed home station with a good antenna often gains little from a long path.

For SmartBeaconing, think about the speed range first. Set the slow rate for a stopped or crawling vehicle, such as a few beacons an hour, and the fast rate for highway speed. Then set the corner-pegging values so a turn triggers a beacon without producing a stream of packets in a parking lot. Compare what your radio actually transmits with what aprs.fi shows. The track often looks fine on the radio but shows gaps or clutter on the map.

  • Administrators

On the Direwolf side, if you are setting up an iGate, start receive-only and confirm your packets appear on aprs.fi from the right station. Check the clock and the passcode if the login fails. Only enable transmit iGating once you understand the filters. Keep your own beacon as a separate, deliberate setting with a modest interval. Many first setups repeat the same beacon or use an excessive path.

For a TNC, a handheld in KISS mode can be convenient, but its built-in APRS functions and the KISS interface are separate features, so confirm which one the other software is expecting. For weather, send data from the station at a sensible interval and verify the units and the symbol before leaving it unattended. Finally, if a message does not get through, check whether the recipient's callsign-SSID matches exactly, since messages are addressed to that specific string.

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.