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: sorting out trackers, digipeater paths, Direwolf iGates and beacon rates

ci_cover.jpg

APRS looks simple (a radio sends a position, a map shows it), but a lot of the trouble people run into comes from the layers in between. This thread is for comparing notes on a few of those layers so beginners and returning operators can see how the pieces fit together.

The basics. In North America, APRS runs on 144.390 MHz using 1200 baud AFSK, carried in AX.25 unnumbered information (UI) frames. Other regions use different frequencies, for example 144.800 MHz across much of Europe and Africa and 145.175 MHz in Australia, so check your local band plan before programming a handheld. Everything shares one simplex channel, which makes beacon discipline matter much more than it first appears.

Handhelds and mobile trackers. The Kenwood TH-D74 and TH-D75 and the Yaesu FT5D all have built-in GPS and APRS functions. The common setup mistakes are mostly the same across them:

  • The APRS frequency, or the band the radio treats as the APRS band, is not set to the local APRS frequency.
  • The data speed is set to 9600 when the local network is 1200.
  • The digipeater path is left at something unsuitable for the area.
  • The beacon is set to transmit on a fixed short interval instead of using SmartBeaconing.

Mic-E is the compact position format most of these radios use for tracking. It packs latitude into the destination address field and puts longitude, speed and course into the information field. That is why a Mic-E packet looks like gibberish in a raw packet monitor, while aprs.fi and most client software decode it without trouble.

Paths. A typical mobile path is WIDE1-1,WIDE2-1. The first hop lets a nearby fill-in digipeater pick you up, and the second hop gets you to a wide-area digipeater. Long paths like WIDE7-7 on a shared channel multiply your traffic across a whole region, which is why most local coordinators discourage them. What counts as a good path depends on how your area's digipeaters are configured, so ask your local APRS group.

SmartBeaconing varies the beacon rate with speed and turns. You set a fast speed and fast rate, a slow speed and slow rate, plus a minimum turn time, turn angle and turn slope. At a standstill you beacon rarely, and on a highway you beacon at a moderate interval. Corner pegging adds extra beacons when your heading changes, so the track follows the road.

Direwolf as a software TNC and iGate. Direwolf can decode from a sound card, act as a KISS or AGW TNC, digipeat, beacon, and gate packets to APRS-IS. A minimal receive-only iGate configuration looks something like this (callsign and passcode are placeholders):

ADEVICE  plughw:1,0
CHANNEL  0
MYCALL   N0CALL-10
MODEM    1200
IGSERVER noam.aprs2.net
IGLOGIN  N0CALL-10 12345

The audio device name will differ on your system. Direwolf's log prints the received audio level, which is a quick way to see whether your receive audio is badly over- or under-driven.

Questions to get things started:

  1. For a handheld used on foot and in a car, what SmartBeaconing numbers have you found sensible? Walking and driving want very different settings.
  2. Is it better to run a receive-only iGate first, and when does enabling RF-side gating make sense?
  3. For weather stations, objects and messages, what are the common formatting mistakes that make data show up wrong on aprs.fi?
  • Replies 2
  • Views 13
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On SmartBeaconing, think about the walking-versus-driving split before you touch the numbers. A single profile rarely suits both. Some radios let you store several beacon profiles, so you can keep one for vehicle use and another for slow movement on foot. Check how your TH-D74, TH-D75 or FT5D handles that in its manual, because the menu structure differs between them.

The general shape is: set the slow rate long enough that a stationary radio isn't clogging the channel, and set the fast rate to something like once every minute or two at highway speed. If the low speed threshold is too low, GPS drift while parked can look like movement and trigger beacons you don't want. The turn parameters matter in town: too sensitive, and every lane change sends a packet. Too relaxed, and your track cuts corners on aprs.fi.

On iGates, a receive-only one is a good first step. It gets your local RF traffic onto the internet without adding transmissions. If you later want to gate messages from the internet back to RF, that needs more care: you should only gate to RF for stations you have recently heard directly on RF, and avoid gating anything marked NOGATE or RFONLY, or anything that already came from APRS-IS. Direwolf handles a lot of these rules, but you should still read its documentation on transmit gating before enabling it.

A practical check for a new iGate is to look at aprs.fi for your own station and for stations you know are nearby. If you see stations appear with the right timing, the RF-to-internet path is working. If nothing appears, check the passcode, the server name, and whether Direwolf says it is connected.

  • Moderators

On the third question: weather, objects and messages each have their own format, and each has its own typical mistakes.

Weather. A weather report uses fixed-width fields in the APRS spec: wind direction and speed, gust, temperature in Fahrenheit, rainfall in hundredths of an inch, humidity, and barometric pressure. A missing value is shown with dots or spaces rather than being left out, which keeps the fields aligned. The usual error is sending the wrong units or the wrong digit count, so the temperature or rain value comes out wrong on the map. Most weather software handles the formatting for you, but if you're writing your own, test it by reading the raw packet. As for how often to send, every 5 to 10 minutes is common. Faster than that adds channel load without much benefit.

Objects. An object is a position report sent on behalf of something else, such as an event, a net location, a storm or a repeater. The object name is nine characters, padded with spaces, and the packet marks it live or killed. If you create an object and walk away, it can sit on the map long after the event ended unless you send a kill. Set a sensible retransmission interval too, since an object that's re-sent often is still using the shared channel.

Messages. Messages are addressed to a callsign-SSID padded to nine characters, with the text after it and an optional message number at the end. The number lets the recipient acknowledge, and the sender retries until it gets an ack. Messages have a limited text length, so keep them short. When two stations have the same callsign with different SSIDs, make sure you're addressing the SSID that's actually on the radio you want to reach.

For all of these, the raw packet view on aprs.fi is useful because it shows exactly what was heard and which path it took. When a message doesn't get through, look at whether the other station was heard at all and by which digipeater or iGate.

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.