Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

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 121
SN 99
A 11
K 3 Unsettled
X-Ray C2.4
Wind 432.2 km/s
Aurora 4
Updated 08:30 UTC HamQSL · N0NBH
Day 80/40m Poor 30/20m Good 17/15m Fair 12/10m Fair
Night 80/40m Fair 30/20m Good 17/15m Fair 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 not making sense to me

so ive been messing around with APRS for a few months now and i think i have a decent grasp on the basics but the path stuff is driving me crazy. im running a TM-D710G with a whip on the roof and i can see my packets going out on aprs.fi just fine, but i keep seeing people debate about WIDE1-1 vs WIDE2-1 vs WIDE2-2 and honestly i still dont fully get when you'd use what.

my current path is WIDE1-1,WIDE2-1 which i think is pretty standard? i'm in a suburban area about 20 miles from a decent sized city so theres no shortage of digipeaters around here. someone on another forum told me i should just use WIDE2-1 and drop the WIDE1-1 entirely but then i read somewhere else that WIDE1-1 is specifically for fill-in digis that wont respond to WIDE2. i dont know who to believe at this point.

also completely unrelated but has anyone used the messaging feature on the 710G to actually send messages back and forth with someone? tried it once with a buddy and it was kinda clunky but worked i guess

  • Replies 1
  • Views 54
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah the path thing trips up a lot of people. the short version is WIDE1-1 first in your path is specifically designed to hit those low-power fill-in digipeaters that dont respond to the regular WIDE2 alias. so in a rural or semi-rural area it genuinely helps your packet get picked up by something close by before getting handed off to a hilltop digi. in your case though, 20 miles from a city with plenty of infrastructure? you probably dont need it. WIDE2-1 alone should get you good coverage without clogging the channel with extra hops. the WIDE2-2 path is basically two hops, which in a dense area just means you're hammering more digipeaters and contributing to congestion. id stick with WIDE2-1 and call it good unless you start noticing coverage gaps.

the messaging thing on the 710G is functional but yeah its not exactly slick. works better if both people have solid igates nearby so the messages can route through the internet side. direct RF messaging is hit or miss depending on who's in range.

i had the same exact confusion when i started. what finally clicked for me was watching my packets on aprs.fi and toggling the path settings over a few days to see what actually got heard and by how many stations. in my area WIDE1-1,WIDE2-1 was way overkill, packets were getting digipeated like 8 times which is just noise. dropped to WIDE2-1 and coverage barely changed but i wasnt spamming the network nearly as much.

the messaging feature i actually use occasionally for EMCOMM exercises, its handy for quick position + message combos but yeah the acknowledge cycle can take a while if the igate isnt nearby. definitely not a replacement for voice for anything time sensitive

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

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.