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 path not working right — packets not getting out

so ive been messing with APRS for a few months now and generally its been fine but lately my packets just arent making it to aprs.fi even though i can hear the local digi pretty clearly. im running a TM-D710G with the internal TNC and ive got my path set to WIDE1-1,WIDE2-1 which from everything ive read should be totally standard. beacon interval is 1 minute.

i went and checked aprsdirect and RF coverage maps and there should be at least two digis that can hit me from here. but when i look at my station on aprs.fi the last heard timestamp is like 6 hours old. my radio is definitely transmitting because i can see the TX light flash on the beacon interval. signal check from a friend down the road says im putting out fine on 144.390.

one thing i noticed is my SSID might be messed up — i had it set to -9 for a while cause i was mobile then forgot to change it back when i got home. could that be causing issues somehow or is that totally unrelated. also not sure if my symbol is right, i think its set to house but honestly i dont remember changing it back after some testing i did last week. kind of a mess honestly

  • Replies 1
  • Views 97
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

the SSID thing shouldn't matter for getting digipeated, that's more just for identification purposes. -9 is technically for mobile but it wont stop a digi from repeating you.

what i'd check first is your actual packet content — hook up a terminal or use a monitor mode on the TNC and look at exactly what youre putting out. sometimes the TM-D710 gets into a weird state where its transmitting but the packet data is garbage or malformed and the digis just drop it. i had this exact thing happen after a firmware glitch and spent like two days chasing my tail before i finally decoded what was actually coming out of the radio. pulled up APRSIS32 with a cheap RTL-SDR to monitor my own packets and immediately saw the issue — the path encoding was totally scrambled.

also double check your baud rate is 1200 not 9600, ive seen that catch people out more than once

yeah what he said about monitoring your own output is good advice. but also — have you tried just manually keying a position beacon and then immediately going to aprs.fi to see if it shows up? sometimes the site caches weirdly or your browser is showing you old data. sounds dumb but ive been burned by that before, sat there convinced my setup was broken for an hour before i hit ctrl-f5.

also worth checking if your local digi is actually running. some of those machines are volunteer-maintained and go down without notice. check if anyone else in your area is getting gated or if the digi itself is showing up on aprs.fi

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.