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 handheld tracker and a Direwolf iGate on 144.390: paths, Mic-E, SmartBeaconing and objects

ci_cover.jpg

I'm planning an APRS setup with two parts and want to sanity-check the design before I put anything on the air.

Part one is a mobile tracker. I'll use a handheld with a built-in GPS and TNC, either a Kenwood TH-D74/TH-D75 or a Yaesu FT5D, in a vehicle. Part two is a fixed receive-only iGate at home. It would be a Raspberry Pi-class box running Direwolf with an RTL-SDR or a soundcard-connected radio on 144.390 MHz. I'm in North America, so 144.390 is the channel. Other regions use different frequencies, so check your local band plan.

Here is what I'm trying to decide:

1) Path. I know WIDE1-1,WIDE2-1 is the usual mobile default. Is there a good reason to change it, and what should the fixed station use?

2) Beaconing. Is SmartBeaconing worth configuring on the radio, or should I use a fixed interval? 1200 baud is a shared channel and I don't want to be the person clogging it.

3) Mic-E versus plain position packets. The handhelds seem to default to Mic-E. Do I lose anything by leaving it alone?

4) Messaging and objects. I'd like to send short messages through the iGate and eventually place an object for a club event. What are the gotchas?

For the iGate, this is the minimal Direwolf config I intend to start with. The callsign and passcode are placeholders, and I'm leaving it RX-only (no IGTXVIA) for now:

ADEVICE plughw:1,0
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=42^37.14N long=071^20.83W comment="RX-only iGate"

Does anything there look wrong or missing? I'd also like to know how you verify that a new iGate is actually working, beyond "no errors in the log."

  • Replies 2
  • Views 34
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the mobile side:

Path: WIDE1-1,WIDE2-1 is still a sensible mobile default. The WIDE1-1 hop lets a fill-in digipeater (often a home or low-power station) pick you up. The WIDE2-1 hop lets a wide-area digipeater carry you farther. If your area has dense digipeater coverage, a single WIDE2-1 may be enough. Avoid long paths like WIDE3-3. Each extra hop multiplies the airtime your packet uses across everyone's coverage area. Your fixed station barely needs a path. An iGate that hears the RF directly doesn't need to be repeated, and a stationary beacon for a receive-only iGate can use an empty path or a single hop.

SmartBeaconing: yes, use it if the radio offers it. The idea is to beacon more often when you're moving fast or turning, and slowly when you're slow or stopped. The parameters are generally fast speed, fast rate, slow speed, slow rate, minimum turn angle, turn slope, and minimum turn time. As a rough starting point, a beacon every minute or two at highway speed and every 20 to 30 minutes when parked is reasonable. Tune from there against how the track looks on aprs.fi. Menu names and defaults differ between the TH-D74/D75 and FT5D, so check each radio's manual rather than assuming the same options.

Mic-E: you lose nothing by leaving it on for tracking. It packs latitude into the destination address field and carries longitude, speed and course in the information field. That makes packets short, which is good for a 1200 baud channel. It also carries the Mic-E message status codes (such as In Service or Emergency), which the handhelds expose as a status setting. Keep your comment text short. A long comment makes every beacon longer for no benefit.

One more thing: set the correct SSID and the right symbol (car, handheld and so on). A mis-set symbol is the most common reason a mobile station looks wrong on the map.

  • Moderators

On the iGate, objects and messaging:

Your Direwolf config is basically right. The key points are a valid IGLOGIN, which requires the correct passcode for the callsign (without the SSID), and an IGSERVER for your region. The PBEACON line is the part people forget. Without it your iGate may be working but not appear on the map. Also check that the PTT isn't configured if you're receive-only, and watch the audio level Direwolf reports. Levels that are very low or constantly clipping will hurt decoding. If you later enable transmit gating, think carefully about it. A TX iGate should only gate messages for stations it has recently heard locally, and a badly configured one can flood the channel.

To verify, look at your iGate callsign on aprs.fi and watch the raw packets. You should see your own beacon appear from the APRS-IS side. Then have a mobile transmit and look for it in the feed with your iGate in the path (for example qAR or qAO in the raw header, followed by your callsign). That shows your iGate heard it off RF and passed it on.

Messaging: messages go to a 9-character padded addressee, include a message number, and expect an ack from the recipient. Keep text short (the format allows about 67 characters). If the recipient is only reachable via the iGate on RF, the delivery depends on whether a TX iGate has recently heard them locally. Don't assume a message will arrive just because you see it on APRS-IS.

Objects: an object has a name of up to nine characters and is marked live or killed. Whoever is beaconing the object is the one keeping it alive, so pick a sensible interval and remember to kill it when the event ends. An object that keeps repeating long after the event is just noise on the map. If you add a weather station later, keep the same restraint. Every five to ten minutes is plenty for most weather reports, and the weather symbol with correctly formatted wind, temperature, rain and pressure fields is what makes aprs.fi display it properly.

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.