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

Planning an APRS setup on 144.390: handheld trackers, a Direwolf iGate, and getting clean data onto aprs.fi

ci_cover.jpg

I'm sketching an APRS setup and want to check the design before building it. The plan has three parts. The first is a mobile or portable tracker, either a Kenwood TH-D74/TH-D75 or a Yaesu FT5D. The second is a fixed RX/TX iGate and fill-in digipeater running Direwolf on a small Linux box with a sound-card interface. The third is optionally a weather station feeding the same Direwolf instance.

Here is what I understand so far, so correct whatever is wrong.

In North America, APRS runs on 144.390 MHz at 1200 baud AFSK, sent as AX.25 UI frames. Other regions use different frequencies (144.800 MHz in much of Europe, for example), so check your local band plan before programming anything. A packet heard by a digipeater can be repeated over RF. A packet heard by an iGate is passed to the APRS-IS network, and that is where aprs.fi gets its data. So a station showing up on aprs.fi only proves that some iGate heard it, not that your own digipeater chain works.

The questions I'd like input on:

1. For a mobile, is a path of WIDE1-1,WIDE2-1 still the sensible default? Or should it be shorter if the area already has good digipeater coverage?

2. Is SmartBeaconing worth enabling on a handheld, and which parameters matter most? My understanding is that it varies the beacon rate with speed and also sends extra beacons on sharp turns (corner pegging).

3. The D74/D75 transmit position as Mic-E, as I understand it. What is the practical difference compared with a plain uncompressed position packet, and does it change how the station appears on aprs.fi?

4. For the Direwolf box, what is the minimum sane configuration? I'm thinking MYCALL, a MODEM 1200 channel, an IGSERVER login, and a PBEACON with a long interval. What should I leave out so I don't flood the channel?

5. What is the cleanest way to handle objects and messaging? I'd like to send a few objects (a net control point, say) and occasionally exchange short messages with a handheld.

  • Replies 2
  • Views 22
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the RF side, WIDE1-1,WIDE2-1 is the usual compromise for a mobile. Fill-in digipeaters answer to WIDE1-1, and wide-area digipeaters pick up WIDE2-1 after that. If the area is dense with digipeaters, a single hop such as WIDE1-1 alone is kinder to the channel. Long paths like WIDE3-3 or more multiply every packet across a large area, so they are best avoided on a shared 1200 baud frequency.

SmartBeaconing is worth using on a moving station. The key parameters are the fast speed with its fast rate, the slow speed with its slow rate, minimum turn time, minimum turn angle, and turn slope. The idea is frequent beacons at speed and on corners, and sparse ones when slow or stopped. Parked at a trailhead, a fixed-interval tracker sends the same position again and again, and SmartBeaconing avoids that. The defaults are a reasonable starting point, but tune them to how you actually move. Walking, cycling and highway driving want quite different values.

Mic-E packs the latitude into the destination address field and puts longitude, speed and course in the information field, along with a symbol and a standard status code (such as In Service or Emergency). The result is a short packet, which matters at 1200 baud where every extra byte adds airtime. The receiving side decodes it into an ordinary position, so it should look normal on aprs.fi. If you open the raw packet you will see an odd-looking destination callsign, and that is the encoded latitude, not a mistake.

For handhelds, keep the transmit side realistic. A small rubber duck at body height with 5 W or less is a weak APRS station next to a mobile with a roof antenna. Check that the unit is set to 1200 baud for 144.390 and not a 9600 mode, and that the GPS has a fix before blaming the path. Also set the beacon comment and status text to something short. Long comments make longer packets, and that load adds up.

  • Administrators

For the Direwolf box, the minimum is small. Define the audio device, set MYCALL to your callsign with an SSID, use MODEM 1200 on the channel, and add an IGSERVER entry with an IGLOGIN using your callsign and APRS-IS passcode. If it is also a digipeater, add a DIGIPEAT line, and only enable the aliases you actually want it to answer. A fixed station can beacon rarely. Every 30 minutes or so is plenty, because it is not moving. Check the Direwolf documentation for the exact PBEACON and IGTXVIA syntax, since the option names matter.

An RX-only iGate is a perfectly good first step. Turn on RF-to-IS gateway behavior and confirm that packets reach the Internet before enabling any IS-to-RF gating. Gating internet traffic back to RF should be limited to messages for stations you have recently heard locally, so you don't push internet traffic onto the channel. Leaving it off is fine at first.

aprs.fi's raw packet view is the best debugging tool. In the path you will see which iGate passed the packet to the internet, usually shown with a qAR or similar q-construct followed by its callsign. An asterisk on a digipeater callsign in the path means that digipeater actually repeated the packet. Together these tell you whether your packet was digipeated, gated, or both.

For weather, the station sends a weather symbol with wind direction and speed, gust, temperature, rain, humidity and barometric pressure in the standard formats. Direwolf doesn't read the sensors itself. You need a separate program that produces the APRS weather data, and you must set the beacon interval sensibly, since every report is airtime.

Objects start with a semicolon, a nine-character padded name, and a live marker (an asterisk). A killed object uses an underscore. Messages carry the addressee in a nine-character field, then the text, then an optional message number used for acknowledgements. Text is limited to 67 characters, so keep messages short. Retries are automatic until an ack arrives, which is another reason not to send long chatty messages over a busy RF channel. Test messaging between two radios of your own before relying on it, and note that different handhelds handle message acks and group messaging a little differently.

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.