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 3 Unsettled
X-Ray B9.2
Wind 423.8 km/s
Aurora 3
Updated 07: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 not igateing my packets - what am i missing

so ive been messing with APRS for a few months now and i cant figure out why my packets arent showing up on aprs.fi even though the local digi is definitely hearing me. i can see my callsign pop up in the raw log on the digi (its a KPC-3 Plus running as a fill-in i think) but nothing ever makes it to the internet side. my path is set to WIDE1-1,WIDE2-1 which i thought was pretty standard but maybe thats the issue.

running a TM-D710G into the radio port on my HT for the GPS feed, and i've got the baud rate set to 4800 which matches what the manual says. beacon rate is every 2 minutes. TX delay is 50ms. i dunno, everything looks right to me but clearly something isnt working right.

anyone run into this where the digi is picking you up but the igate just isnt forwarding it? is there a way to tell if the problem is on my end or the igates end?

  • Replies 1
  • Views 16
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah this is actually a pretty common thing and it usually comes down to the igate not having RF-to-internet enabled, or the digi and igate arent coordinated right. the digi hearing you doesnt mean much if the igate isn't close enough or properly configured to pass packets upstream to the APRS-IS servers.

check aprs.fi direct for your callsign but also try filtering by the raw packets tab - sometimes youre actually getting through but aprs.fi just isnt updating the map view right away. also look at findu.com, it sometimes shows stuff aprs.fi misses for whatever reason. if neither shows anything then the igate leg is definitely broken somewhere. you could also try messaging a nearby igate station directly from your radio and see if they get it, that'll tell you a lot about where the chain is breaking down.

your path looks fine honestly. WIDE1-1,WIDE2-1 is exactly what most people run around here. id bet its the igate and not you.

tx delay of 50ms might actually be too short depending on your radio - some rigs need more like 150-200ms for the TNC to fully key up before sending. i had a similar thing a while back and bumping that up fixed it, packets were getting clipped at the start and the digi couldnt decode them cleanly even if it was hearing carrier. worth trying before you go nuts chasing the igate config.

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.