APRS 144.390 setup notes: paths, Mic-E, SmartBeaconing, Direwolf iGate and checking results on aprs.fi
- Replies 2
- Views 41
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Admin_Lee 1 post
This thread is for sorting out the practical parts of APRS that tend to get confused when someone moves from "my radio beacons" to "I'm running infrastructure." It covers the RF side (144.390 MHz in North America), what the handheld does for you, and what a Direwolf box adds. Please correct anything that doesn't match your region or firmware.
The basics. APRS rides on AX.25 unnumbered information (UI) frames, sent as 1200 baud AFSK (Bell 202-style) on the standard simplex channel. That channel is 144.390 MHz in North America. Other regions use other frequencies, for example 144.800 MHz in much of Europe and Africa, and 145.175 MHz in Australia. Check your local band plan before programming a radio. Because every station shares one channel and there is no collision avoidance beyond listen-before-talk, airtime is the scarce resource. Most of the tuning advice below comes down to sending fewer, more useful packets.
Paths. A UI frame carries a destination field, a source callsign and up to eight digipeater hops. A fill-in digipeater answers to WIDE1-1. Wide-area digipeaters answer to WIDE2-n. The usual guidance for mobile stations is WIDE1-1,WIDE2-1, which gives one fill-in hop and one wide hop. Fixed stations with good coverage often go direct or use a single hop. Long paths like WIDE5-5 multiply every packet across the whole area and are widely discouraged. If you can see a digipeater directly, you rarely need more than one or two hops.
Mic-E versus plain position reports. Mic-E packs latitude into the destination address field and puts longitude, speed and course in the information field, plus a status code such as In Service or Emergency. It's compact, which is why many handhelds and mobile rigs use it for tracking. Plain (uncompressed) position reports are longer but human-readable, and they are what you see on most fixed stations, objects and weather reports. If a tracker is doing Mic-E and you decode it on a laptop, a destination callsign that looks like gibberish is expected.
Handhelds. The Kenwood TH-D74 and TH-D75 have a built-in GPS, a TNC and APRS support, and they can also be used as a KISS TNC over USB or Bluetooth. The Yaesu FT5D also has built-in GPS and APRS. Details such as beacon types, packet formats and data rates differ by model and firmware, so check the manual for what your unit actually sends. A common mistake with all of them is leaving the beacon on a fixed interval while standing still. That fills the channel with duplicate positions.
SmartBeaconing. This is the usual fix for that problem. It beacons often when you are moving fast, rarely when slow or stopped, and sends an extra packet when your heading changes enough. The main parameters are:
Defaults suit highway driving. They may be too chatty for walking or cycling, and too slow for tight city streets, so adjust them to how you actually travel.
Direwolf as TNC, digipeater and iGate. Direwolf is a software TNC. A sound card or USB audio interface connects to the radio, and Direwolf handles the modem, KISS and AGW interfaces, digipeating and the iGate function. A minimal config has these pieces, with placeholder values here:
Set levels carefully. Over-driven receive audio is a frequent cause of poor decoding, and the audio levels Direwolf reports at startup are a good starting point. Also keep in mind that gating RF to the internet requires a valid login and that iGates should only pass traffic appropriately. Many operators begin with receive-only (RF to IS) before enabling any transmit gating.
Objects, messages, weather. An object lets one station report a position for something else, such as an event, a repeater or a storm. It has a name of up to nine characters and is marked live or killed. Messages are addressed to a callsign padded to nine characters, with a message number so the other end can acknowledge. Weather reports use a weather symbol and fixed fields for wind, gust, temperature, rain, humidity and barometric pressure, and they should go out at a modest interval.
Questions to get started: What path do you use on a mobile, and why? Has anyone tuned SmartBeaconing for walking or cycling? And what's your preferred way of checking that an iGate is actually working?
Link to comment
https://www.hamradiobase.com/forums/topic/11199-aprs-144390-setup-notes-paths-mic-e-smartbeaconing-direwolf-igate-and-checking-results-on-aprsfi/Share on other sites