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 93
A 11
K 2 Quiet
X-Ray B9.5
Wind 413.9 km/s
Aurora 2
Updated 05:30 UTC HamQSL · N0NBH
Day 80/40m Fair 30/20m Good 17/15m Fair 12/10m Fair
Night 80/40m Good 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 not propagating my packets beyond a few hops

so ive been messing with APRS for a few months now and overall its working okay but i cant figure out why my packets seem to die after like one or two hops. im running a TM-D710G with the internal TNC and using WIDE1-1,WIDE2-1 as my path which from everything ive read should be pretty standard. i can see myself hitting the local digi and sometimes one more out but then nothing, my symbol just stops showing up on aprs.fi beyond maybe 40-50 miles.

i checked my path settings probably six times, everything looks right. power is 50 watts into a vertical on the roof with a decent ground plane, so RF shouldnt really be the issue. neighbor down the road with a VX-8 shows up all over the map so its not like the network is dead here.

one thing i noticed is that when i send a message through the APRS-IS gateway it goes fine, so at least that part works. its really just the RF hop propagation thats bugging me. anyone seen this before or have ideas what to poke at next?

  • Replies 1
  • Views 4
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

check if the digis in your area are actually set up to handle WIDE1-1 vs WIDE2-2. some of the older installs around here only pass WIDE2-n and wont act on the WIDE1-1 at all unless they're specifically configured as fill-in digis. you can actually verify this by pulling up aprs.fi and clicking on a packet that does make it through -- itll show you the path it actually took and which digis touched it. if you're only seeing one digi in the path it tells you a lot.

also worth checking if maybe the digi closest to you is set to a low power or has a crippled path limit. some sysops cap hops at 1 even if you request 2, which is honestly fine network practice but can make you think somethings broken when its not.

yeah this drove me nuts for a while too. turned out in my case the issue was the TNC was sending duplicate packets because i had both the radio's internal APRS mode AND Xastir running at the same time both trying to key up. the digis were probably dropping the dupes. dont ask me how long it took me to figure that one out lol. probably not your issue since you said its just the internal TNC but worth double checking nothing else is keying the radio.

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.