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

using a pi zero to automate my shack logging - anyone done this before

so ive been messing around with a raspberry pi zero W for a few months now trying to get it to automatically pull my WSJT-X logs and push them to LOTW and QRZ at the same time without me having to sit there and do it manually every time. the zero is honestly underpowered for running WSJT-X itself but as like a little helper that just watches a folder and does stuff when files change it works fine.

right now i have a python script using watchdog to monitor the ADIF log file and when it detects a change it waits like 30 seconds (so the QSO is definitely complete) and then calls tqsl on a separate machine via SSH and also posts to QRZ via their API. its mostly working but occasionally it double-logs things and im not sure if thats a watchdog issue or something with how WSJT-X writes to the file - i think it might flush and then write again or something which triggers the callback twice.

has anyone done something similar or dealt with that double-trigger problem. i also have an arduino nano sitting around and was wondering if theres any reason to involve that instead of doing everything on the pi but i cant think of what it would actually add here

  • Replies 1
  • Views 13
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah the double trigger thing is almost certainly the file write behavior - a lot of apps do a partial write and then finalize and watchdog sees both events. easiest fix ive found is to track a hash of the last N bytes of the file or just keep a set of QSO timestamps youve already processed and skip anything thats already in there. the 30 second wait helps but its not bulletproof depending on how wsjtx is flushing.

as for the arduino question, no real reason to use one here. the pi zero is fine for this kind of task. arduino makes sense when you need fast real time GPIO stuff or youre interfacing with hardware directly like building a band decoder or controlling antenna relays. for pure software automation and API calls youre in pi territory all the way. i do use a nano in my shack but its literally just watching the band decoder output from my radio and switching a relay board, the pi handles all the actual logic and the arduino is just the muscle that flips pins fast.

i did something similar a while back but gave up on watchdog and just used a cron job every 5 minutes that diffs the current adif against a copy i keep and only processes new lines. its dumb simple and works perfectly, never had a duplicate since i switched. the pi zero might chug a tiny bit doing the diff on a big log file but honestly mine has like 8000 QSOs in there and it takes maybe half a second so whatever

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.