APRS on 144.390: how the pieces fit (handheld, digipeater, Direwolf iGate, aprs.fi) and what to tune first
- Replies 2
- Views 37
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Mod_Mike 1 post
I'm putting together a mental model of a basic North American APRS setup and want to check it against what others know. The chain as I understand it:
Tracker or handheld (Kenwood TH-D74/TH-D75, Yaesu FT5D, or a GPS plus TNC) sends an AX.25 UI frame on 144.390 MHz, 1200 baud AFSK. A digipeater may repeat it based on the path. An iGate hears it on RF and forwards it to the APRS-IS servers over the internet. Sites like aprs.fi read from APRS-IS and plot it.
Where I'd like input is the details that make or break this in practice:
1. Paths. In North America, WIDE1-1,WIDE2-1 is the usual starting point for mobiles. WIDE1-1 lets fill-in digipeaters pick up a low-power handheld, and WIDE2-1 gives one more hop from a wide-area digi. Long paths like WIDE2-2 or more only multiply the traffic on a single shared channel. Fixed stations in a well-covered area often do fine with a single hop or even no path.
2. Mic-E vs. plain position. 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 on a 1200 baud channel shared by everyone. Many radios, including the Kenwood and Yaesu handhelds, can send Mic-E. Plain uncompressed positions are longer but easier to read in a raw packet log.
3. SmartBeaconing. Instead of a fixed interval, the beacon rate follows speed and heading changes. Typically you set a low speed and slow rate (stopped or walking), a high speed and fast rate (driving), and corner-pegging values (turn angle, turn slope, minimum turn time) that trigger an extra beacon when your heading changes. The goal is good tracks without flooding the channel while parked. The TH-D74/TH-D75 and many other radios expose these parameters, and Direwolf has a SMARTBEACONING config line for the same purpose.
4. Direwolf as TNC and iGate. Direwolf is a software TNC that decodes audio from a sound card. It can run a digipeater and an iGate, and can talk KISS or AGW to other software. A minimal receive-only iGate config looks roughly like this (placeholders only):
The login needs a valid APRS-IS passcode for your callsign, and the SSID on the iGate should be unique so it doesn't collide with your handheld.
5. Objects and messages. Objects are packets that report a position for something other than the sending station (an event, a net control point, a weather alert area). The name is padded to nine characters, and the object stays on the map as long as it is re-sent or until it is killed. Messages go to an addressee padded to nine characters and carry a message number so the recipient can ack. For example,
:N0CALL-7 :hello{12.Questions: what are sensible starting values for SmartBeaconing on a handheld versus a car? Should a first-time Direwolf iGate stay receive-only? And is there a good way to sanity-check that my packets are actually reaching aprs.fi rather than just showing up locally?
Link to comment
https://www.hamradiobase.com/forums/topic/11446-aprs-on-144390-how-the-pieces-fit-handheld-digipeater-direwolf-igate-aprsfi-and-what-to-tune-first/Share on other sites