Getting a handheld tracker, a Direwolf iGate and aprs.fi to agree on 144.390
- Replies 2
- Views 54
- Created
- Last Reply
Top Posters In This Topic
-
Mod_Chrissy 1 post
-
Mod_Nancy 1 post
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
A common first APRS setup has three parts: a handheld or mobile beaconing on 144.390 MHz (the North American frequency; Europe uses 144.800), a Raspberry Pi or PC running Direwolf as an RX iGate, and aprs.fi to confirm that packets are reaching the internet. When it works, the track appears on the map. When it doesn't, the cause is usually one of a few things, and this thread is for sorting those out.
Quick recap of the chain. A tracker such as a Kenwood TH-D74/TH-D75 or a Yaesu FT5D sends an AX.25 UI frame at 1200 baud AFSK. A digipeater may repeat it, depending on the path. An iGate that hears it on RF forwards it to APRS-IS, and aprs.fi reads it from there. A missing station could mean a failure at any hop: bad RF, a path nobody answers, an iGate that isn't logging in, or a beacon that isn't being sent at all.
Here is a minimal Direwolf config for a receive-only iGate. The callsign, passcode, audio device and coordinates are placeholders. Check the server name against the current APRS-IS rotate for your region.
The
sendto=IGoption sends the iGate's own position straight to APRS-IS instead of over RF, which is the usual choice for an RX-only station. Without a transmit configuration the station only listens, which suits a first test.Questions to start with: what do you check first when a beacon doesn't show on aprs.fi? And how do you decide between WIDE1-1,WIDE2-1 and a shorter path once you know what the local digipeaters are doing?
Link to comment
https://www.hamradiobase.com/forums/topic/11047-getting-a-handheld-tracker-a-direwolf-igate-and-aprsfi-to-agree-on-144390/Share on other sites