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 144.390 setup notes: paths, Mic-E, SmartBeaconing, Direwolf iGate and checking results on aprs.fi

ci_cover.jpg

This thread is for sorting out the practical parts of APRS that tend to get confused when someone moves from "my radio beacons" to "I'm running infrastructure." It covers the RF side (144.390 MHz in North America), what the handheld does for you, and what a Direwolf box adds. Please correct anything that doesn't match your region or firmware.

The basics. APRS rides on AX.25 unnumbered information (UI) frames, sent as 1200 baud AFSK (Bell 202-style) on the standard simplex channel. That channel is 144.390 MHz in North America. Other regions use other frequencies, for example 144.800 MHz in much of Europe and Africa, and 145.175 MHz in Australia. Check your local band plan before programming a radio. Because every station shares one channel and there is no collision avoidance beyond listen-before-talk, airtime is the scarce resource. Most of the tuning advice below comes down to sending fewer, more useful packets.

Paths. A UI frame carries a destination field, a source callsign and up to eight digipeater hops. A fill-in digipeater answers to WIDE1-1. Wide-area digipeaters answer to WIDE2-n. The usual guidance for mobile stations is WIDE1-1,WIDE2-1, which gives one fill-in hop and one wide hop. Fixed stations with good coverage often go direct or use a single hop. Long paths like WIDE5-5 multiply every packet across the whole area and are widely discouraged. If you can see a digipeater directly, you rarely need more than one or two hops.

Mic-E versus plain position reports. Mic-E packs latitude into the destination address field and puts longitude, speed and course in the information field, plus a status code such as In Service or Emergency. It's compact, which is why many handhelds and mobile rigs use it for tracking. Plain (uncompressed) position reports are longer but human-readable, and they are what you see on most fixed stations, objects and weather reports. If a tracker is doing Mic-E and you decode it on a laptop, a destination callsign that looks like gibberish is expected.

Handhelds. The Kenwood TH-D74 and TH-D75 have a built-in GPS, a TNC and APRS support, and they can also be used as a KISS TNC over USB or Bluetooth. The Yaesu FT5D also has built-in GPS and APRS. Details such as beacon types, packet formats and data rates differ by model and firmware, so check the manual for what your unit actually sends. A common mistake with all of them is leaving the beacon on a fixed interval while standing still. That fills the channel with duplicate positions.

SmartBeaconing. This is the usual fix for that problem. It beacons often when you are moving fast, rarely when slow or stopped, and sends an extra packet when your heading changes enough. The main parameters are:

  • a low speed and slow rate
  • a high speed and fast rate
  • a minimum turn angle
  • a turn slope
  • a minimum time between turn-triggered beacons

Defaults suit highway driving. They may be too chatty for walking or cycling, and too slow for tight city streets, so adjust them to how you actually travel.

Direwolf as TNC, digipeater and iGate. Direwolf is a software TNC. A sound card or USB audio interface connects to the radio, and Direwolf handles the modem, KISS and AGW interfaces, digipeating and the iGate function. A minimal config has these pieces, with placeholder values here:

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

Set levels carefully. Over-driven receive audio is a frequent cause of poor decoding, and the audio levels Direwolf reports at startup are a good starting point. Also keep in mind that gating RF to the internet requires a valid login and that iGates should only pass traffic appropriately. Many operators begin with receive-only (RF to IS) before enabling any transmit gating.

Objects, messages, weather. An object lets one station report a position for something else, such as an event, a repeater or a storm. It has a name of up to nine characters and is marked live or killed. Messages are addressed to a callsign padded to nine characters, with a message number so the other end can acknowledge. Weather reports use a weather symbol and fixed fields for wind, gust, temperature, rain, humidity and barometric pressure, and they should go out at a modest interval.

Questions to get started: What path do you use on a mobile, and why? Has anyone tuned SmartBeaconing for walking or cycling? And what's your preferred way of checking that an iGate is actually working?

  • Replies 2
  • Views 41
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On paths: it helps to check what your local digipeaters actually do before choosing. Some areas run only WIDE1-1 fill-ins plus WIDE2-n wide digis, and others use regional aliases. Reading nearby digipeater beacons and comments, or asking the local APRS group, is better than copying a path from a forum post. If you transmit from a high point, a single hop is often enough, and a long path will only cause duplicates over a larger area.

On SmartBeaconing, the cleanest way to tune it is to think about what each setting is for. The slow rate is the heartbeat while you're stopped. The fast rate is for highway speeds. The turn settings are there to keep the track from cutting corners on the map. If you see lots of beacons while stationary, the likely culprit is GPS jitter making the unit think it's turning, so raise the minimum turn time or the turn angle. For walking, you'd usually lower the high-speed threshold so the fast rate actually kicks in.

For the TH-D74/D75, FT5D and others, also check whether the radio is set to digipeat, whether it uses its internal TNC or an external one, and which frequency the APRS band is set to. A surprising number of "it doesn't work" cases come down to the radio sitting on the wrong band or channel.

  • Administrators

For checking an iGate, aprs.fi is useful because you can open a station's raw packets and read the path. Packets that came in over RF and were gated usually carry a q construct such as qAR or qAO along with the iGate's callsign, so you can see which iGate put them on the internet. If your own packets never show up there, work backward. First, is the radio really transmitting on the right frequency? Second, can another station or iGate hear you? Third, is the packet being decoded properly, and is the path sensible? Direwolf's console output is handy here because it shows what it received on RF.

A couple of Direwolf notes. Use unique SSIDs so your iGate, digipeater and mobile don't all appear as the same station. Don't enable both digipeating and internet-to-RF gating without understanding the consequences, because careless IS-to-RF gating adds traffic to a channel that is already narrow. Many iGates only gate messages for stations they have recently heard on RF, which is the right design.

On weather and objects, one practical point: the weather packet format is picky about field widths, and missing values are filled with dots or spaces rather than left out. If aprs.fi shows a station as a weather station but displays odd values, compare the raw packet to the format spec. Units are also easy to mix up, since temperature is in degrees Fahrenheit and pressure is in tenths of a millibar in the standard format.

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.