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: tuning a tracker, a Direwolf iGate and a handheld so they don't clog the channel

ci_cover.jpg

I'd like to compare notes on how people set up the pieces of an APRS system so they work together instead of fighting over one 1200 baud channel. In North America the shared frequency is 144.390 MHz, using AFSK (Bell 202 tones) carrying AX.25 UI frames. Other regions use different frequencies, such as 144.800 in much of Europe and 145.175 in Australia, so confirm your local APRS frequency before transmitting.

The pieces I'm interested in:

1. Handheld and mobile trackers. The Kenwood TH-D74 and TH-D75 have a built-in GPS and TNC, and the Yaesu FT5D has built-in GPS and APRS. Both families send position beacons with no external hardware. Most radios of this type default to Mic-E encoding for position. Mic-E packs latitude into the destination address field and puts longitude, speed and course in the information field. That makes packets shorter than plain-text position reports, which matters when every packet takes airtime on a shared channel.

2. Beacon timing. A fixed beacon every 3 minutes from a moving car is wasteful when you're stopped at a light and too slow when you're turning through switchbacks. SmartBeaconing varies the rate with speed and adds extra beacons when your heading changes. The parameters are fast speed and fast rate, slow speed and slow rate, minimum turn time, minimum turn angle and turn slope. The defaults suit a car, and walking or cycling needs a much lower speed threshold and a longer slow rate.

3. Digipeater path. The usual advice is to keep it short. For many areas, WIDE1-1,WIDE2-1 is the standard for mobiles, and some regions recommend just WIDE2-1 where fill-in digipeaters are rare. Avoid long paths such as WIDE7-7. Each extra hop multiplies the traffic that the whole channel has to carry.

4. A Direwolf iGate or digipeater. Direwolf is a software TNC that uses a sound card to decode and encode 1200 baud packets. It can also run as a digipeater and an RF-to-Internet gateway to APRS-IS. A rough skeleton of the relevant direwolf.conf lines looks like this. It is not a complete config, so check it against the Direwolf documentation for your version:

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

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 iGate"

Replace the callsign, passcode and coordinates with your own. Use a sensible beacon interval for a fixed station, because 30 minutes is plenty. Think carefully before enabling Internet-to-RF gating (IGTXVIA and related settings). RX-only is the safer default, and a licensed operator should understand the local rules and the traffic load before turning on transmit.

5. Seeing the result. aprs.fi is useful for checking whether your packet reached an iGate and was posted to APRS-IS. If your station appears there with a raw packet, you know at least one iGate heard it. If it doesn't, either nobody was in range or something is wrong with your path or settings. Note that purely local RF-to-RF digipeating is invisible there unless an iGate also heard it.

6. Beyond position reports. APRS also carries weather reports (wind, gust, temperature in Fahrenheit, rain, humidity, barometric pressure), objects and items (for example a net control point or a marked hazard), and messages. A message is addressed to a callsign padded to 9 characters, with a message number for acknowledgement. Objects use a 9-character name and a live or killed marker.

Questions for the thread: What beacon rate and path do you use for a fixed station versus a mobile? How have you handled Mic-E versus uncompressed position when decoding on other software? And has anyone found a reliable way to confirm that a message was acknowledged end-to-end when using a handheld in a fringe area?

  • Replies 2
  • Views 117
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On the handhelds, treat the built-in TNC as a convenience and not as a replacement for planning your path. On a TH-D74 or TH-D75 the APRS settings (beacon type, interval, path, comment, status text) are separate from the voice settings, so it's easy to leave a default path on that's far too aggressive for a dense area. Check what the radio is actually sending, not just what the menu implies. A Mic-E packet decoded on aprs.fi or on another radio's display will show the path, so you can verify it.

For SmartBeaconing, tune it to how you move. A car can use a fast speed in the highway range with a rate of a minute or two, and a slow rate of 10 to 30 minutes when stopped. Walking at 3 to 5 km/h will probably never reach those thresholds, so the radio stays on the slow rate and you lose track detail. Lowering the speed thresholds, or using a fixed interval of a few minutes for hiking, gives a cleaner track. Also be careful with corner pegging. A small minimum turn angle or short turn time on a twisty road produces a lot of packets that add little.

On the FT5D side, check the manual for its APRS beacon and data-band behavior. It matters which band is set to transmit data and whether the radio will still receive voice on the other band while beaconing, since that differs between radio models and can surprise you in a car.

  • Moderators

For the iGate, I'd suggest getting RX-only working first, because most of the usefulness comes from that part. Get clean audio into the sound card with no clipping. In Direwolf the decode statistics show how many packets are being heard, and an overdriven input can look like "no packets" or lots of garbled ones. Set the receive level so that decoded packets show a healthy audio level, then check the same packets on aprs.fi for your station and for a nearby one to confirm your uploads are showing up.

If you transmit, set the transmit audio level and PTT carefully. An overdeviated 1200 baud signal decodes worse, not better, and a stuck PTT on a shared simplex channel will upset everyone nearby. Ideally check deviation with a service monitor or at least with another receiver. If you run a digipeater, limit it to what the area needs. A fill-in digipeater that answers WIDE1-1 and drops anything with big hop counts is more useful than a wide-area one that repeats everything.

On weather: the packet encodes temperature in Fahrenheit regardless of your local units, so make sure your software converts correctly. A weather station needs a real location and a sensible interval, such as 5 to 10 minutes, and not a packet every 30 seconds. For objects, remember that an object stays in the network only as long as someone keeps sending it, so a live object needs periodic retransmission and a killed object needs a proper kill packet. Otherwise it lingers on maps.

On the acknowledgement question: messaging works with a message number and an ack from the recipient. If you don't see the ack, you don't know whether the message or the ack was lost. So the sender retries a few times with backoff, and some messages arrive twice. Keep messages short (the practical limit is 67 characters) and don't count on delivery for anything urgent.

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.