Add Usermod for Power Measurement using esp's adc #4108
Conversation
This file contains 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
- Implement functions to measure power consumption
|
Please rebase your PR for 0_15 branch. |
- Implement functions to measure power consumption
|
Hey there, I'm not very familiar with Git, and it seems like I've messed something up. I was following your guide on how to properly submit a PR in the wiki, but I think I missed forking the other branches. I'd like to start over from scratch. |
|
Thank you so much for your help should I reverse the 712b72d commit? |
No. |
…pdate Update usermod "Battery" improved MQTT support
- disable JSON live - WS error string - button irelevant check
- provide LED types from BusManager for settings Credit: @netmindz for the idea.
Demystified some byte definitions of WiZmote ESP-NOW message
- move macros to constexpr methods - introduce type capabilities for UI - add phase shifting (POC) to PWM - replace PWM CIE LUT with calculated curve CIE & phase shifting credit @DedeHai
…scalc replaced PWM LUT with calculation
- LEDC: allocate same timer for CCT PWM - use SOC constants BusManager update - use allocateMultiplePins for BusPwm
- phase shifting correction (limit to PWM CCT)
Clarifications
Add semaphoring Determine CCT overlap
added `-D sqrt_internal=sqrtf` -> needed for good performance
Detect IRAM pointers if we can't be sure.
This is a platform feature that asks forgiveness for PROGMEM misuse: it adds a handler such that incorrectly used PROGMEM will work without crashing, just really, *really* inefficiently. Given that most of our real-world use cases for PROGMEM strings are relatively infrequent text calls, we can err on the side of developer convenience and address performance problems if and when they arise.
Replace with F() or PSTR() as appropriate.
Since oappend() is now strongly typed, pass the correct type. This is a step towards removing the extra shim logic on ESP8266.
This reverts commit 7d067d8.
Since oappend() is now strongly typed, pass the correct type. This is a step towards removing the extra shim logic on ESP8266.
Esp8266 oappend fix
Usermod F-string hygiene
Fix for LED and Scenes uncontrollable using Alexa. Weird behavior regarding to the device names and shared scenes fixed with this. Seen in issue Aircoookie/Espalexa#228 and fixed from @ams-hh Tested by myself and works just fine. Created second pull request here because the library seems to be a bit different from the official Espalexa repo. --------- Co-authored-by: Frank <[email protected]> Co-authored-by: Blaz Kristan <[email protected]>
- increase WLED_MAX_BUSSES for C3 (fixes Aircoookie#4215) - fix for Aircoookie#4228 - fix for very long running effect (strip.now, strip.timebase) - C++ API change to allow `seg.setColor().setOpacity()`
- fix for Aircoookie#4172 - fix for Aircoookie#4230 - /json/live enabled when WS disabled
WLED 0.15.0-b7 release
this chip has 16MB or 32MB flash, and requires .memory_type = opi_opi
Add support for ESP32-S3 WROOM-2 (solves Aircoookie#4099)
Avoiding name collisions with the 'delay' function.
Fixed point calculation for improved accuracy, dithering in debug builds only. Averaging and optional multiplier can be set as compile flags, example for speed testing with long averaging and a 10x multiplier: -D FPS_CALC_AVG=200 -D FPS_MULTIPLIER=10 The calculation resolution is limited (9.7bit fixed point) so values larger than 200 can hit resolution limit and get stuck before reaching the final value. If WLED_DEBUG is defined, dithering is added to the returned value so sub-frame accuracy is possible in post-processingwithout enabling the multiplier.
dithering is not really needed, the FPS_MULTIPLIER is a much better option.
Fixed & improved FPS calculation
… and update calculations
- Implement functions to measure power consumption
- Implement functions to measure power consumption
… and update calculations
…as-Kuchta-FPV/WLED-power-usermod into PR-Usermod-power-measurement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi WLED community,
As an intermediate coder and someone who has benefited from this project, I wanted to contribute by creating a usermod that measures power consumption using a voltage divider and a Hall current sensor.
Summary of Changes
There are still some issues that I would need some help with
Any feedback, suggestions, or assistance would be greatly appreciated!
Thank you for your support!