#wavelog — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #wavelog, aggregated by home.social.
-
QSO over two days 24 & 25 Sep 26
- Total Contacts: 22 QSOs
- DXCC Entities: 18 unique entities
- Mode: 100% CW
CT9/UR9IDX
TM4GGR
G3ROO
F5IN
OT4A
DK9PY
DK7DC
DB26YLBB
IK5RP
DL4HRM
S58W
SM4OTI
SA2CLC
OM4KW
OK2LA
OH3IH
HA5JI
ES2RW
LZ1NP
4X4JU
R9HEC
UA9JLL/M#cw #cwops #skcc #a1cub #hamradio #wavelog #spothole #qrp #ic705 #30cw #getontheair
-
QSO over two days 24 & 25 Sep 26
- Total Contacts: 22 QSOs
- DXCC Entities: 18 unique entities
- Mode: 100% CW
CT9/UR9IDX
TM4GGR
G3ROO
F5IN
OT4A
DK9PY
DK7DC
DB26YLBB
IK5RP
DL4HRM
S58W
SM4OTI
SA2CLC
OM4KW
OK2LA
OH3IH
HA5JI
ES2RW
LZ1NP
4X4JU
R9HEC
UA9JLL/M#cw #cwops #skcc #a1cub #hamradio #wavelog #spothole #qrp #ic705 #30cw #getontheair
-
QRP CW QSO Summary
🗓️ Date (UTC): 2026-09-17📊 Core Metrics:
• Total Stations Worked: 13
• Unique Callsigns: 12
• ODX (Longest Distance): G3RWF (England) : 6,623.7 km (15m CW)📡 Band Breakdown:
• 15m: 5 QSOs
• 17m: 3 QSOs
• 20m: 2 QSOs
• 12m: 1 QSO
• 40m: 1 QSO
• 30m: 1 QSO📋 Worked Callsigns:
RA9V, R2WB, E75A, R1AL, E27CLF, SP7HKK, VU2CPL, RK3ER, OS5Z, DL7SX, G3RWF, DK7DC
#ic705 #cw #qrp #qso #wavelog #CW4EVR -
QRP CW QSO Summary
🗓️ Date (UTC): 2026-09-17📊 Core Metrics:
• Total Stations Worked: 13
• Unique Callsigns: 12
• ODX (Longest Distance): G3RWF (England) : 6,623.7 km (15m CW)📡 Band Breakdown:
• 15m: 5 QSOs
• 17m: 3 QSOs
• 20m: 2 QSOs
• 12m: 1 QSO
• 40m: 1 QSO
• 30m: 1 QSO📋 Worked Callsigns:
RA9V, R2WB, E75A, R1AL, E27CLF, SP7HKK, VU2CPL, RK3ER, OS5Z, DL7SX, G3RWF, DK7DC
#ic705 #cw #qrp #qso #wavelog #CW4EVR -
QRP CW QSO Summary
🗓️ Date (UTC): 2026-09-17📊 Core Metrics:
• Total Stations Worked: 13
• Unique Callsigns: 12
• ODX (Longest Distance): G3RWF (England) : 6,623.7 km (15m CW)📡 Band Breakdown:
• 15m: 5 QSOs
• 17m: 3 QSOs
• 20m: 2 QSOs
• 12m: 1 QSO
• 40m: 1 QSO
• 30m: 1 QSO📋 Worked Callsigns:
RA9V, R2WB, E75A, R1AL, E27CLF, SP7HKK, VU2CPL, RK3ER, OS5Z, DL7SX, G3RWF, DK7DC
#ic705 #cw #qrp #qso #wavelog #CW4EVR -
QRP CW QSO Summary
🗓️ Date (UTC): 2026-09-17📊 Core Metrics:
• Total Stations Worked: 13
• Unique Callsigns: 12
• ODX (Longest Distance): G3RWF (England) : 6,623.7 km (15m CW)📡 Band Breakdown:
• 15m: 5 QSOs
• 17m: 3 QSOs
• 20m: 2 QSOs
• 12m: 1 QSO
• 40m: 1 QSO
• 30m: 1 QSO📋 Worked Callsigns:
RA9V, R2WB, E75A, R1AL, E27CLF, SP7HKK, VU2CPL, RK3ER, OS5Z, DL7SX, G3RWF, DK7DC
#ic705 #cw #qrp #qso #wavelog #CW4EVR -
Wavelog 3.2.2 has been released today, 2026-09-14:
https://github.com/wavelog/wavelog/releases/tag/3.2.2
#Wavelog #HamRadio #AmateurRadio #hamr #radio #OpenSource #FOSS #logs #logging #HamLogging
-
Wavelog 3.2.2 has been released today, 2026-09-14:
https://github.com/wavelog/wavelog/releases/tag/3.2.2
#Wavelog #HamRadio #AmateurRadio #hamr #radio #OpenSource #FOSS #logs #logging #HamLogging
-
Wavelog 3.2.2 has been released today, 2026-09-14:
https://github.com/wavelog/wavelog/releases/tag/3.2.2
#Wavelog #HamRadio #AmateurRadio #hamr #radio #OpenSource #FOSS #logs #logging #HamLogging
-
Wavelog 3.2.2 has been released today, 2026-09-14:
https://github.com/wavelog/wavelog/releases/tag/3.2.2
#Wavelog #HamRadio #AmateurRadio #hamr #radio #OpenSource #FOSS #logs #logging #HamLogging
-
Wavelog 3.2.2 has been released today, 2026-09-14:
https://github.com/wavelog/wavelog/releases/tag/3.2.2
#Wavelog #HamRadio #AmateurRadio #hamr #radio #OpenSource #FOSS #logs #logging #HamLogging
-
I did not intend to spend several hours today making 3 releases full of new features to WaveLogGoat, but I did. One of them is a workaround for a regression in wavelog, but the rest are pure features!
- It now scales reported power by a max power setting. Defaults to 100 (100W) since percent equals watts on most shack rigs. If you have a 100W rig feeding a 500W dial-a-watt amp, set max power to 500W and even if the rig is reporting watts instead of percent, what is logged will be the watts coming out of the amp. If you have a 5W or 10W rig that shows 100W at full power when logged in wavelog via WaveLogGoat, set the max power to 5W or 10W, and it should become correct.
- mDNS support for talking to hamlib, rigctl, and wavelog using
.localaddresses (a.k.a. Avahi). Previously this didn't work unless you did a localCGO_ENABLED=1build in order to use the C library's resolver. I added explicit native Go support, so the binaries are still self-contained. - Log the version of wavelog (requires adding an api V1 key, separate from the api V2 key, because the version is not available under api v2.)
- Send power as int instead of float only if talking to wavelog 3.2.0 which improperly rejects floats and is planned to be fixed in 3.2.1. On other versions, keep sending float in particular to support logging QRPp operation. (This depends on the api V1 key being configured; it defaults to float otherwise.)
- Added an example systemd user unit file to the documentation
- Fixed a build command that should never have worked (not sure how releases made it out before, but not motivated to look further).
Also, it became clear partway through this work that what had been a single tiny Go file that I had expected to barely ever touch was getting hard to navigate, so I refactored out into multiple files. I also updated the README in various ways.
-
I did not intend to spend several hours today making 3 releases full of new features to WaveLogGoat, but I did. One of them is a workaround for a regression in wavelog, but the rest are pure features!
- It now scales reported power by a max power setting. Defaults to 100 (100W) since percent equals watts on most shack rigs. If you have a 100W rig feeding a 500W dial-a-watt amp, set max power to 500W and even if the rig is reporting watts instead of percent, what is logged will be the watts coming out of the amp. If you have a 5W or 10W rig that shows 100W at full power when logged in wavelog via WaveLogGoat, set the max power to 5W or 10W, and it should become correct.
- mDNS support for talking to hamlib, rigctl, and wavelog using
.localaddresses (a.k.a. Avahi). Previously this didn't work unless you did a localCGO_ENABLED=1build in order to use the C library's resolver. I added explicit native Go support, so the binaries are still self-contained. - Log the version of wavelog (requires adding an api V1 key, separate from the api V2 key, because the version is not available under api v2.)
- Send power as int instead of float only if talking to wavelog 3.2.0 which improperly rejects floats and is planned to be fixed in 3.2.1. On other versions, keep sending float in particular to support logging QRPp operation. (This depends on the api V1 key being configured; it defaults to float otherwise.)
- Added an example systemd user unit file to the documentation
- Fixed a build command that should never have worked (not sure how releases made it out before, but not motivated to look further).
Also, it became clear partway through this work that what had been a single tiny Go file that I had expected to barely ever touch was getting hard to navigate, so I refactored out into multiple files. I also updated the README in various ways.
-
I did not intend to spend several hours today making 3 releases full of new features to WaveLogGoat, but I did. One of them is a workaround for a regression in wavelog, but the rest are pure features!
- It now scales reported power by a max power setting. Defaults to 100 (100W) since percent equals watts on most shack rigs. If you have a 100W rig feeding a 500W dial-a-watt amp, set max power to 500W and even if the rig is reporting watts instead of percent, what is logged will be the watts coming out of the amp. If you have a 5W or 10W rig that shows 100W at full power when logged in wavelog via WaveLogGoat, set the max power to 5W or 10W, and it should become correct.
- mDNS support for talking to hamlib, rigctl, and wavelog using
.localaddresses (a.k.a. Avahi). Previously this didn't work unless you did a localCGO_ENABLED=1build in order to use the C library's resolver. I added explicit native Go support, so the binaries are still self-contained. - Log the version of wavelog (requires adding an api V1 key, separate from the api V2 key, because the version is not available under api v2.)
- Send power as int instead of float only if talking to wavelog 3.2.0 which improperly rejects floats and is planned to be fixed in 3.2.1. On other versions, keep sending float in particular to support logging QRPp operation. (This depends on the api V1 key being configured; it defaults to float otherwise.)
- Added an example systemd user unit file to the documentation
- Fixed a build command that should never have worked (not sure how releases made it out before, but not motivated to look further).
Also, it became clear partway through this work that what had been a single tiny Go file that I had expected to barely ever touch was getting hard to navigate, so I refactored out into multiple files. I also updated the README in various ways.
-
I did not intend to spend several hours today making 3 releases full of new features to WaveLogGoat, but I did. One of them is a workaround for a regression in wavelog, but the rest are pure features!
- It now scales reported power by a max power setting. Defaults to 100 (100W) since percent equals watts on most shack rigs. If you have a 100W rig feeding a 500W dial-a-watt amp, set max power to 500W and even if the rig is reporting watts instead of percent, what is logged will be the watts coming out of the amp. If you have a 5W or 10W rig that shows 100W at full power when logged in wavelog via WaveLogGoat, set the max power to 5W or 10W, and it should become correct.
- mDNS support for talking to hamlib, rigctl, and wavelog using
.localaddresses (a.k.a. Avahi). Previously this didn't work unless you did a localCGO_ENABLED=1build in order to use the C library's resolver. I added explicit native Go support, so the binaries are still self-contained. - Log the version of wavelog (requires adding an api V1 key, separate from the api V2 key, because the version is not available under api v2.)
- Send power as int instead of float only if talking to wavelog 3.2.0 which improperly rejects floats and is planned to be fixed in 3.2.1. On other versions, keep sending float in particular to support logging QRPp operation. (This depends on the api V1 key being configured; it defaults to float otherwise.)
- Added an example systemd user unit file to the documentation
- Fixed a build command that should never have worked (not sure how releases made it out before, but not motivated to look further).
Also, it became clear partway through this work that what had been a single tiny Go file that I had expected to barely ever touch was getting hard to navigate, so I refactored out into multiple files. I also updated the README in various ways.
-
I did not intend to spend several hours today making 3 releases full of new features to WaveLogGoat, but I did. One of them is a workaround for a regression in wavelog, but the rest are pure features!
- It now scales reported power by a max power setting. Defaults to 100 (100W) since percent equals watts on most shack rigs. If you have a 100W rig feeding a 500W dial-a-watt amp, set max power to 500W and even if the rig is reporting watts instead of percent, what is logged will be the watts coming out of the amp. If you have a 5W or 10W rig that shows 100W at full power when logged in wavelog via WaveLogGoat, set the max power to 5W or 10W, and it should become correct.
- mDNS support for talking to hamlib, rigctl, and wavelog using
.localaddresses (a.k.a. Avahi). Previously this didn't work unless you did a localCGO_ENABLED=1build in order to use the C library's resolver. I added explicit native Go support, so the binaries are still self-contained. - Log the version of wavelog (requires adding an api V1 key, separate from the api V2 key, because the version is not available under api v2.)
- Send power as int instead of float only if talking to wavelog 3.2.0 which improperly rejects floats and is planned to be fixed in 3.2.1. On other versions, keep sending float in particular to support logging QRPp operation. (This depends on the api V1 key being configured; it defaults to float otherwise.)
- Added an example systemd user unit file to the documentation
- Fixed a build command that should never have worked (not sure how releases made it out before, but not motivated to look further).
Also, it became clear partway through this work that what had been a single tiny Go file that I had expected to barely ever touch was getting hard to navigate, so I refactored out into multiple files. I also updated the README in various ways.
-
Wavelog 3.2.0 is now available!
https://github.com/wavelog/wavelog/releases/tag/3.2.0
#Wavelog #AmateurRadio #HamRadio #hamr #radio #logging #logs #radiowaves #RadioLogging #HamLogging #OpenSource #FOSS #FLOSS
-
Wavelog 3.2.0 is now available!
https://github.com/wavelog/wavelog/releases/tag/3.2.0
#Wavelog #AmateurRadio #HamRadio #hamr #radio #logging #logs #radiowaves #RadioLogging #HamLogging #OpenSource #FOSS #FLOSS
-
Wavelog 3.2.0 is now available!
https://github.com/wavelog/wavelog/releases/tag/3.2.0
#Wavelog #AmateurRadio #HamRadio #hamr #radio #logging #logs #radiowaves #RadioLogging #HamLogging #OpenSource #FOSS #FLOSS
-
Wavelog 3.2.0 is now available!
https://github.com/wavelog/wavelog/releases/tag/3.2.0
#Wavelog #AmateurRadio #HamRadio #hamr #radio #logging #logs #radiowaves #RadioLogging #HamLogging #OpenSource #FOSS #FLOSS
-
Wavelog 3.2.0 is now available!
https://github.com/wavelog/wavelog/releases/tag/3.2.0
#Wavelog #AmateurRadio #HamRadio #hamr #radio #logging #logs #radiowaves #RadioLogging #HamLogging #OpenSource #FOSS #FLOSS
-
I have released WaveLogGoat v0.3.0 with all the rest of @DJ7NT's fixes and improvements that he'd reasonably given up on PRing back to me when I didn't notice that github wasn't telling me about PRs in my own project. 😭
The headline feature is TLS support for the websocket connection.
Power reporting for hamlib should also work normally now.
If you want a GUI, use WaveLogGate — it changed from an Electron app to a Go/Wails app so it is no longer a resource hog.
But if you like command-line, textual configuration, and something designed to run nicely as a systemd user unit? WaveLogGoat might be just your thing.
-
I have released WaveLogGoat v0.3.0 with all the rest of @DJ7NT's fixes and improvements that he'd reasonably given up on PRing back to me when I didn't notice that github wasn't telling me about PRs in my own project. 😭
The headline feature is TLS support for the websocket connection.
Power reporting for hamlib should also work normally now.
If you want a GUI, use WaveLogGate — it changed from an Electron app to a Go/Wails app so it is no longer a resource hog.
But if you like command-line, textual configuration, and something designed to run nicely as a systemd user unit? WaveLogGoat might be just your thing.
-
I have released WaveLogGoat v0.3.0 with all the rest of @DJ7NT's fixes and improvements that he'd reasonably given up on PRing back to me when I didn't notice that github wasn't telling me about PRs in my own project. 😭
The headline feature is TLS support for the websocket connection.
Power reporting for hamlib should also work normally now.
If you want a GUI, use WaveLogGate — it changed from an Electron app to a Go/Wails app so it is no longer a resource hog.
But if you like command-line, textual configuration, and something designed to run nicely as a systemd user unit? WaveLogGoat might be just your thing.
-
I have released WaveLogGoat v0.3.0 with all the rest of @DJ7NT's fixes and improvements that he'd reasonably given up on PRing back to me when I didn't notice that github wasn't telling me about PRs in my own project. 😭
The headline feature is TLS support for the websocket connection.
Power reporting for hamlib should also work normally now.
If you want a GUI, use WaveLogGate — it changed from an Electron app to a Go/Wails app so it is no longer a resource hog.
But if you like command-line, textual configuration, and something designed to run nicely as a systemd user unit? WaveLogGoat might be just your thing.
-
I have released WaveLogGoat v0.3.0 with all the rest of @DJ7NT's fixes and improvements that he'd reasonably given up on PRing back to me when I didn't notice that github wasn't telling me about PRs in my own project. 😭
The headline feature is TLS support for the websocket connection.
Power reporting for hamlib should also work normally now.
If you want a GUI, use WaveLogGate — it changed from an Electron app to a Go/Wails app so it is no longer a resource hog.
But if you like command-line, textual configuration, and something designed to run nicely as a systemd user unit? WaveLogGoat might be just your thing.
-
Hat hier jemand erfolgreich WSJT-X an Wavelog per API v2 key angebunden? Bei mir wills irgendwie nicht, "Test API" in WSJT-X schlägt fehl.
-
Hat hier jemand erfolgreich WSJT-X an Wavelog per API v2 key angebunden? Bei mir wills irgendwie nicht, "Test API" in WSJT-X schlägt fehl.
-
Hat hier jemand erfolgreich WSJT-X an Wavelog per API v2 key angebunden? Bei mir wills irgendwie nicht, "Test API" in WSJT-X schlägt fehl.
-
Hat hier jemand erfolgreich WSJT-X an Wavelog per API v2 key angebunden? Bei mir wills irgendwie nicht, "Test API" in WSJT-X schlägt fehl.
-
Hat hier jemand erfolgreich WSJT-X an Wavelog per API v2 key angebunden? Bei mir wills irgendwie nicht, "Test API" in WSJT-X schlägt fehl.
-
-
