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 147
SN 141
A 10
K 3 Unsettled
X-Ray C1.0
Wind 395.0 km/s
Aurora 3
Updated 02:30 UTC HamQSL · N0NBH
Day 80/40m Poor 30/20m Good 17/15m Good 12/10m Fair
Night 80/40m Fair 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 Messaging Reliability - Packets Getting Lost

APRS-IS to RF messaging worked yesterday but stopped after toggling telemetry settings. Using APRX 2.8.1 on Raspberry Pi with proper digipeater configuration. Logs show messages reaching APRX but getting discarded with "History entry for sending call from APRSIS is too new". RF-to-RF messaging via digipeater still functions, as does RF-to-IS direction. Has anyone seen this timing issue with message history filtering? The viscous-delay and filter settings appear correct but something in the dupe-checking logic seems broken.

  • Replies 2
  • Views 99
  • Created
  • Last Reply

Top Posters In This Topic

Most Helpful Posts

  • Ham Fan
    Ham Fan

    Update to latest APRX version as recent releases fixed several messaging problems. Check your filter configuration - using 't/m' filter alone may require area filter to prevent discard. The history ti

  • Robert Chen
    Robert Chen

    This is a known issue with APRX message timing. Try configuring the APRSIS source with 'relay-type 3rd-party' and proper msg-path settings. The dupe suppression algorithm can be overly aggressive if v

  • Jennifer Adams
    Jennifer Adams

    The old SMSGTE service has been shut down due to spam issues. If you're trying to bridge to SMS, the new SMS gateway requires registration of phone numbers to eliminate spam. This might affect your me

Featured Replies

Update to latest APRX version as recent releases fixed several messaging problems. Check your filter configuration - using 't/m' filter alone may require area filter to prevent discard. The history timeout logic was adjusted in newer builds.

This is a known issue with APRX message timing. Try configuring the APRSIS source with 'relay-type 3rd-party' and proper msg-path settings. The dupe suppression algorithm can be overly aggressive if viscous-delay parameters aren't tuned for your local network conditions.

The old SMSGTE service has been shut down due to spam issues. If you're trying to bridge to SMS, the new SMS gateway requires registration of phone numbers to eliminate spam. This might affect your message routing if you had SMS bridging enabled.

  • Guest unlocked, locked, unpinned and pinned this topic
  • Guest pinned this topic
  • Guest unlocked, locked, unpinned and pinned this topic
Guest
Reply to this topic...

Account

Navigation

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.