Skip to content

Conversation

@mattmelling
Copy link

We currently read the mode and bandwidth from hamlib as

? p
USB 2400

However hamlib actually returns these as separate lines:

? p
USB
2400

The extra line causes the next read (power) to consume the second line (bandwidth), leading to incorrect power settings being reported to hamlib.

The correct command to read the power level setting from hamlib is

? l RFPOWER
0.5

(l = level, this is read RF power level)

Fixes #4 and uses the correct command to read the RF power level.

@mattmelling mattmelling force-pushed the fix-hamlib-power branch 2 times, most recently from 9cd0327 to 7d399f1 Compare December 31, 2025 16:35
@mattmelling mattmelling changed the title Discard bandwidth from hamlib mode report Discard bandwidth from hamlib mode report, use correct level command to request RF power Dec 31, 2025
@mattmelling mattmelling marked this pull request as ready for review December 31, 2025 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Incorrect power sent to Wavelog for hamlib

1 participant