Skip to content
New issue

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

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

Already on GitHub? # to your account

correctly manage transmission power with addition of a MAX_RFO_PWR se… #300

Closed
wants to merge 1 commit into from

Conversation

disk91
Copy link

@disk91 disk91 commented Apr 4, 2019

…tting
The objective is to correctly manage the TX power setting on sx1276 with an optimal current consumption.
The MAX_RFO_PWR allows to set the limit between use of PA_BOOST vs RFO. When the device does not have RFO connected like for RFM95 this setting must be set to 0.

@terrillmoore
Copy link
Member

Hi, thanks for your input. This looks like it will address #46, which has been on the list for some time.

Unfortunately, your patch doesn't compile. Perhaps there's a missing commit to a header file? For example:

lib/arduino-lmic/src/lmic/radio.c: In function 'configPower':
lib/arduino-lmic/src/lmic/radio.c:459:22: error: 'MAX_RFO_PWR' undeclared (first use in this function)
} else if ( pw > MAX_RFO_PWR ){
^
lib/arduino-lmic/src/lmic/radio.c:459:22: note: each undeclared identifier is reported only once for each function it appears in

Best regards,
--Terry

@disk91
Copy link
Author

disk91 commented Apr 8, 2019

project_config/lmic_project_config.h has also been patched for declaring MAX_RFO_PWR ; it's part of the pull request. Did you add this line to your file ?

@terrillmoore
Copy link
Member

Please see travis build log. First step is to pass travis builds, without that we can't make progress. The ESP32 logs are easier to follow than the others, because there's less build-system noise. Click on the Details button for the failing build, and dig down to the ESP32 build.

In any case, your commit did not include the project_config file, and so that didn't get updated in Travis, which is why the build is broken.

We may need to reorganize; MAX__RFO_POWER, if it's a user configurable item, needs to go into the configuration table, rather than being a compile parameter, because Arduino compile-time config is such a headache. It looks like it's only one byte, so this is easy. But first step is to get a clean build. Thanks!

@terrillmoore
Copy link
Member

I have used some of the ideas from this, but because of the need to get policy from the user's configuration, my implementation is substantially different. See #46 and related pull requests.

@terrillmoore terrillmoore self-assigned this May 20, 2019
terrillmoore added a commit that referenced this pull request Jun 23, 2019
Fix #46: make Tx Pwr policy explicit; see #300 (WIP). Also fix #261, #262, #321, and #263.
@terrillmoore
Copy link
Member

Superseded by #319

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants