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
ESPixelStick-4.0-beta5 Multi LED Protocol Output Bug #732
Comments
I just configured WS2811 on port 1, UCS1903 on ports 5 & 6 (8 port device) from a clean start and did not have a crash and it is working fine. NOTE: A change in protocol on a port requires a reboot since the IDF drivers do not properly support disconnecting an output. So if you changed from DMX to UCS1903 on a port then there is an expected reboot. After the reboot it should come up in the desired mode. I did not see it come up in the disabled mode after a protocol was selected. Please post a screenshot of the admin page. Please ensure you are running the latest dist found here: https://github.com/MartinMueller2003/ESPixelStick/releases |
@MartinMueller2003 thank you for looking into this. I changed my steps based on what you suggested and it appears to be more stable.
|
That is not quite what I meant. :) I just configured 5 outputs at the same time (single save) and it did not crash. It WILL reboot (not a crash) if you change the output type after an output has been configured. This is needed due to limitations of the RMT low level driver. |
2024-01-18_13-26-58.mp4Thank you. I really appreciate the support and knowledge. Yes gotcha but you got me thinking about performing more saves. I have uploaded a video of this happening. 40s-60s you can see that I have defined multiple outputs and then around 55s everything resets. Another thing that I just noticed is that the pixel count defaults to 100 when issue occurs. If it defaults to the proper count then everything seems to work? |
That build is not the latest build and a lot of issues have been fixed since then. Please use the newest dist.zip from https://github.com/MartinMueller2003/ESPixelStick/releases |
I have tried multiple times to recreate this and it does not happen on my card. Not sure what to do next. It looks to me as if you are having a file corruption issue. That is in the framework code. Not easy to debug. |
No problem. If other people have similar issues LMK and I can troubleshoot
it with you real time. Like I said I can make it work but takes brute
force but once the settings stick it seems stable for at least 4hrs. (The
length of my test)
Thanks again
…On Tue, Feb 27, 2024 at 4:54 AM Martin Mueller ***@***.***> wrote:
I have tried multiple times to recreate this and it does not happen on my
card. Not sure what to do next. It looks to me as if you are having a file
corruption issue. That is in the framework code. Not easy to debug.
—
Reply to this email directly, view it on GitHub
<#732 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFNSK5W6QIMI5JC254P5NTDYVXJPBAVCNFSM6AAAAABB7K6RW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRWGQ4DGMZQGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
No one else is reporting such an issue. |
--------- Instructions --------
Please provide answers directly below each section.
--------- Instructions ---------
ESPixelStick Firmware Version
4.0-beta5
Hardware Version
sp32_quinled_dig_octa
Binary release or compiled yourself?
Binary
Operating System (and version)
Win11
Web Browser (and version)
Chrome Version 120.0.6099.224 (Official Build) (64-bit)
Access Point
?? Not sure what this means
Describe the bug
Hi, I'm using the SD card to play a remote sequence from xLights and it works fine if all device output settings have the same protocol. (WS2811 for example) There is a an error that crashes the board and resets the output configuration to "disabled"
Steps to reproduce:
Another thing to note is that the file management tab... The date/time of the uploaded file is not correct...
Screenshots.pdf
The text was updated successfully, but these errors were encountered: