NRF52 Companion Power Optimizations and UI Support for XIAO NRF52 #1122
+77
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
According to the documentation and experiments on other boards using NRF52 + SX1262 this reduces the power consumption significantly. This assumes that the hardware actually has the inductor for the internal DC/DC regulator populated which is very likely. Even if not, it won't hurt. Signed-off-by: Frieder Schrempf <frieder@fris.de>
This ensures that the SX1262 and the antenna switch is properly put into low-power sleep. This reduces the power consumption in the off-state significantly and increases "shelf-life" of companion nodes. Signed-off-by: Frieder Schrempf <frieder@fris.de>
Use the blue LED as status LED. This prevents the blue LED from being always-on and draining the battery. Instead use it as status LED with blink patterns as other companion devices do. Signed-off-by: Frieder Schrempf <frieder@fris.de>
This ensures that the SX1262 and the antenna switch is properly put into low-power sleep. This reduces the power consumption in the off-state significantly and increases "shelf-life" of companion nodes. Signed-off-by: Frieder Schrempf <frieder@fris.de>
This reduces the power consumption by approximately 25%. Signed-off-by: Frieder Schrempf <frieder@fris.de>
The Xiao nRF52840 combined with the Wio-SX1262 is often used for cheap and compact DIY companion nodes. The Wio actually has an onboard pushbutton that can be used as user button. Enable support for the button. Signed-off-by: Frieder Schrempf <frieder@fris.de>
Add the necessary code to properly power-off the Xiao + Wio companions. This way we can achieve around 15 microamps of power consumption in the off state. Signed-off-by: Frieder Schrempf <frieder@fris.de>
The current logic only works for active high LEDs. Some boards need an active low level control and therefore they set LED_STATE_ON to 0. Take this into account and use the correct LED pattern for both cases. Signed-off-by: Frieder Schrempf <frieder@fris.de>
Fix the active state of the LEDs (active low) and enable the status LED. Signed-off-by: Frieder Schrempf <frieder@fris.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a collection of small changes that improve the power consumption for some NRF52-based companion devices and adds UI (LED & user button) support for the XIAO NRF52 + Wio-SX1262.
Changes
Seeed SenseCAP T1000-E
RAK WisMesh Tag
Seeed XIAO NRF52 + Wio-SX1262
LED_STATE_ON=0and enable status LEDRemarks
The power optimizations were only done for devices that I was able to do tests on. There are other devices that could probably benefit from the same changes. Unfortunately the current code structure doesn't make it easy to implement this for the whole NRF52 platform.
The way
radio.sleep()is called is not great (global functions,externaldeclaration, etc.). Unfortunately a better way is not possible without major refactoring. Actually in the future it would be better to implement this not on the board level, but on the companion app level, soradio.sleep()would be called for any device in case of power-off.