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 101
SN 82
A 6
K 0 Quiet
X-Ray B3.6
Wind 323.7 km/s
Aurora 1
Updated 12:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
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 igating my packets - what am i missing

so ive been messing with APRS for a few months now and i finally got my Kenwood TM-D710G set up and beaconing but when i check aprs.fi my position either shows up super late or sometimes not at all. the digipeater i can see on the map is only like 8 miles away and i know its hitting it because i can see my packets getting digi'd on the RF side when i monitor 144.390, but they just dont seem to be making it to the internet.

im running WIDE1-1,WIDE2-1 path which i thought was the standard thing to do around here. ive got the beacon rate set to every 5 minutes which felt reasonable. not sure if the issue is the igate side or if my path is somehow wrong. also not totally clear on whether the digipeater and igate are the same station or if those are two different things - i kind of assumed they were combined but maybe thats my whole problem right there

anyone dealt with something like this or know what to look for

  • Replies 1
  • Views 51
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah digipeaters and igates are definitely two separate functions - a lot of stations run both but plenty of them only digi without igating anything to the internet. so your packets might be getting repeated just fine over RF but if the igate covering that area is down or doesn't have good coverage of your digipeater's output then nothing gets to aprs-is.

easiest thing to do is go to aprs.fi and search for your callsign then click on the raw packets tab - it'll show you what path each packet actually took to get there and which igate received it. if you're seeing big gaps its probably an igate coverage hole. also check APRS Direct or findu to see if theres any igate activity near you, sometimes a site that looks covered on paper just has one igate thats been offline for weeks and nobody noticed. your path looks fine by the way, WIDE1-1,WIDE2-1 is totally appropriate for mobile or home use in most areas.

one more thing - if you have a way to run Direwolf on a separate machine even just a pi, you could set it up as your own igate and solve the coverage problem yourself. thats how i ended up going down that rabbit hole, had the same issue a couple years back and just stood up my own igate. now i see half the county's traffic which is kind of entertaining honestly. APRS messaging actually works pretty reliably once you get the whole chain sorted out.

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.