-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Freeze at startup during WiFi initialization #7
Comments
Hey! Awesome that you love the project so much! I'm really looking forward to your upcoming UI project 😄 It is normal that the effects stutter on boot (or even for a short time when sending a web request). This is because of the ESP being busy with other stuff immediately after the WiFi is connected (initialising Webserver, starting interfaces). I can attempt to mitigate it by refreshing the strip a few times between initialization steps, but I can't tell you yet whether that will help in any way. Either way, I can't think Preset 0 does currently not support saving since it is the default preset on boot. To be honest, I implemented it this way because it was easier at the time. It would be no problem to change it so that saving preset 0 would be the same as saving the LED settings with the "Ignore and use current color..." option enabled, which would improve the experience, I believe. You're welcome! I'm so glad you like the program! |
Yeah - i'm looking for some boot speed optimizations. I'm using the project for permanently inplace light strips around the house/kitchen tied to wall switches initial boot up is a noticable delay to last pre-set. I wonder if maybe something for hooking a burst over the pixel bus of the last preset using the ULP or something might mitigate this? I guess this is a general - better boot speed to last preset from cold state feature request. |
Hey! This issue has been open for quite some time without any new comments now. It will be closed automatically in a week if no further activity occurs. |
Merge from THATDONFC/Chris - WLED 0.10.0 Merge
First of all I want to get in line for further praises of this great project, thanks so much for all the effort that was put into it! I originally bought the SP108 before I became aware of this great project, yet it created a lot of headaches. I had a few spare ESP01Ses lying around and for the 5v vs 3v problem I found this neat little board for less than a euro on aliexpress where you just click your esp into and that takes care of the 5v. Since this setup now is already so great and striving for perfection is always fun I was wondering whether there is still work put into getting rid of the freeze during initialization issue... I want to put the whole setup behind an existing relay setup so it can easily be integrated in my home-automation and does not have always to be turned on. Since SP108 uses pretty much the same chip yet does not show a freeze during bootup there must be a way to do it. Looking at photos of it, it also seems the sp108 also does everything with one esp without any daughter board/chip lightening the load. I was wondering whether there might be a way to do parts of the initialization later or not all at once? I suppose people would not mind if you can't immediately access the web ui if that means no freezes during startup EDIT: Just in case some stumbles upon this - if was very wrong, since the SP108 actually has a separate controller which means this extra chip is also the reason the ESP does not have to carry all the load and you don't see a freeze during startup. On the one hand it means without an extra controller the very short freeze is something we have to live with on the other hand it makes me be even more amazed what WLED is capable of squeezing out of the ESP :) |
this is a band-aid fix for random crashes when switching between presets with multiple segments - crossfade disabled. !! adding type initializers fixed it for me on -S3, however I still see (less frequent) crashes on esp32, due to heap corruption. It took me hours to get a meaningful stackdump: assert failed: heap_caps_free heap_caps.c:360 (heap != NULL && "free() target pointer is outside heap areas") Backtrace: 0x40084ee1:0x3ffb2570 0x4008e341:0x3ffb2590 0x40094709:0x3ffb25b0 0x4008534a:0x3ffb26e0 0x40094739:0x3ffb2700 0x400e9037:0x3ffb2720 0x400e917c:0x3ffb2740 0x400eaeeb:0x3ffb2760 0x40117ec5:0x3ffb27c0 0x401184ea:0x3ffb2800 0x4013509d:0x3ffb2820 #0 0x40084ee1:0x3ffb2570 in panic_abort at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/esp_system/panic.c:402 #1 0x4008e341:0x3ffb2590 in esp_system_abort at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/esp_system/esp_system.c:128 #2 0x40094709:0x3ffb25b0 in __assert_func at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/newlib/assert.c:85 #3 0x4008534a:0x3ffb26e0 in heap_caps_free at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/heap/heap_caps.c:360 (inlined by) heap_caps_free at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/heap/heap_caps.c:345 #4 0x40094739:0x3ffb2700 in free at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/newlib/heap.c:39 #5 0x400e9037:0x3ffb2720 in Segment::deallocateData() at wled00/FX_fcn.cpp:189 #6 0x400e917c:0x3ffb2740 in Segment::resetIfRequired() at wled00/FX_fcn.cpp:206 (inlined by) Segment::resetIfRequired() at wled00/FX_fcn.cpp:203 #7 0x400eaeeb:0x3ffb2760 in WS2812FX::service() at wled00/FX_fcn.cpp:1216 (discriminator 2) #8 0x40117ec5:0x3ffb27c0 in WLED::loop() at wled00/wled.cpp:115 (discriminator 3) #9 0x401184ea:0x3ffb2800 in loop() at C:/src/wled00/wled00.ino:20 #10 0x4013509d:0x3ffb2820 in loopTask(void*) at C:/Users/user/.platformio/packages/framework-arduinoespressif32/cores/esp32/main.cpp:50 ELF file SHA256: 18c20b536f4c6ef4
Hey!
Still loving this project and still working on an API based HTML user interface 😄
Recently I was working on adding the presets, I've noticed that when the device now boots up with a fancy effect instead of a static colour, the effect seems to lag a bit and freezes for a moment during the first few seconds then goes to working normally. Is this just the hardware lagging when the WiFi connects or something?
Also it seems you can not update Preset 0, which is fine because you can change the boot preset to another number and update that. Just thought I'd note it as I thought I was doing something wrong for a while 😄
Thanks again! Do you have a contact email so I can send you the HTML UI I have been working on? I'm not very experienced with contributing via GitHub itself.
The text was updated successfully, but these errors were encountered: