APRS on 144.390: choosing paths, iGate settings, beacon rates and Mic-E vs. Direwolf for a tracker and fixed station
- Replies 2
- Views 45
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
This thread is for pulling together practical settings for a typical APRS setup: a Direwolf-based fixed station (RX iGate, possibly a fill-in digipeater) and handheld or mobile trackers such as the Kenwood TH-D74/TH-D75 or Yaesu FT5D. The same few questions come up again and again, so here is a baseline to argue with.
Frequency and modulation. In North America APRS lives on 144.390 MHz: FM, 1200 baud Bell 202 AFSK, AX.25 UI frames. Other regions use different frequencies, for example 144.800 MHz across Europe and Africa, so check your local band plan before programming memories. Because everyone shares one simplex channel, every unnecessary packet costs everybody else airtime. Most APRS "problems" are really channel-loading problems.
What the network pieces do. A digipeater repeats packets on RF according to the path in the header. An iGate bridges RF to the internet (APRS-IS), which is what puts your position on aprs.fi. An RX-only iGate is perfectly useful and carries fewer obligations. A TX-capable iGate also sends internet-originated messages back to RF, but only for stations it has recently heard locally on RF, wrapped in a third-party header. Done carelessly it adds traffic, so it is worth enabling only when you have good coverage and a clean transmit chain.
A minimal Direwolf starting point (callsign, passcode and coordinates are placeholders):
The passcode is derived from the callsign, so use the one for your own call. Leaving out any transmit-to-RF directives keeps this receive-only for the internet side. Direwolf prints an audio level for each decoded frame. Use that readout rather than guessing at the receive volume from the radio's speaker or data port. The Direwolf documentation suggests aiming for a moderate level, not a clipped one.
Paths. For mobiles, WIDE1-1,WIDE2-1 is the common default in the US, and it works well when fill-in digis answer to WIDE1-1. Long paths like WIDE7-7 mostly spread one packet across a whole region. A fixed station with a good antenna often does fine with WIDE2-1 or even no path, because an iGate or wide-area digi can hear it directly.
Mic-E and SmartBeaconing. Mic-E packs latitude into the destination address field and puts longitude, speed and course in the information field. That makes frames short, which matters at 1200 baud. It also carries one of the standard Mic-E status codes (In Service, En Route, Emergency and so on). SmartBeaconing varies the beacon interval with speed and adds extra beacons when your heading changes by more than some threshold (corner pegging). The usual parameters are fast speed/rate, slow speed/rate, minimum turn angle, turn slope and minimum turn time. The goal is to send fewer packets when you are parked or crawling and enough on curves to keep the track on aprs.fi from cutting corners.
Questions to get started: what paths and beacon intervals are you using for tracking versus fixed stations? How do you handle weather stations and objects without flooding the channel? And what do you check first when a station is heard locally but never shows up on aprs.fi?
Link to comment
https://www.hamradiobase.com/forums/topic/10888-aprs-on-144390-choosing-paths-igate-settings-beacon-rates-and-mic-e-vs-direwolf-for-a-tracker-and-fixed-station/Share on other sites