Setting up a handheld tracker and a Direwolf iGate on 144.390: paths, Mic-E, SmartBeaconing and objects
- 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 planning an APRS setup with two parts and want to sanity-check the design before I put anything on the air.
Part one is a mobile tracker. I'll use a handheld with a built-in GPS and TNC, either a Kenwood TH-D74/TH-D75 or a Yaesu FT5D, in a vehicle. Part two is a fixed receive-only iGate at home. It would be a Raspberry Pi-class box running Direwolf with an RTL-SDR or a soundcard-connected radio on 144.390 MHz. I'm in North America, so 144.390 is the channel. Other regions use different frequencies, so check your local band plan.
Here is what I'm trying to decide:
1) Path. I know WIDE1-1,WIDE2-1 is the usual mobile default. Is there a good reason to change it, and what should the fixed station use?
2) Beaconing. Is SmartBeaconing worth configuring on the radio, or should I use a fixed interval? 1200 baud is a shared channel and I don't want to be the person clogging it.
3) Mic-E versus plain position packets. The handhelds seem to default to Mic-E. Do I lose anything by leaving it alone?
4) Messaging and objects. I'd like to send short messages through the iGate and eventually place an object for a club event. What are the gotchas?
For the iGate, this is the minimal Direwolf config I intend to start with. The callsign and passcode are placeholders, and I'm leaving it RX-only (no IGTXVIA) for now:
Does anything there look wrong or missing? I'd also like to know how you verify that a new iGate is actually working, beyond "no errors in the log."
Link to comment
https://www.hamradiobase.com/forums/topic/11284-setting-up-a-handheld-tracker-and-a-direwolf-igate-on-144390-paths-mic-e-smartbeaconing-and-objects/Share on other sites