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: sane paths, beacon rates, and a Direwolf iGate/digi next to a TH-D74/D75 or FT5D tracker

ci_cover.jpg

I'm putting together a small APRS setup and want to check my reasoning before I put packets on a shared channel. The plan is a Direwolf box at a fixed location acting as an RX iGate and possibly a fill-in digipeater, plus a handheld (TH-D74/D75 or FT5D) as a mobile tracker. I'd also like to publish an occasional object and a weather station later.

Here is what I understand so far. Please correct anything that's wrong.

Channel basics. In North America APRS runs on 144.390 MHz, 1200 baud AFSK (Bell 202), carried as AX.25 UI frames. Other regions use other frequencies. Europe and Africa use 144.800 and Australia uses 145.175, so check your local band plan. It's a single shared simplex channel with no coordination beyond listen-before-talk and luck, so every unnecessary beacon costs everyone.

Paths. For a mobile, WIDE1-1,WIDE2-1 is the usual starting point. WIDE1-1 lets a nearby fill-in digi pick the packet up, and WIDE2-1 gives one more wide-area hop. A fixed station with good coverage shouldn't need that much. A single WIDE2-1 or even no path is often enough. Long paths like WIDE2-2 stacked on WIDE1-1, or anything above 2 hops, mostly generate duplicate traffic.

Position format. The Kenwood and Yaesu radios use Mic-E for position reports. Mic-E packs the latitude into the destination address field and puts longitude, speed and course in the information field. That makes it compact, which matters at 1200 baud. If you see an odd-looking destination callsign like S5QX4R in a raw packet, that's the latitude, not a real station.

Open questions:

1. What's a reasonable beacon interval for a fixed station versus a moving one? I'd rather not run a fixed station every 30 seconds.

2. Is it better to run the digi and the iGate on the same Direwolf instance, or keep the digi off unless coverage is clearly lacking?

3. For objects and messaging, are there format gotchas worth knowing before I start sending them from the radio?

  • Replies 2
  • Views 29
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On question 2, I'd lean toward not enabling digipeating until you've watched the channel for a while. Run Direwolf as an RX iGate first and look at aprs.fi to see what you're hearing and what path the packets arrive with. If a good wide-area digi already covers the area, a second one mostly adds duplicates and collisions. If the local terrain leaves gaps for handhelds and low-power mobiles, a WIDE1-1 fill-in is the more useful job than a big wide-area digi.

For Direwolf, the iGate part comes down to a few directives in direwolf.conf: your MYCALL, the audio device and modem settings, and the APRS-IS connection. It looks roughly like this:

ADEVICE plughw:1,0
CHANNEL 0
MYCALL N0CALL-10
MODEM 1200
IGSERVER noam.aprs2.net
IGLOGIN N0CALL-10 12345

Use your real callsign and your own APRS-IS passcode, and check the current Direwolf documentation for the exact syntax, because directives and examples change between versions. If you enable the TX iGate side, be careful. A proper TX iGate only sends internet-to-RF packets for stations it has recently heard directly on RF, and mostly for messages. It should not dump general internet traffic onto the channel. Packets whose path contains TCPIP, TCPXX, NOGATE or RFONLY must not be gated to APRS-IS at all.

If you do digipeat, the Direwolf docs include a standard example using the WIDEn-N paradigm with a filter that keeps hop counts sane. Copy from the docs rather than writing the pattern yourself. Most bad digi behavior comes from ad hoc regexes.

Don't skip audio levels. An overdriven receive level or a hot transmit level will cause more lost packets than any path choice. Set the receive level so Direwolf's audio-level numbers sit in a comfortable range, and keep TX deviation reasonable. Too much deviation makes packets less decodable at the other end.

  • Moderators

On beacon rates: for anything that isn't moving, a long interval is fine. Position beacons from fixed stations are commonly sent every 10 to 30 minutes. Weather stations tend to report every 5 to 10 minutes at the short end, and nobody needs weather data faster than the sensor changes. For a tracker, don't use a fixed rate. Use SmartBeaconing.

SmartBeaconing changes the beacon rate with speed and also beacons on turns (corner pegging). The usual parameters are a slow speed and slow rate, a fast speed and fast rate, a minimum turn time, a minimum turn angle, and a turn slope. At highway speed you want a moderate interval, and at walking speed you want it to back off. Parked or stopped, it should drop to the slow rate or stop, because a stationary tracker beaconing every minute is channel pollution. The TH-D74, TH-D75 and FT5D all have some form of smart beaconing, though the menu names and parameter ranges differ. Check each radio's manual rather than assuming the defaults suit your area. Defaults are often more aggressive than a busy channel can bear.

About objects and messaging, a few format details matter:

Objects are position reports about something other than the sender. The object name is exactly 9 characters, padded with spaces, followed by a live marker (*) or a killed marker (_). To remove an object you send it again with the kill marker. Items are similar but use a different leading character and a shorter name field. Objects get re-sent periodically, so use long intervals and delete them when they're no longer valid. Stale objects sitting on aprs.fi are a common annoyance.

Messages use the form :ADDRESSEE:text{msgid. The addressee field is padded to 9 characters, the text is limited to 67 characters, and the message number lets the receiver send an ack. Without a working ack the sender keeps retrying, which is more traffic. Radios can retry on their own, so keep an eye on retry counts if you're testing messaging on a busy channel.

Weather reports use the weather symbol and a data string with wind direction and speed, gust, temperature, rainfall, humidity and pressure. Direwolf can pass weather data from a station to APRS, but check the data-format documentation for your sensor, because units matter. Temperature goes out in degrees Fahrenheit even if your sensor reads Celsius, and rain is in hundredths of an inch.

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.