Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TX Power Control issues #46

Closed
terrillmoore opened this issue Jan 28, 2018 · 1 comment
Closed

TX Power Control issues #46

terrillmoore opened this issue Jan 28, 2018 · 1 comment
Assignees
Labels
Projects

Comments

@terrillmoore
Copy link
Member

terrillmoore commented Jan 28, 2018

Per @Cyberman74

For me it seems LMiC code in radio.c selecting the PA Output pin of SX1276 is erroneous. Always Pin PA_BOOST is selected. This can cause malfunction, if board hardware does not wire this pin, because it uses the RFO_HF / RFO_LF pins only.

Code review and checking datasheet says that current code does not actually activate high-power on PA_BOOST. It always sets RegPaDac bits 2:0 to 4. Datasheet says that to activate high-power on PA_BOOST, RegPaDac bits 2:0 must be set to 7.

However, bit 7 of RegPaConfig is always set to 1, so the output port is always the PA_BOOST at +17dBm (section 5.4.3).

There are a number of constraints on duty cycle, etc., in section 5.4.3 when using +20 dBm mode.

See also #50 (just simple errors in power-setting code).

More entries are needed in the lmic_pinmap structure to specify the board configuration re LF/HF/PA_BOOST pins of the radio. This should be combined with the SPI setting changes for #37.

For additional background see mcci-catena/ibm-lmic#15 and matthijskooijman#33.

@terrillmoore
Copy link
Member Author

Based on input from #300, and review of the Semtech reference code, and review of datasheets, I have a patch that addresses this for the 1272 and 1276. See 49b495d and successors.

terrillmoore added a commit that referenced this issue Jun 23, 2019
Fix #46: make Tx Pwr policy explicit; see #300 (WIP). Also fix #261, #262, #321, and #263.
@terrillmoore terrillmoore moved this from To do to Done in Vnext Sep 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Vnext
  
Done
Development

No branches or pull requests

1 participant