Aircoookie
Ethernet doesn't work when LEDs are set to LPD6803.
What happened?
I have a Dig-Uno connected to LPD6803 leds. I have been doing my initial tests over wifi and that has worked to get everything started.
But I want to be able to control via ArtNet so I have been planning to do wired ethernet for that. (Art Net stutters over our wifi) When I plug in the ethernet the LEDs on the dig-uno and on the router light up. but the Dig Uno stayed connected to Wifi. I tried deleting the wifi settings to see if that would make it connect to ethernet. but then it just didn't connect at all.
Ethernet type is set to "QuinLED-ESP32"
I tested all my network things, but it seemed like a problem with the Dig Uno, so I grabbed another one I had laying around and connected it to the same ethernet port cable and it worked and connected to ethernet.
So I went to just change the settings on that one to work with my LPD6803 leds. when I changed the settings it stopped connecting to ethernet.
I tested all the settings that I changed one at a time, and it is when I change the leds to LPD6803 that the ethernet stops working.
To Reproduce Bug
Set LEDs to LP6803.
Ethernet Stops working
Expected Behavior
Ethernet works.
Install Method
Self-Compiled
What version of WLED?
WLED 0.14.0 (build 2310130)
Which microcontroller/board are you seeing the problem on?
ESP32
Relevant log/trace output
Anything else?
No response
Code of Conduct
- [x] I agree to follow this project's Code of Conduct
@TMKvamme the first thing you could check is the two pins you entered in LED settings. You led pins should never overlap with ethernet pins, otherwise ethernet will not work.
https://github.com/wled/WLED/blob/fe33709eb00dc8a9edb4ffd8902bc591c3f85627/wled00/network.cpp#L58-L68
and
https://github.com/wled/WLED/blob/fe33709eb00dc8a9edb4ffd8902bc591c3f85627/wled00/network.cpp#L10-L17
This issue feels similar to https://github.com/wled/WLED/issues/2542 since those are other clock based LEDs that broke ethernet. Not sure if that means they are actually related...
@TMKvamme good point, it also reminds me of this
- https://github.com/wled/WLED/issues/4703
(scroll down to "What can users do to mitigate the hardware bug")
If you want to connect to the controller via Ethernet:
- Disable the ESP-NOW remote support. (It's off by default in WLED's settings, though.)
- Do not use the WLED-AP WiFi connection. Always use the Ethernet port's IP instead.
It seems that the esp32 clock chip has a major problem, that leads to various strange effects. As your LEDs are also clock based, the problems might indeed have a common root cause.
@TMKvamme maybe take a look at the discussion in the "other" ethernet-related bug report. I've tried to make an overview of usable PINs that seems to be free on any eth-enabled board, maybe it helps to find two good pins for your led strip.
- #5155
I went through and tried all the "OK" or "?" pins.
I first set the LED type to ws281X Got ethernet connected and working. Then changed LED type to LPD6803 I left the Data Pin as 16 and made the Clock PIn to the next pin I was testing in the list. Each time when I clicked save it broke the ethernet connection.
I would power cycle, then it would connect via WIFI. I changed back the LED type to WS281X, got ethernet working again and tried the test again on the next pin.
Each of the pins broke ethernet.
Did I test that properly? Anything else you suggest I try?
(I was able to get better ArtNet performance over wifi by changing to unicast from multicast now that I have everything else set up. So while I would still prefer wired, I've at least got it useable on wifi now, but still happy to help test anything I can.)
I left the Data Pin as 16
Please also change the data pin, gpio16 seems to be one of the problematic pins, too.
I tried every combo of "OK" pins 4,13,20 for data and clock and all of them broke ethernet. 24 was on the list as OK but in settings it is red and says unusable. (forgot to mention that is the last tests)