APRS on 144.390: sorting out paths, iGate behavior, Direwolf, handheld settings and beacon rates
- Replies 2
- Views 34
- 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'm putting together a checklist for people new to APRS who have a handheld (TH-D74, TH-D75 or FT5D) and may later add a Direwolf station at home. Here is how I understand the pieces. Corrections are welcome.
APRS sends unconnected AX.25 UI frames, normally 1200 baud AFSK, on a shared simplex channel. In North America that is 144.390 MHz. Europe and Africa mostly use 144.800 MHz, and other regions differ, so check your local band plan before programming a memory. Nothing is acknowledged at the RF level for position beacons, so every packet competes for the same channel. That is why beacon rate and digipeater path matter so much.
The roles break down like this. A tracker or handheld with a TNC transmits position, status, messages or weather. A digipeater repeats a packet on RF, using the path field to decide whether to do so. An iGate hears RF and forwards valid packets to the APRS-IS network over the internet. Sites like aprs.fi display what reached APRS-IS. A station showing on aprs.fi tells you someone gated it, not that you were heard directly by the digipeater you expected.
On paths, the usual advice for mobiles is a short one, such as
WIDE1-1,WIDE2-1, or justWIDE1-1where the area has good wide-area digipeater coverage. Long paths such as WIDE2-2 stacked on other hops multiply the same packet across the channel. Old aliases like RELAY or bare WIDE are best avoided. Local practice varies, so find out what digipeaters in your area actually respond to.On the Direwolf side, the config file covers most of what is needed:
ADEVICEfor the sound interface,MYCALLwith an SSID,MODEM 1200, a PTT method, thenIGSERVERandIGLOGINfor the iGate.PBEACONsends fixed-position beacons andTBEACONhandles GPS tracking. Receive-only iGating is the safe starting point. Gating internet traffic back to RF should be limited, deliberate and local, and theIGTXLIMITsettings exist for that reason.Two things I'd like opinions on: how often a fixed station should beacon, and what is the cleanest way to get SmartBeaconing set up on a handheld without flooding the channel.
Link to comment
https://www.hamradiobase.com/forums/topic/11342-aprs-on-144390-sorting-out-paths-igate-behavior-direwolf-handheld-settings-and-beacon-rates/Share on other sites