-
-
Notifications
You must be signed in to change notification settings - Fork 651
Force LDO option set or unset #668
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
Conversation
Some remote clients needs LDO using on any Spreading Factor. CDEbyte E32 for example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @zbx-sadman,
Thanks for taking the time to open this pull request, what do think about splitting the API to enableLowDataRateOptimize()
and disableLowDataRateOptimize()
?
Hello @sandeepmistry Library author known better how to make his code pretty and readable, i guess. Honestly, i modified source a bit deeper and it can be written now as follows: LoRa.h
LoRa.cpp
Let me know if i must create another pull-request. Thanks for your helpful library. |
Hi @zbx-sadman, Thanks for considering the feedback, I would suggest making the |
Hello @sandeepmistry, i've add separated setter methods for LDO flag. |
@zbx-sadman yes, that looks good. I've pushed some minor changes in 1928aab to update the |
Some remote clients needs LDO using on any Spreading Factor. CDEbyte E32 (and similar) modules for example.