APRS setup sanity check: paths, Mic-E, SmartBeaconing, and getting a Direwolf iGate onto aprs.fi
- Replies 2
- Views 33
- 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 the technical basics of APRS in one thread, because the same questions keep coming up: why a beacon doesn't show on aprs.fi, why a handheld floods the channel, and what the difference is between a digipeater and an iGate. Corrections are welcome. Details vary by region and by network policy, so treat the specifics below as a starting point.
The basics. APRS sends unconnected AX.25 UI frames, 1200 baud AFSK, on a shared simplex frequency. In North America that is 144.390 MHz. Other regions use different frequencies; 144.800 MHz is common in Europe, for example. Because everyone shares one slow channel, every unnecessary packet costs everybody airtime. Most APRS problems come down to too many beacons, paths that are too long, or no one in range to hear you.
Digipeater vs. iGate. A digipeater repeats your packet on RF so more stations can hear it. An iGate listens on RF and forwards valid packets to the APRS-IS internet backbone, and it can also gate messages from the internet back to RF for stations it has recently heard locally. aprs.fi is a viewer for APRS-IS data. If your packet never reaches an iGate, it never appears there, no matter how well it was transmitted. Packets whose path contains markers like TCPIP, TCPXX, NOGATE or RFONLY are not supposed to be gated.
Paths. A common mobile or handheld path is WIDE1-1,WIDE2-1. WIDE1-1 lets a local fill-in digipeater pick you up, and WIDE2-1 lets a wide-area digipeater take one more hop. Long paths, or the old RELAY and TRACE aliases, mostly add duplicate traffic. If you have a good line to an iGate or a wide-area digi, a shorter path such as WIDE2-1 or even a single hop is often enough. Ask local operators what the area expects.
Mic-E. The Kenwood TH-D74 and TH-D75 and the Yaesu FT5D can all send Mic-E position reports. Mic-E packs the latitude into the destination address field and puts longitude, speed and course in the information field. That makes packets short, which matters at 1200 baud. Some decoders show the Mic-E status message (In Service, En Route, Emergency and so on) as a separate field, so don't be surprised if two clients display the same packet differently.
SmartBeaconing. Fixed-interval beacons from a moving station are wasteful. SmartBeaconing adjusts the beacon rate to speed and turning. At low speed it beacons rarely, at high speed more often, and it adds a beacon on sharp turns (corner pegging). The main parameters are the slow and fast speeds, the slow and fast rates, the minimum turn time, the turn angle and the turn slope. Defaults vary by radio and software, so check your menu or config rather than assuming. A stationary station should beacon slowly, with intervals of tens of minutes rather than seconds.
Direwolf. Direwolf can act as a software TNC, a digipeater and an iGate, and it exposes KISS and AGW interfaces for other software. A minimal iGate needs a sound device, a callsign-SSID, a PTT method if you transmit, and an APRS-IS login with your passcode. The relevant config lines look like this:
ADEVICE,MYCALL,MODEM 1200,IGSERVER,IGLOGIN. You can also add aPBEACONline for your own position. Use your own callsign and passcode, and pick an SSID that doesn't collide with anything else you run. Audio level matters: an overdriven input or a badly set transmit level will cost you decodes. Direwolf's own logs show decode counts and can help you tune.Handheld TNCs. The TH-D74 and TH-D75 have a built-in TNC and GPS, and they can be used with an external application through KISS mode. The FT5D also has APRS and GPS features built in. In all of these, check which band is set as the APRS or data band, the packet path, the beacon type and the transmit rate. A radio that's set to beacon every 30 seconds while parked is a classic cause of channel clutter.
Messaging, objects and weather. An APRS message is addressed to a callsign padded to nine characters, and the text is short (up to 67 characters). The message number allows acknowledgment, and a retry that never gets an ack is just more traffic. Objects and items let one station post something else on the map, such as an event or a repeater. An object has a nine-character name and is marked live or killed, and objects should be removed when no longer valid. Weather stations send temperature, wind, rain, humidity and pressure in a standard format, and they usually beacon every 10 to 15 minutes or so. Faster doesn't help anyone.
Questions for the thread: what's your debugging order when a beacon doesn't show on aprs.fi? And what path do you recommend in a sparse area versus a dense one?
Link to comment
https://www.hamradiobase.com/forums/topic/11386-aprs-setup-sanity-check-paths-mic-e-smartbeaconing-and-getting-a-direwolf-igate-onto-aprsfi/Share on other sites