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 B8.3
Wind 432.7 km/s
Aurora 3
Updated 06: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 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, got my callsign and SSID set correctly (at least i think so), path is set to WIDE1-1,WIDE2-1 and im transmitting every 5 minutes. I can hear other stations just fine on 144.390 and the radio is clearly keying up when it should beacon but nothing ever shows up on aprs.fi. not even a delayed packet or anything.

Tried changing the symbol, tried shortening the beacon interval to see if that helped, even drove around for a bit thinking maybe my home location is in a dead spot. Other stations in my area are showing up fine so the frequency is obviously active. Starting to wonder if theres something wrong with my path config or maybe the SSID is the issue somehow. Anyone dealt with this before?

  • Replies 1
  • Views 22
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

First thing id check is whether the TNC is actually encoding your callsign right. On the D710 theres a separate menu for the packet callsign vs the regular radio callsign and a lot of people set one and forget the other. Go into the TNC settings specifically and make sure the source callsign matches what you think you set. Also double-check that your SSID is something valid - if you accidentally put a letter in there instead of a number it can cause weird behavior.

The other thing worth trying is connecting a laptop via the data port and running something like Dire Wolf or even just a dumb terminal to see the raw packets coming out before they go over the air. That way you know exactly what the TNC is actually sending rather than guessing. If the packet looks right locally then the problem is RF or path, but at least you've eliminated the encoding side.

yeah had something similar happen to me last year, turned out one of my digipeaters in the area had been offline for months and i just assumed the network was healthy because i could receive fine. receiving and being digipeated are totally different things obviously. might be worth checking if any of the nearby fill-in digis are actually active by watching for their own beacons.

also WIDE2-1 on its own might get you further than WIDE1-1,WIDE2-1 depending on how your local network is configured, some areas the WIDE1 layer isnt really needed

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.