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 128
SN 73
A 6
K 1 Quiet
X-Ray C2.2
Wind 403.6 km/s
Aurora 2
Updated 23:00 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 not hitting igate — losing packets somewhere

so ive been messing with this for about three weeks now and im pretty sure im missing something obvious but cant figure out what. running a TM-D710G with the built-in TNC, got it set to beacon every 3 minutes with WIDE1-1,WIDE2-1 path. i can see my own packets decoding locally on the radio display but they're almost never showing up on aprs.fi — sometimes one gets through, maybe every 30-40 minutes if im lucky.

theres definitely a digipeater about 8 miles from me, i can see it beaconing fine on 144.390 and it shows up on the map with good activity. so its not like the local infrastructure is dead. my antenna is a mag mount on the car which i know isnt ideal but it shouldnt be this bad right? when im mobile it seems even worse, barely a trace on the map.

checked the TX power, its at 50W. ssid is set to -9. not sure if the issue is the path, the antenna, or something with how the 710 is configured. anyone dealt with this before?

  • Replies 1
  • Views 25
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

the path you're using is fine for most situations, WIDE1-1,WIDE2-1 is pretty standard. my first suspicion with what you're describing is actually RF getting back into the TNC somehow — mag mounts on cars can do weird things especially if the ground plane isnt great. the 710 is sensitive to that.

one thing worth checking is whether the digipeater is actually hearing you at all. if you have access to a second receiver or can pull up a webSDR near you, monitor 144.390 while you key up and see if your packet even makes it to the digi. if the digi isnt hearing you then it doesnt matter what your path says, nothing gets to the igate. the 8 mile distance with 50W should be totally workable but terrain and that mag mount could be killing you more than you think.

also double check your MYCALL is set right in the TNC config, not just in memory — ive seen the 710 where those get out of sync and weird stuff happens with how packets get formed.

had almost the exact same thing happen to me last year. turned out the local digi was hearing me fine but the igate downstream was only running during certain hours because the guy who ran it had it on a timer or something. checked aprsdirect and could actually see my packets being digi'd but they just werent making it to the IS. worth checking if your packets show up on any of the direct RF monitoring sites vs aprs.fi specifically.

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.