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 (handheld, digipeater, Direwolf iGate, aprs.fi) and what to tune first

ci_cover.jpg

I'm putting together a mental model of a basic North American APRS setup and want to check it against what others know. The chain as I understand it:

Tracker or handheld (Kenwood TH-D74/TH-D75, Yaesu FT5D, or a GPS plus TNC) sends an AX.25 UI frame on 144.390 MHz, 1200 baud AFSK. A digipeater may repeat it based on the path. An iGate hears it on RF and forwards it to the APRS-IS servers over the internet. Sites like aprs.fi read from APRS-IS and plot it.

Where I'd like input is the details that make or break this in practice:

1. Paths. In North America, WIDE1-1,WIDE2-1 is the usual starting point for mobiles. WIDE1-1 lets fill-in digipeaters pick up a low-power handheld, and WIDE2-1 gives one more hop from a wide-area digi. Long paths like WIDE2-2 or more only multiply the traffic on a single shared channel. Fixed stations in a well-covered area often do fine with a single hop or even no path.

2. Mic-E vs. plain position. Mic-E packs latitude into the destination address field and puts longitude, speed and course in the information field. That makes frames short, which matters on a 1200 baud channel shared by everyone. Many radios, including the Kenwood and Yaesu handhelds, can send Mic-E. Plain uncompressed positions are longer but easier to read in a raw packet log.

3. SmartBeaconing. Instead of a fixed interval, the beacon rate follows speed and heading changes. Typically you set a low speed and slow rate (stopped or walking), a high speed and fast rate (driving), and corner-pegging values (turn angle, turn slope, minimum turn time) that trigger an extra beacon when your heading changes. The goal is good tracks without flooding the channel while parked. The TH-D74/TH-D75 and many other radios expose these parameters, and Direwolf has a SMARTBEACONING config line for the same purpose.

4. Direwolf as TNC and iGate. Direwolf is a software TNC that decodes audio from a sound card. It can run a digipeater and an iGate, and can talk KISS or AGW to other software. A minimal receive-only iGate config looks roughly like this (placeholders only):

ADEVICE  plughw:1,0
ACHANNELS 1
CHANNEL 0
MYCALL N0CALL-10
MODEM 1200

IGSERVER noam.aprs2.net
IGLOGIN N0CALL-10 12345

PBEACON delay=1 every=30 symbol="igate" overlay=R lat=00^00.00N long=000^00.00W comment="RX-only iGate"

The login needs a valid APRS-IS passcode for your callsign, and the SSID on the iGate should be unique so it doesn't collide with your handheld.

5. Objects and messages. Objects are packets that report a position for something other than the sending station (an event, a net control point, a weather alert area). The name is padded to nine characters, and the object stays on the map as long as it is re-sent or until it is killed. Messages go to an addressee padded to nine characters and carry a message number so the recipient can ack. For example, :N0CALL-7 :hello{12.

Questions: what are sensible starting values for SmartBeaconing on a handheld versus a car? Should a first-time Direwolf iGate stay receive-only? And is there a good way to sanity-check that my packets are actually reaching aprs.fi rather than just showing up locally?

  • Replies 2
  • Views 37
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Your chain is correct. On staying receive-only first: yes, that's a sensible way to begin. An RX-only iGate (RF to Internet) already helps coverage, and you can watch Direwolf's log for what you decode before adding any transmit function. Internet-to-RF gating is a separate decision. Well-run iGates only send messages to RF for stations they have recently heard directly on RF, and they don't gate everything, because that would swamp 1200 baud. Gating rules also drop packets with TCPIP, TCPXX, NOGATE or RFONLY in the path, so don't be surprised if some traffic never reaches the internet.

For checking your packets on aprs.fi, search for your callsign-SSID and look at the raw packets view. It shows the path and which station (the iGate) injected the frame. If you see your handheld's packet there with a q construct like qAR followed by an iGate callsign, it went over RF and was gated. If nothing shows, check these in order: is the iGate actually connected to APRS-IS (look for a login success in the Direwolf output), is your beacon path reaching a digi or iGate at all, and is the radio on the right frequency with APRS actually enabled? Many people forget that a handheld's APRS band may be set separately from the voice band.

One audio detail: level matters more than people expect. If Direwolf's receive audio is clipped or too low, decodes drop badly. It prints audio level hints in its log, so use those to set the sound card input gain before blaming the radio.

  • Administrators

On SmartBeaconing, I'd treat any numbers as a starting point and adjust to your area's channel load. The structure is: slow rate when below the low speed (often a beacon every 20 to 30 minutes when stopped), fast rate at or above the high speed (often one to a few minutes), and in between the rate scales with speed. Corner pegging then triggers a beacon on turns. For walking or cycling, the high-speed threshold should be low. Using a car's numbers on foot means you'll almost never reach the fast rate. For a car, a high speed threshold around highway speeds and a fast rate of a minute or two is a typical shape, but check your local APRS group's recommendations since busy areas ask people to be conservative.

On handhelds: the TH-D74 and TH-D75 have a built-in GPS and TNC, and APRS beaconing and SmartBeaconing are configured in the radio's menus. The FT5D also has built-in GPS and APRS. Read each manual for how the beacon type (automatic, SmartBeaconing, manual), position comment, and path are set, because menu names differ between radios and firmware. Also, handheld transmit power and antenna are usually the limiting factor, not the settings. A handheld at its own height may reach a digi in one place and not another, so a fill-in digi with WIDE1-1 matters a lot.

Weather stations are worth mentioning too. A positional weather report carries wind direction and speed, gust, temperature, rainfall, humidity and pressure in a fixed-format string, and it's normally sent at a modest interval, like every 10 minutes or longer. There's no benefit to beaconing weather faster than the sensors change.

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.