Hi.
So, I've successfully connected the ESP32 80pin to the LAN8720a board. It does work, but I have questions/observations.
I've wired it up as per this image https://github.com/flusflas/esp32-ethernet
Firstly.
Is this how you would wire it up @MartinMueller2003 ? as per the image in the link.
And if so, do I need to connect any resistors in between some of the pins?
There seems to be some inconsistencies when it boots. Sometimes I need to press the reboot button to get it connected to the ethernet.
I am using pins 0, 2 and 4. to control 3 props.
The power led doesn't lights and I presume it's because I'm using pin 2 as an output instead of the internal LED.
Can I gain back the gpio that are assigned to the SD card now that I'm not using the sd card but the fields are still populated in ESP4
I think that's all for now.
Thanks
Yes you can use the SD card pins as outputs. FYI: It is always a bad idea to use GPIO 2 unless you provide a high impedance device that will not affect the internal usage of the pin at boot time.
You do not need to add external resistors. The internal pullups work just fine. In my code I list all of the pins in the gpio defs files so that you can use that to check your pin usage.
Thanks for that. What pin numbers do you recommend? I'm using 0 and 4, just need one more
Take a look at the quinled quad eth platform file.
#define DEFAULT_RMT_0_GPIO gpio_num_t::GPIO_NUM_16
#define DEFAULT_RMT_2_GPIO gpio_num_t::GPIO_NUM_3
#define DEFAULT_RMT_3_GPIO gpio_num_t::GPIO_NUM_1
#define DEFAULT_RMT_4_GPIO gpio_num_t::GPIO_NUM_4
Thank you. Got it working on the quad eth platform. Only thing I had to do was move the power on wire from pin 16 from the wiring diagram to pin 5 as per the default pin settings in ESPixelstick. I also had to change another setting on the network page from 0 to 1. I forget what it was called. Something about Physical MDIO.
HI @MartinMueller2003 great news. I have it working using the quinled quad eth file, but I have noticed some weird behavior.
1. As above the Physical MDIO defaults to 0 and the board id non accessable through Ethernet. I change it to one and I can access. This is where it can get weird. Sometimes it changes this back to 0 and I need to use the wifi to get back into the board to change back to 1.
2. Also when running the lights, every now and then the board goes offline, but then comes back after a couple of minutes. I still have the wifi function on to make sure I can access the board as above. But should I really turn off the wifi of the boards so it's ethernet only. I thought the wifi might be causing the boards to reboot if the signal fluctuates.
Thanks
You may be running out of ram. Try it with the WiFi turned off.
That may have done the trick. Testing last night went well. I test for a few more nights. Thanks again.
So, out of the 5 boards in test only one is still rebooting at random.
Could it be the amount of pixels running on the one output pin? I have 1224 pixels running from one output. I do get the warning in Xlights about exceeding 1024 pixels.
Do you think this could be the issue?
Just to be clear, I'm running a test sequence from FPP on a Raspberry pi. When I'm in test mode in FFP it doesn't reboot at all. But the sequence does.
Do you have the web UI turned on (browser connected). This uses a lot of memory as well. The ESP32 can run up to 3000 pixels on a single port. The output stage does not care. However, using DDP (or even worse, e!.31) does use more memory as the number of pixels go up. You might want to switch to using the ESPS in "FPP Remote" mode and save the sequences on an SD card attached to the ESPS. The QUAD SW does support this by using the AE+ board.
