-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
v0.14.1-b2: ESP8266 fade issue with Breathe effect on Solid and the freeze function #3643
Comments
Related: |
Please power your strip from a separate power supply. 1m strip with 144 LEDs/m requires 8A of current at full brightness. |
I see the same behavior when using two segments on 16x16 matrix , I do not think this is HW related |
Please post your configuration and picture of HW set up. As mentioned above there are no interactions between different segments (apart from ABL) to do that. |
I was actually testing with a remote unit using ddp but sure if you disable limiter the issue is no longer there |
Makes sense to explain the behaviour with ABL (auto brightness limiter).
--> segment1 seems to fade or flicker. This would be expected behaviour. @casesolved-co-uk please try this:
|
@softhack007 thanks for the explanation, ABL explains the effect interaction and goes away with ABL disabled. It cannot be a current issue in this case as the power is being fed directly to the board where the 3 LEDs are fading out. Plus the behaviour is clearly software controlled. Current is 0.7A with ABL enabled and rises to 1.4A with it disabled, including 0.2A for the board. And the freeze issue goes away too. Since we're on the subject, does ABL only apply to onboard busses and is ignored for external busses, e.g. on the network? |
Yes. |
What happened?
See video for the interaction between the Breathe Effect and Solid:
2024-01-03_21-37-09.mp4
To Reproduce Bug
Follow the video
Expected Behavior
Solid remains solid, freeze freezes the segment and prevents changes
Install Method
Binary from WLED.me
What version of WLED?
v0.14.1-b2
Which microcontroller/board are you seeing the problem on?
ESP8266
Relevant log/trace output
No response
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: