Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base -Powered By Ham CQ DX

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Solar
SFI 147
SN 141
A 10
K 2 Quiet
X-Ray C2.6
Wind 390.7 km/s
Aurora 3
Updated 04:30 UTC HamQSL · N0NBH
Day 80/40m Fair 30/20m Good 17/15m Good 12/10m Fair
Night 80/40m Good 30/20m Good 17/15m Good 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots
Select a band above to load spots
Ready — select a band to fetch live spots

APRS digipeater path confusion — am i doing this wrong?

 Loading...

so ive been messing with APRS for a few months now and i think i finally have my station somewhat dialed in but im getting weird results with my path settings and cant figure out if its a config problem or just how the network works in my area.

running a TM-D710G with a homebrew vertical on the roof, using WIDE1-1,WIDE2-1 which i thought was pretty standard. but when i check aprs.fi i sometimes see my packets showing up with like 6 or 7 hops listed and other times barely any. my buddy who lives about 8 miles away says he sees my beacons fine direct sometimes but sometimes not at all.

also tried reducing to just WIDE2-2 based on something i read on a mailing list but honestly im not sure i understand the difference well enough to know which is better for my situation. im in a semi-rural area, not super dense with digipeaters but theres a few around. is there a good way to actually test this without just guessing?

  • Replies 1
  • Views 25
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

the WIDE1-1,WIDE2-2 path (note: WIDE2-2 not WIDE2-1 at the end) is actually the more common recommendation these days especially if you're in an area with fill-in digis. WIDE1-1 is specifically intended to be heard by those low-power fill-in digipeaters that might not respond to WIDE2 calls. if your area doesn't have many of those it's basically just adding hops for no reason and yes that can cause duplicate packets floating around which is why you see inconsistent behavior on aprs.fi.

best way to test honestly is aprs.fi combined with findu.com — look at the raw packets and see which digis are actually picking you up and how many times each packet shows. if you're seeing the same packet relayed 4-5 times from the same digi chain that's a sign your path is too aggressive for the local infrastructure. i went through the same thing when i moved out here, took me a while to realize there was a really solid WIDE2 digi about 12 miles out that was doing all the heavy lifting and my WIDE1-1 was just creating extra garbage on the channel.

yeah what he said about checking raw packets is the way to go. also worth looking up what digis are actually in your area on aprs.fi map — zoom in and filter for digipeaters, gives you a pretty good sense of the coverage you're actually working with before you spend too much time tweaking paths blind.

tbh in semi rural areas i usually just run WIDE2-2 and call it good, keeps it cleaner

  • Guest locked, unpinned, unlocked and pinned this topic

Join the conversation

You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.