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

Setting up a Direwolf digi/iGate on 144.390 and getting handheld trackers to behave: paths, beacons, Mic-E, objects

ci_cover.jpg

Starting a thread to compare notes on a common APRS setup: a fixed Direwolf station (sound card or USB audio interface into a mobile or base radio on 144.390 MHz in North America) serving as a digipeater and/or iGate, plus a few handhelds acting as trackers and messaging terminals (Kenwood TH-D74 or TH-D75, Yaesu FT5D). It looks simple, but a lot of channel congestion and "why can't I see my packets on aprs.fi" problems come from a handful of settings.

Frequency first. 144.390 MHz is the APRS channel in the US and Canada. Other regions use different frequencies: 144.800 in Europe and Africa, 145.175 in Australia, and so on. Check your local band plan before you transmit. The channel is 1200 baud AFSK carrying AX.25 UI frames, so there is very little capacity. Every unnecessary beacon or long digipeater path costs everyone else airtime.

A minimal Direwolf starting point looks like this (callsigns, passcode and coordinates are placeholders):

MYCALL N0CALL-10
MODEM 1200
IGSERVER noam.aprs2.net
IGLOGIN N0CALL-10 12345

# Position beacon over RF, via a single hop
PBEACON delay=1 every=30 symbol="digi" overlay=S lat=DD^MM.MMN long=DDD^MM.MMW comment="Fill-in digi" via=WIDE1-1

The audio device, PTT method (serial RTS, GPIO or CM108-style USB) and digipeat rules also need configuring. The Direwolf user guide covers those better than any forum post can. Questions I'd like the thread to cover:

1. For a fixed station, how often is a position beacon actually justified? Every 30 minutes or more is common for something that never moves.

2. What is a sensible digipeater path for a handheld tracker in a mixed urban and rural area: WIDE1-1,WIDE2-1, WIDE2-1 only, or no path?

3. How do you check that RF packets are really reaching the internet? On aprs.fi, the raw packet view shows the path and which station gated the packet into APRS-IS.

4. Where does each of you draw the line on IS-to-RF gating? Direwolf can send internet traffic (such as messages to stations recently heard locally) back to RF, but that should be limited and deliberate.

  • Replies 2
  • Views 39
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On paths, the old RELAY, WIDE and TRACE habits are largely obsolete. The modern New-N approach is built around WIDE1-1 for fill-in digis and WIDE2-N for wide-area digis. A mobile commonly uses WIDE1-1,WIDE2-1, which allows a hop through a fill-in digi and then one wide digi. Larger values like WIDE2-3 or WIDE7-7 tend to make one packet repeat across a huge area and burn channel time. If your fixed station has a good antenna and is already heard by a wide-area digi or an iGate, a short path or even none is often better.

A fixed digi should not beacon often, and it shouldn't beacon via a long path. If you configure it as a fill-in digi, it should answer only to WIDE1-1 and let the wide-area digis handle the rest. Duplicate suppression matters too: digipeaters keep a short memory of packets they've repeated, so the same frame isn't sent again. Reading the DIGIPEAT section and the comments in the sample config is worth the time.

For trackers, SmartBeaconing is the main fix for congestion. It adjusts beacon rate to speed and turning. You set a fast speed with a short interval, a slow speed with a long interval, and corner-pegging parameters (minimum turn time, minimum turn angle, turn slope). That gives you a dense track when you're moving fast or turning and almost nothing when you're stopped. Use it instead of a fixed one-minute beacon, and check that the radio's "stopped" behaviour doesn't leave it transmitting every few minutes in a parking lot.

  • Moderators

On the handheld side, the TH-D74 and TH-D75 have a built-in TNC and GPS, and they can send Mic-E or standard position formats depending on settings. Mic-E packs latitude into the AX.25 destination address and puts longitude, speed and course in the information field. That makes each packet shorter, which is good for a shared 1200 baud channel, and it also carries a status code such as In Service or Off Duty. The FT5D also has built-in APRS. Whichever radio you use, check what it's actually transmitting: look at the raw packet on aprs.fi, not just the radio's menu. If the data type, symbol or comment looks wrong there, other stations will see it wrong too.

Messaging is a different packet type from position reporting. A message has the form :ADDRESSEE:text{msgno, with the addressee padded to nine characters and a message length limit of 67 characters. The receiver replies with an ack, and the sender retries until it gets one. That means a handheld can sit quiet and then burst-retry if the other end isn't hearing it. If nobody replies, check whether the intended station can actually hear a digi that reaches you, and use a short path. The iGate only helps if the recipient is also reachable by RF or is logged in to APRS-IS.

Objects and weather are the two things people most often over-beacon. An object (the ; format with a 9-character name, live * or killed _) is for things like an event location, a net control point or a shelter. Don't re-send it every minute. Beacon it at a sensible interval, kill it when it's done, and avoid creating objects for anything that doesn't need one. A weather station reports temperature, wind, rain and pressure with a position, and ten minutes is a more reasonable interval than every minute or two. Weather packets are bigger, and flooding the channel with them hurts everybody's tracking.

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.