Setting up APRS properly on 144.390: Direwolf iGate, handheld trackers, Mic-E, SmartBeaconing and what to put on the channel
- Replies 2
- Views 11
- 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 want to collect the practical parts of APRS in one thread, because the same questions keep coming up: why a position doesn't show on aprs.fi, why messages don't get acknowledged, and why the local channel is full of packets nobody can use. Please correct anything below that doesn't match how your region runs it.
The basics. APRS is unconnected AX.25 (UI frames) at 1200 baud AFSK, Bell 202 tones, on FM. In North America the shared frequency is 144.390 MHz. Other regions use different frequencies, for example 144.800 MHz across much of Europe and Africa, with others elsewhere, so check your local band plan before you transmit. Every station shares one simplex channel. That channel has very little capacity, so most of the etiquette is about not wasting airtime.
The chain. A tracker sends a packet. A digipeater may repeat it, based on the path in the header. An iGate that hears it on RF can forward it to APRS-IS over the internet, and sites like aprs.fi show what APRS-IS received. If your position isn't on the map, either no iGate heard you, or an iGate heard you but dropped the packet, for example because it was a duplicate or the path was unsuitable. Aprs.fi shows what the network heard, not what your radio sent, so the raw packet view is the first place to look when debugging.
Paths. A common mobile path is WIDE1-1,WIDE2-1. WIDE1-1 lets a fill-in digi pick the packet up first, and WIDE2-1 lets a wide-area digi carry it further. Many areas discourage long paths such as WIDE2-2 or higher, or cap them. A fixed home station usually needs a short path such as WIDE1-1, or no digipeating at all if an iGate hears it directly. Ask your local APRS group what the region recommends before you copy a path from a forum post.
Direwolf. Direwolf is a software TNC and can act as a digipeater, an iGate, a beacon source and a KISS or AGWPE server for other software. A minimal iGate configuration looks roughly like this, with placeholders you'll need to replace:
Check the Direwolf documentation for your platform's audio device names and PTT options. The passcode comes from your own callsign, so don't paste someone else's. Set audio levels carefully. If Direwolf's receive level is clipped or very low, you will decode fewer packets, and a transmit level that over-deviates will splatter and sound bad to every other decoder on the channel.
For discussion: what are people using for the RF side of a home iGate? A dedicated radio, an RTL-SDR in receive-only mode, or a TNC on a separate box?
Handhelds. The Kenwood TH-D74 and TH-D75 and the Yaesu FT5D all have built-in APRS and GPS, so they can send beacons and handle messages without an external TNC. Menu names and defaults differ between models and firmware versions, so use the manual for yours. The points that matter on any of them are the same: set your callsign and SSID correctly, choose a sensible path, pick a beacon interval that matches how you move, and don't leave a fixed handheld beaconing every minute.
Mic-E and SmartBeaconing. Mic-E is a compact position format used by many radios and trackers. Latitude is encoded in the AX.25 destination address, and the info field carries longitude, speed, course and the symbol. That is why a raw Mic-E packet shows an odd-looking destination callsign and an unreadable info field. Mic-E also carries a status code (In Service, En Route, Emergency and so on). SmartBeaconing varies the beacon rate with speed and course changes. You set a slow speed and slow rate, a fast speed and fast rate, a minimum turn time, a turn angle and a turn slope, and the radio beacons more often while turning or moving fast and rarely while parked. Treat any default numbers as starting points and tune them for your own driving and area.
Link to comment
https://www.hamradiobase.com/forums/topic/11826-setting-up-aprs-properly-on-144390-direwolf-igate-handheld-trackers-mic-e-smartbeaconing-and-what-to-put-on-the-channel/Share on other sites