APRS on 144.390: sorting out paths, iGates, Mic-E and SmartBeaconing across a handheld, Direwolf and aprs.fi
- Replies 2
- Views 43
- 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 is a technical thread on how the pieces of APRS fit together, since the same questions come up repeatedly. A station beacons a position or message as an AX.25 UI frame at 1200 baud AFSK on 144.390 MHz (North America). A digipeater may repeat it, and an iGate may pass it into APRS-IS, the internet backbone. Sites like aprs.fi are a window onto the APRS-IS data stream. They are not the radio network itself.
Start with the frequency. 144.390 MHz is the North American APRS channel. Other regions use other frequencies, for example 144.800 MHz in Europe and Africa. Check your local band plan and set the radio before travelling, otherwise the radio will beacon into the void and never hear local traffic.
On the radio side, the Kenwood TH-D74 and TH-D75 have a built-in TNC and GPS, so they can beacon with no extra hardware. They also offer a KISS mode, so the radio can act as a TNC for software on a phone or PC. The Yaesu FT5D also has integrated GPS and APRS. Details such as supported baud rates, path presets and beacon options vary by model and firmware, so check the current manual rather than relying on what someone remembers.
The beacon path decides how far a packet travels and how much channel it burns. A common mobile setting is WIDE1-1,WIDE2-1. WIDE1-1 lets a fill-in digi pick up a low-power handheld, and WIDE2-1 allows one more hop through a wide-area digi. Long paths such as WIDE1-1,WIDE2-2 or larger multi-hop paths flood a shared 1200 baud channel quickly. Fixed stations that are already well heard should usually use a shorter path, or none.
Mic-E is the position format most Kenwood and Yaesu radios use for mobile tracking. It packs latitude into the destination address field and puts longitude, speed and course in the information field. This makes packets short, which matters on a slow channel. It also means that if your decoder shows odd destination calls like "T5SQPX", that is normal and not corruption.
The questions for discussion:
1. For a mobile tracker, what SmartBeaconing settings (fast/slow speed, fast/slow rate, minimum turn time, turn angle, turn slope) give a clean track without hammering the channel?
2. For a Direwolf station used as a digipeater and iGate, what is the sanest way to avoid gating loops and duplicates?
3. When your beacon shows up on aprs.fi but nobody can message you, where do you look first?
Weather stations, objects and bulletins can follow later in the thread.
Link to comment
https://www.hamradiobase.com/forums/topic/11061-aprs-on-144390-sorting-out-paths-igates-mic-e-and-smartbeaconing-across-a-handheld-direwolf-and-aprsfi/Share on other sites