Skip to content

Fix for Rx boosted gain on LR1110#2844

Open
oltaco wants to merge 4 commits into
meshcore-dev:devfrom
oltaco:fix-rx-boosted-gain
Open

Fix for Rx boosted gain on LR1110#2844
oltaco wants to merge 4 commits into
meshcore-dev:devfrom
oltaco:fix-rx-boosted-gain

Conversation

@oltaco

@oltaco oltaco commented Jun 25, 2026

Copy link
Copy Markdown
Member

This PR fixes Rx boosted gain not being applied on LR1110 and improves the error handling when setting Rx boosted gain.

Previously LR1110 was never getting Rx boosted gain set due to an overly narrow guard condition in MyMesh. Nobody noticed that the override wasn't getting called because the call was void and the default was no-op so there was no error to report.

I have changed setRxBoostedGain() and setRxBoostedGainMode() to return bool and the default is to return false. Now errors can propagate back to CommonCLI so that we know when radio.rxgain is unsupported or the radio returned an error.

Tested on LR1110 (T1000e) and (RAK 4631).

Confirmed building on SX1268 (Meshadventurer) and ESPNOW (Heltec V3), untested but should be fine.

Comment thread variants/t1000-e/platformio.ini Outdated
Comment thread platformio.ini Outdated
@oltaco oltaco force-pushed the fix-rx-boosted-gain branch from a9cfacb to b07aba7 Compare June 25, 2026 22:45
@oltaco

oltaco commented Jun 25, 2026

Copy link
Copy Markdown
Member Author

Thanks @recrof didn't mean to include those 👍

Comment thread src/helpers/CommonCLI.cpp

@ViezeVingertjes ViezeVingertjes left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM; did open a PR to yours with a few suggestions but those are more style/cleanup, so not mandatory. 👍🏼

(Still having nightmares of the LR1110 deafness problems when i read that type haha)

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.

4 participants