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 B6.4
Wind 390.4 km/s
Aurora 2
Updated 02: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 beacon not showing up on aprs.fi — what am I missing

so ive been trying to get my APRS setup working for about two weeks now and im losing my mind a little. running a TM-D710G with the internal TNC, callsign and SSID are set correctly (pretty sure anyway), path is WIDE1-1,WIDE2-1 and i can hear packets on 144.390 just fine. the radio decodes them and i can see the station list filling up. but when i key up and send a beacon, nothing shows on aprs.fi. tried manual beacon, smart beaconing, doesnt matter.

one thing i noticed is the TX light does flash when i beacon so it IS transmitting something. a buddy a few miles away with a direwolf IGate said he can occasionally hear my packets but they're not making it to the internet. he said something about the SSID on my path being wrong but i dont fully understand what he meant. is there like a setting on the radio that controls what gets included in the packet header vs just the voice side of things?

also is there any way to decode my own packets locally to verify the packet content before it goes out? i have a spare SDR dongle sitting around.

  • Replies 1
  • Views 130
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

the SDR idea is actually pretty solid for self-monitoring. pipe the audio into direwolf on your laptop and set it to just decode, youll see the raw packet string and can verify your callsign, path, symbol, everything. that's the fastest way to catch a formatting issue without depending on someone else to hear you.

on the path thing — WIDE1-1,WIDE2-1 is fine for most areas, your buddy might have been talking about something else. one thing to double check on the D710 is whether the TNC is actually in APRS mode vs just packet mode. there's a difference and its easy to have it in the wrong one. also check that your beacon comment or position format isnt somehow corrupted. ive seen radios where a firmware quirk sends a malformed lat/lon that digipeaters just silently drop.

had almost the exact same problem last year. turned out my APRS symbol was set to something the software didn't like and iGates in my area were just not forwarding it for some reason — never fully figured that part out honestly. but the bigger issue for me was that i was too far from an iGate and the two digipeaters between me and the nearest one were both kind of flaky. you can check coverage on aprs.fi by looking at who's actually hitting your area, zoom in and see if theres even an active iGate within a hop or two of you.

also try sending a message to SMSGTE or something just to see if messaging works independent of position beacons, sometimes that helps narrow down whats broken.

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.