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 148
SN 157
A 6
K 1 Quiet
X-Ray C1.1
Wind 515.2 km/s
Aurora 1
Updated 06: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 beacon showing up on aprs.fi but my messages aren't going through

so ive been messing with APRS for a few months now and got my beacon working pretty solid, showing up on aprs.fi with good position reports every few minutes which is great. but the messaging part is just completely broken for me and i cant figure out if its my setup or something with the network.

im running a TM-D710G with a Raspberry Pi running direwolf as a secondary igate at home, and i also have the radio itself set up with its built in TNC. when i try to send messages to other stations i can see the packets going out in direwolf's output, they get acked sometimes, but the people im trying to reach say they never got anything. i tried messaging WB4APR just to see if the message robot thing would bounce back and nothing came back either.

is there some setting im missing with the message path or something? i have the path set to WIDE1-1,WIDE2-1 which should be fine i think. been googling this for days and half the stuff i find is like 10 years old and i dont know if its still relevant.

  • Replies 1
  • Views 62
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

the path thing is worth double checking but honestly messaging on APRS has always been kinda flaky in my experience. one thing to check is whether the igates in your area are actually igating messages both directions — a lot of igates are RF-to-internet only and wont pass messages back down to RF. thats usually the culprit when you can see your packets going out but the other end never gets them.

also the aprs.fi message interface has been weird lately, not sure if that affects WB4APR's message server or not. try messaging a local station who you know is definitely on RF and watching their radio and see if that works, that'll help narrow down if its a local rf problem or an igate problem.

yeah what the previous guy said about bidirectional igating is the thing. i ran into this exact same issue when i set up my first igate. most igates running aprx or even some direwolf configs are only listening and not gating back down. look at aprs.fi and find the igates near you, click on them and see if it says RF-only or bidirectional. if all your local ones are RF-only then messages from the internet side are just never gonna make it back to RF and to whoever your trying to reach. its kind of a frustrating gap in APRS infrastructure honestly, not enough people running full bidirectional igates.

  • Guest unpinned, locked, pinned and unlocked this topic
  • Guest pinned, unpinned, locked and unlocked this topic
  • Guest locked, unpinned, pinned and unlocked this topic

Join the conversation

You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

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.