Skip to content

Conversation

@weebl2000
Copy link
Contributor

@weebl2000 weebl2000 commented Jan 3, 2026

Change tx_power_dbm from uint8_t to int8_t to support negative TX power values. SX1262 for example allows down to -9 dBm.

  • NodePrefs.tx_power_dbm, setTxPower(), and radio_set_tx_power() across all variants: uint8_tint8_t
  • TX power constraint lower bound: 1-9
  • get tx CLI prints as signed value

@weebl2000 weebl2000 changed the base branch from main to dev January 3, 2026 21:02
Like SX1262 allows -9 dBm lowest, some allow lower but that probably
isn't useful
@liamcottle
Copy link
Member

Hey, thanks for the PR. Have you tested setting -9 tx power through the app and confirmed that it saves as still transmits?

@weebl2000
Copy link
Contributor Author

weebl2000 commented Feb 7, 2026

Hey, thanks for the PR. Have you tested setting -9 tx power through the app and confirmed that it saves as still transmits?

Had to parse as signed int, then it works. But the app needs to be changed to read the response as signed int too. Setting -9 now shows as 247 dBm - because the app is reading it as an unsigned int I guess.

Just a visual bug though, my companion still sends at -9 dBm and that works.

1000027079.mp4

@liamcottle liamcottle merged commit 10eacc4 into meshcore-dev:dev Feb 7, 2026
@liamcottle
Copy link
Member

liamcottle commented Feb 7, 2026

Great, thanks! Merged in. I've also updated the app to read as a signed int. This should be working through the web app if you force reload the page. It will also be available from the next mobile app update v1.39.0, older clients will just show as a high positive number.

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.

2 participants