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 - WIDE1-1 vs WIDE2-1

I'm setting up my first APRS mobile station using a Kenwood TM-D710G and getting conflicting information about path settings. The recommended path for mobiles or portable stations in North America is now WIDE1-1,WIDE2-1, but I'm seeing older documentation suggesting just WIDE2-2.

Can someone explain when to use which path? I understand the New-N paradigm was implemented to reduce network congestion, but I want to make sure I'm not causing QRM with improper path settings.

Also, should I be using different paths for stationary vs mobile operation? My QTH is in a suburban area with good digipeater coverage.

  • Replies 2
  • Views 150
  • Created
  • Last Reply

Top Posters In This Topic

Most Helpful Posts

  • David Thomas
    David Thomas

    The WIDE1-1,WIDE2-1 path is correct for mobile operation. Smart TNCs are capable of determining what has already happened with the packet and can prevent redundant packet repeating within the network.

  • David Williams99
    David Williams99

    I had the same confusion when I started! The key is understanding that WIDE1-1 hits nearby fill-in digis first, then WIDE2-1 gets you the wide coverage. Avoid the old WIDE2-2 path - it causes unnecess

Featured Replies

The WIDE1-1,WIDE2-1 path is correct for mobile operation. Smart TNCs are capable of determining what has already happened with the packet and can prevent redundant packet repeating within the network. This two-hop path allows your packets to reach fill-in digipeaters first, then get picked up by wide-area digipeaters for better coverage without excessive repeating.

For stationary operation, you might want to consider a shorter path or even direct operation if you're in a well-covered area. If you're a stationary object, we don't need to hear from you any more than every 15 minutes. Preferably 30 unless you're serving up weather data. Check your local APRS activity first before adding to the network.

I had the same confusion when I started! The key is understanding that WIDE1-1 hits nearby fill-in digis first, then WIDE2-1 gets you the wide coverage. Avoid the old WIDE2-2 path - it causes unnecessary network traffic. Your TM-D710G should handle the path settings perfectly once configured correctly.

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