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 mic-E, SmartBeaconing, digipeater paths and iGates fit together (and where Direwolf, the D74/D75 and FT5D come in)

ci_cover.jpg

I'd like to lay out how an APRS packet gets from a handheld or mobile to a dot on aprs.fi, and then ask for corrections and additions. The aim is a mental model that helps when something doesn't show up on the map.

Start with the RF layer. In North America APRS runs on 144.390 MHz using 1200 baud AFSK (Bell 202) carrying AX.25 unnumbered information (UI) frames. These are unconnected broadcasts. There is no handshake and no guarantee anyone heard you. Other regions use different frequencies, so check your local APRS frequency before assuming 144.390 applies to you.

A packet has a source callsign with SSID, a destination field, an optional digipeater path, and an information field. The path (for example WIDE1-1,WIDE2-1) tells digipeaters how far they may repeat the packet. Each digipeater that repeats it decrements the hop count, and the packet is dropped when the count reaches zero. The usual advice is to keep paths short. Long paths such as WIDE2-2 or more multiply every transmission across a shared 1200 baud channel, and the channel gets crowded fast.

Mic-E is worth understanding because the Kenwood and Yaesu handhelds use it. It is a compact position format that hides part of the latitude in the destination address field, and the information field carries longitude, speed, course and symbol. It also carries one of a small set of preset status codes (In Service, En Route, Off Duty and so on). That is why a Mic-E packet looks odd in a raw monitor: the destination looks like a random string rather than a callsign or the usual APRS software identifier. It is not corrupt.

SmartBeaconing is a beaconing algorithm, not a packet format. Instead of transmitting every N minutes, the radio adjusts its rate to your behaviour. It beacons often at speed, slowly when stopped or crawling, and sends an extra beacon when you turn by more than a threshold. The tunable parameters are roughly slow speed and slow rate, fast speed and fast rate, minimum turn angle, turn slope and minimum turn time. Poor settings are a common cause of a cluttered trail or a track that cuts corners, so tune them to how you actually drive or walk rather than copying values blindly.

The radios: the Kenwood TH-D74 and TH-D75 have an integrated GPS, APRS, a built-in TNC and a KISS mode, so they can serve as a TNC for a computer. The Yaesu FT5D has GPS and APRS built in as well. All of them transmit at handheld power, usually with a compromise antenna, so being decoded by a digipeater is the limiting factor, not the radio's features. A mobile with an external antenna often gets into the network where a handheld on the belt does not.

On the infrastructure side, an iGate receives RF packets and forwards them to APRS-IS, the Internet backbone. aprs.fi is one of several sites that reads from APRS-IS. If your dot isn't on aprs.fi, the packet may not have been heard by any iGate, or it may have been malformed or filtered. The site's raw packet view is the first place to look.

Direwolf is a popular software TNC and can also act as digipeater and iGate. It decodes audio from a sound interface, speaks KISS and AGW to client programs, and can beacon itself. A minimal iGate config is conceptually just a few lines:

MYCALL N0CALL-10
MODEM 1200
IGSERVER your.aprs-is.server
IGLOGIN N0CALL-10 yourpasscode
PBEACON delay=1 every=30 symbol=igate lat=.. long=..

Treat that as a sketch. Check the Direwolf documentation for the exact syntax and current options, and use your own callsign and passcode. Also be conservative about gating from the Internet back to RF. It should be limited, for example to messages addressed to stations recently heard locally, so you don't add unnecessary traffic to the channel.

Finally, the less glamorous packet types. Objects (the ; type) let one station place a named item on the map, such as an event or a hazard, with a nine-character name that can be marked live or killed. Messages go to an addressee padded to nine characters, can carry a message number, and are acknowledged by the receiver; the text is short, around 67 characters. Weather stations send a weather report with position, containing wind direction and speed, gust, temperature in Fahrenheit, rain, humidity and barometric pressure in tenths of millibars. Each of these is a different information-field format on the same shared channel.

What have I got wrong or oversimplified? I'm especially interested in sensible path choices for a fixed station versus a mobile, and in what reasonable SmartBeaconing starting values look like for a car and for walking.

  • Replies 2
  • Views 36
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

The mental model is right. One refinement on paths: the right choice depends on what digipeaters exist where you are. In an area with good wide-area digipeater coverage, a fixed station often needs only a single hop or none at all, and a mobile might use WIDE1-1,WIDE2-1 so that small fill-in digis and wide-area digis can both pick it up. In sparse areas, a longer path may be justified, but it should be a deliberate decision, not a default someone copied from a tutorial. Look at what your local APRS group recommends, because digipeater behaviour varies by region.

On the handheld question, the same applies to the TH-D74/D75 and the FT5D. The radio is not the bottleneck, the antenna is. A rubber duck held against your body and used indoors can mean a perfectly configured radio never reaches a digipeater. If a position doesn't show up, check the radio's own APRS monitoring first. If you can hear the local digipeater and it hears you, the beacon should get through. If you hear nothing at all, the issue is coverage, not settings.

One more tip on Mic-E: if your raw packet looks strange, decode it before blaming the radio. aprs.fi's raw view and Direwolf's own logs will both interpret it for you. The garbage-looking destination field is normal.

  • Moderators

A few practical additions on the software side. With Direwolf, most trouble is audio level, not configuration. If the input level is too high or too low, decoding drops and you will see missed packets even though the config is perfect. Direwolf prints audio level information for each decoded frame, so use that to adjust the receive level, and make sure your radio's data or packet mode and its squelch behave as expected. Also watch the transmit side: overdriving the audio into the radio's mic or data input widens the signal and hurts decoding for everyone.

For SmartBeaconing, keep the idea of the tradeoff in mind. A faster fast-rate gives a smoother track but uses more channel time, and 1200 baud channels are shared by everyone in range. A turn-triggered beacon is useful, but a very low minimum turn time can produce bursts on twisty roads. Start from the defaults your radio provides, watch your trail on aprs.fi, and adjust one parameter at a time. Walking needs different speed thresholds than driving; the slow speed and fast speed values should reflect your actual speeds.

On weather stations: the packet format is simple, but units are specific (Fahrenheit, mph, hundredths of an inch for rain, pressure in tenths of a millibar), so a weather program that converts units is worth using rather than hand-building packets. Beacon the weather at a modest interval. Weather data rarely changes fast enough to justify frequent transmissions.

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.