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 C3.5
Wind 416.0 km/s
Aurora 2
Updated 00: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 questions — am i doing this wrong

 Loading...

so ive been running APRS for about 8 months now and i think i finally have a decent setup but something has been nagging at me for a while. im using a Kenwood TM-D710G with the built in TNC and i have it set to WIDE1-1,WIDE2-1 which i know is pretty standard but im in a fairly rural area about 30 miles from the nearest city and i keep seeing my packets show up on aprs.fi with like 3 or 4 hops sometimes and other times barely anything gets through at all.

my question is mostly about the path — should i be using something different out here or is WIDE1-1,WIDE2-1 still the right call. ive read some stuff that says WIDE2-2 is better for rural areas because you get more hops but then other stuff says that just creates congestion. i honestly cant tell if my packets are even hitting a fill-in digi or if theyre going straight to a wide digi. is there a way to figure that out just from what aprs.fi shows you

also secondary question — the messaging function on the 710 is kind of clunky but does anyone actually use it for real communication or is it mostly just a novelty at this point

  • Replies 1
  • Views 46
  • Created
  • Last Reply

Top Posters In This Topic

Most Helpful Posts

  • Ham Fan
    Ham Fan

    yeah aprs.fi will show you the digipeater path in the packet detail, look for the path trace on each entry. if you see WIDE1-1 in the via field getting replaced with an actual callsign you know a fill

Featured Replies

the path thing is one of those debates that never really fully settles but here's what i'd say — in a rural area WIDE2-2 can actually make sense because you need those extra hops to reach a digi at all. WIDE1-1,WIDE2-1 is designed for areas where there are fill-in digis that respond to WIDE1-1 first, if those arent around then that first hop is kind of wasted. you can check aprs.fi and click on your callsign then look at the raw packets, it'll show you which digis actually touched the packet and in what order. that gives you a pretty good picture of whats happening. the path shows up in the path field for each individual packet so you can see exactly who digipeated it.

for the messaging, i actually use it semi regularly on nets and occasionally for emcomm stuff. its not fast and yeah the interface on the 710 is annoying to type on but it gets the job done. some of the newer software clients like Xastir or even APRS-IS stuff make messaging way more usable if you have a computer tied in.

yeah aprs.fi will show you the digipeater path in the packet detail, look for the path trace on each entry. if you see WIDE1-1 in the via field getting replaced with an actual callsign you know a fill-in digi grabbed it. if you're only seeing wide area digis then you probably dont have any WIDE1-1 capable fill-ins nearby and you might as well just run WIDE2-2 and skip that first hop entirely.

i went through the same thing when i moved out to a more rural area. ended up dropping to WIDE2-2 and my coverage actually got more consistent. less elegant maybe but it worked. also depending on how remote you are you might want to bump your beacon rate down a little so you're not hammering the channel unnecessarily since out in the sticks there's probably not a ton of traffic anyway.

  • Guest locked, unpinned and unlocked this topic
  • Guest locked, unlocked and unpinned this topic
  • Guest unlocked, locked and unpinned 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.