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 412.9 km/s
Aurora 1
Updated 14:00 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: choosing paths, iGate settings, beacon rates and Mic-E vs. Direwolf for a tracker and fixed station

ci_cover.jpg

This thread is for pulling together practical settings for a typical APRS setup: a Direwolf-based fixed station (RX iGate, possibly a fill-in digipeater) and handheld or mobile trackers such as the Kenwood TH-D74/TH-D75 or Yaesu FT5D. The same few questions come up again and again, so here is a baseline to argue with.

Frequency and modulation. In North America APRS lives on 144.390 MHz: FM, 1200 baud Bell 202 AFSK, AX.25 UI frames. Other regions use different frequencies, for example 144.800 MHz across Europe and Africa, so check your local band plan before programming memories. Because everyone shares one simplex channel, every unnecessary packet costs everybody else airtime. Most APRS "problems" are really channel-loading problems.

What the network pieces do. A digipeater repeats packets on RF according to the path in the header. An iGate bridges RF to the internet (APRS-IS), which is what puts your position on aprs.fi. An RX-only iGate is perfectly useful and carries fewer obligations. A TX-capable iGate also sends internet-originated messages back to RF, but only for stations it has recently heard locally on RF, wrapped in a third-party header. Done carelessly it adds traffic, so it is worth enabling only when you have good coverage and a clean transmit chain.

A minimal Direwolf starting point (callsign, passcode and coordinates are placeholders):

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

IGSERVER rotate.aprs2.net
IGLOGIN N0CALL-10 00000

PBEACON delay=1 every=30 sendto=IG symbol="igate" overlay=R lat=DD^MM.MMN long=DDD^MM.MMW comment="RX iGate"

The passcode is derived from the callsign, so use the one for your own call. Leaving out any transmit-to-RF directives keeps this receive-only for the internet side. Direwolf prints an audio level for each decoded frame. Use that readout rather than guessing at the receive volume from the radio's speaker or data port. The Direwolf documentation suggests aiming for a moderate level, not a clipped one.

Paths. For mobiles, WIDE1-1,WIDE2-1 is the common default in the US, and it works well when fill-in digis answer to WIDE1-1. Long paths like WIDE7-7 mostly spread one packet across a whole region. A fixed station with a good antenna often does fine with WIDE2-1 or even no path, because an iGate or wide-area digi can hear it directly.

Mic-E and SmartBeaconing. 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 at 1200 baud. It also carries one of the standard Mic-E status codes (In Service, En Route, Emergency and so on). SmartBeaconing varies the beacon interval with speed and adds extra beacons when your heading changes by more than some threshold (corner pegging). The usual parameters are fast speed/rate, slow speed/rate, minimum turn angle, turn slope and minimum turn time. The goal is to send fewer packets when you are parked or crawling and enough on curves to keep the track on aprs.fi from cutting corners.

Questions to get started: what paths and beacon intervals are you using for tracking versus fixed stations? How do you handle weather stations and objects without flooding the channel? And what do you check first when a station is heard locally but never shows up on aprs.fi?

  • Replies 2
  • Views 45
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the "heard locally but not on aprs.fi" question, read the raw packet rather than guessing. aprs.fi's raw packet view shows the path and the q-construct the server appended. A qAR entry followed by an iGate callsign means that iGate received it off RF and could transmit. qAO indicates an RX-only gateway. If nothing shows at all, work through the basics. Does your frame actually decode at the iGate, or only at your own radio? Is the destination field legal? Does the path contain TCPIP or NOGATE, which tell iGates not to pass it? Is the iGate's APRS-IS connection even up?

For beacon timing, fixed stations sitting in the same spot rarely need to transmit more often than every 10 to 30 minutes. If you are on a digipeated path, a once-a-minute beacon from a house is just noise to everyone else. Weather stations deserve the same restraint, since a packet every few minutes on RF is wasteful when the iGate can see the data. If you have internet at the station, send the frequent weather updates to APRS-IS only, and keep a slow RF beacon for the benefit of people with no network access.

Weather reports are fixed-format text. The wind direction field is c, speed s, gust g, temperature t in degrees Fahrenheit, rain fields r, p and P, humidity h (00 means 100%) and barometric pressure b in tenths of hPa. Many first-time weather setups go wrong with the units, so check them before blaming the radio.

  • Moderators

On the handheld side, the main thing to verify on the TH-D74/D75 and FT5D is which band and function the APRS data actually uses. These radios can run APRS on one side while you listen to voice on the other, but the menu setting for the APRS data band decides where beacons go out, and it is easy to leave it pointed at the wrong frequency. Also confirm that the radio's APRS frequency is 144.390 (or your region's equivalent) and not a voice channel next to it. Both families support 1200 and 9600 bps APRS, but 9600 is not what the typical wide-area network listens on. Stick to 1200 for normal use unless you know your local network runs otherwise.

Check the position and comment fields too. A beacon with a long comment is a long packet at 1200 baud, so keep the text short and the symbol sensible. For messaging, remember that the addressee field is padded to nine characters, the text is limited to 67 characters, and a message ID after { is what triggers the ack and retry logic. A message to a callsign-SSID has to match the SSID exactly, and a message to an operator sitting at another SSID will just retry until it times out.

Objects work the same way. An object has a name of up to nine characters, a live/killed flag, a timestamp and a position, and it is sent under your callsign as the originator. They are good for events, repeaters, or temporary things like a shelter or a net control point, but each object adds a periodic transmission. If you create one, send it with a slowing retransmit schedule if the software supports it and kill it when the event ends, or the channel will keep carrying an object nobody needs anymore.

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.