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 162
A 10
K 1 Quiet
X-Ray C1.3
Wind 392.8 km/s
Aurora 1
Updated 11: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 showing up on aprs.fi but position is way off

 Loading...

so ive been running APRS for a few months now with a TM-D710G and a byonics GPS puck mounted on the dash. works great most of the time but every now and then my position on aprs.fi shows me like 12 miles south of where I actually am, sometimes in the middle of a lake which is obviously wrong. the weird thing is it doesn't happen consistently, could be fine for days then suddenly show up wrong for a few beacons then fix itself.

my NMEA feed looks correct when i monitor it through the radio's display, shows the right lat/lon, so im not sure if its a digipeater thing or what. using WIDE1-1,WIDE2-1 path which i figured was pretty standard. anybody seen this kind of thing before or have a idea what might cause it

  • Replies 1
  • Views 8
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

that sounds like it could be a corrupt packet getting through without triggering a checksum failure, or possibly a different station's packet getting attributed to your callsign somehow. does aprs.fi show the path info on those bad position reports? if you click on the packet detail it'll show you which digipeaters touched it and that might give you a clue. also worth checking if your SSID is unique, ive seen cases where someone nearby is running the same callsign-SSID combo which causes all kinds of weirdness on the network.

the 12 miles off thing is suspicious though, that's too consistent to be pure noise. could be a NMEA sentence getting parsed wrong, like if the GPS occasionally spits out a position from before it had a solid fix and the radio is just blindly forwarding it. some of those cheaper pucks will output a technically valid NMEA sentence with old coordinates right after powerup before they reacquire. might be worth looking at what time of day the bad beacons happen and see if it correlates with when you start the car.

yeah the startup thing is almost certainly it. my mobilinkd had the same deal when i was running it with a garmin that took a while to get a solid fix. the radio doesnt know the GPS hasnt settled yet, just sees valid NMEA and fires a beacon. i just added a small delay before the radio starts transmitting after power on, think there's a setting for that in the TM-D710 menu somewhere, beacon delay or something like that. been ages since i configured mine so dont quote me on the exact menu location

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.