Direwolf iGate plus fill-in digi for a mixed HT fleet (TH-D74/D75, FT5D): paths, Mic-E, SmartBeaconing and messaging
- 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'm planning an APRS node on 144.390 MHz (North America) built around Direwolf and a sound-card interface. It would run as an iGate, and maybe as a fill-in digipeater if the coverage gap justifies it. The users would carry a mix of Kenwood TH-D74 and TH-D75 radios and a Yaesu FT5D. I'd like to compare notes on the details that cause trouble in practice, so here is my current understanding. Please correct anything wrong.
Channel basics. APRS on VHF is 1200 baud AFSK carrying AX.25 UI frames. Nothing is acknowledged at the link layer, so every packet competes for the same shared channel. Other regions use different frequencies, for example 144.800 MHz in Europe and 145.175 MHz in Australia, so check the local band plan before configuring a radio.
Direwolf skeleton. This is a sketch of the iGate side only. Substitute your own callsign, audio device, PTT method and the passcode generated for your callsign.
Direwolf also has a DIGIPEAT directive that takes alias and wide patterns. I'd read the User Guide section on it before enabling it, because a badly written pattern can make the node repeat things it shouldn't.
Handheld settings I'm trying to standardize:
Open questions: how should the beacon path be set for a station that is already well covered by a wide-area digipeater? And what is the best way to confirm that an iGate really passes messages to RF, and not just position data to the Internet?
Link to comment
https://www.hamradiobase.com/forums/topic/10804-direwolf-igate-plus-fill-in-digi-for-a-mixed-ht-fleet-th-d74d75-ft5d-paths-mic-e-smartbeaconing-and-messaging/Share on other sites