APRS on 144.390: Direwolf iGate/fill-in digi plus handheld tracking with SmartBeaconing, paths, and messaging
- Replies 2
- Views 46
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
I'd like to collect practical notes on a common APRS setup: a fixed Direwolf station at home acting as an iGate (and possibly a fill-in digipeater), plus a handheld or mobile radio such as a Kenwood TH-D74/TH-D75 or Yaesu FT5D doing tracking and messaging. Most problems with this setup come from a handful of settings, so here is the basic picture, then some questions.
The RF side. In North America, APRS runs on 144.390 MHz at 1200 baud AFSK (Bell 202), carrying AX.25 UI frames. Other regions use different frequencies. Europe and Africa are generally on 144.800, and Australia and New Zealand use 145.175 and 145.225. Check your local band plan before programming a radio. The channel is shared and simplex, with CSMA-style listen-before-talk, so every extra beacon costs everyone airtime. That is why beacon rate and path length matter.
Paths. The usual mobile or handheld path in the "new-N" model is WIDE1-1,WIDE2-1. WIDE1-1 lets a fill-in digi near you pick up a low-power signal. WIDE2-1 lets a wide-area digi carry it one more hop. Long paths such as WIDE5-5 mostly create duplicate traffic. A fixed station with good coverage often does better with a single hop or no digipeating at all. If your own iGate hears you directly, the packet reaches APRS-IS without any digipeater.
Direwolf as an iGate. Direwolf is a software TNC and sound-card modem. It can decode, digipeat, iGate, and talk to other software over KISS or AGWPE. A minimal receive-only iGate config looks roughly like this (placeholders, not real values):
The passcode is the APRS-IS passcode derived from your callsign, and the server should be the regional rotate for your area. Using sendto=IG keeps the station beacon on the internet side only, with no RF transmission. For a TX iGate or digipeater you also need PTT control, a sensible via path on the beacon, and a deliberate decision about what gets gated from the internet to RF. A TX iGate should only pass messages to stations it has recently heard on RF, not general traffic. Otherwise it floods the channel.
Handhelds. The TH-D74, TH-D75, and FT5D all have a built-in GPS and APRS function, and both Kenwoods can also act as a KISS TNC. They typically encode position as Mic-E. Mic-E packs latitude into the destination address field and puts longitude, speed, course, and a status code into the information field, so a position report is short. A shorter frame is a shorter transmission on the shared channel. Menu names and supported baud rates differ by model and firmware, so check the manual for your radio. For 144.390, use 1200 baud.
SmartBeaconing. A fixed interval is wasteful. At 5 km/h you don't need a position every 60 seconds, and at highway speed once a minute is too coarse. SmartBeaconing adjusts the rate by speed and sends extra beacons when you turn. The main parameters are:
Defaults are usually a reasonable start. If you see clusters of points in town, raise the minimum turn time or angle before shortening anything.
Weather, objects, messaging. A weather station sends a position report with the weather symbol and fields such as wind direction (c), wind speed (s), gust (g), temperature in Fahrenheit (t), rain (r, p, P), humidity (h), and barometric pressure (b). Ten minutes or longer between reports is plenty. Objects (the ';' packet type) let one station place a named item on the map, such as an event or a shelter. The name is padded to nine characters, and '*' marks it live while '_' kills it. Messages use the ':' type, with the addressee padded to nine characters, text limited to 67 characters, and an optional message number after '{' for acknowledgement.
To verify things, look up your callsign-SSID on aprs.fi and open the raw packets view. The path shows whether you were heard directly or via digipeaters, and which iGate injected the packet. If your handheld's packets never appear, the problem is usually RF coverage, deviation or audio level, or a bad path rather than the radio.
Questions for everyone: what path do you recommend for a handheld that is mostly stationary? And how do you decide between RX-only iGate, TX iGate, and fill-in digi when an area already has some coverage?
Link to comment
https://www.hamradiobase.com/forums/topic/11117-aprs-on-144390-direwolf-igatefill-in-digi-plus-handheld-tracking-with-smartbeaconing-paths-and-messaging/Share on other sites