WT32-ETH01

[iron]

Anyone has any experience with this ESP32 / LAN8720 module ?

Product Page :
http://www.wireless-tag.com/portfolio/wt32-eth01/

Datasheet:
https://tinyurl.com/WT32-ETH01

AliExpress:
https://www.aliexpress.com/item/1005001739834076.html

-D

[TD-er]

Have you tried the "eth" builds?

[iron]

Have you tried the "eth" builds?

Yeah, i have a few Olimex ESP32-POE working stable on the eth builds.

I wish there was support for more Enviroment and switch (MCP23017) devices.
(Not sure how a GPS module is useful to a wired module)

-D

[TD-er]

GPS can be useful to get a very accurate time, without any drift.
It is like an atomic clock.

And about the MCP23017 you mentioned...
I ordered it 8 days ago, so I guess it will be here soon.

[iron]

NTP, DST and Location settings work great for me in terms of time.

MCP23017 has been stable in ESP8266 for a long time now.

-D

[TD-er]

MCP23017 is part of P009.
The GPIO related stuff has now moved to be an internal command, so I guess it should now work on ESP32 too in the more recent builds.
Isn't it working?

[iron]

MCP23017 is not available on the eth .bin of the ESP32

-D

[iron]

Checking on Tasmota's work in an effort to save me any headache if possible on the WT32-ETH01 (should be coming in soon)

Code: Select all

 * {"NAME":"Olimex ESP32-PoE","GPIO":[1,1,1,1,1,1,0,0,5536,1,1,1,1,0,5600,0,0,0,0,5568,0,0,0,0,0,0,0,0,1,1,1,1,1,0,0,1],"FLAG":0,"BASE":1}
 * GPIO12 = ETH POWER
 * GPIO18 = ETH MDIO
 * GPIO23 = ETH MDC
 * #define ETH_TYPE          ETH_PHY_LAN8720
 * #define ETH_CLKMODE       ETH_CLOCK_GPIO17_OUT
 * #define ETH_ADDR          0
 *
 * {"NAME":"wESP32","GPIO":[0,0,1,0,1,1,0,0,1,1,1,1,5568,5600,1,0,0,0,0,1,0,0,0,0,0,0,0,0,1,1,1,1,1,0,0,1],"FLAG":0,"BASE":1}
 * GPIO16 = ETH MDC
 * GPIO17 = ETH MDIO
 * #define ETH_TYPE          ETH_PHY_LAN8720
 * #define ETH_CLKMODE       ETH_CLOCK_GPIO0_IN
 * #define ETH_ADDR          0
 *
 * {"NAME":"WT32-ETH01","GPIO":[1,1,1,1,1,1,0,0,1,0,1,1,3840,576,5600,0,0,0,0,5568,0,0,0,0,0,0,0,0,1,1,0,1,1,0,0,1],"FLAG":0,"BASE":1}
 * GPIO16 = Force Hi
 * GPIO18 = ETH MDIO
 * GPIO23 = ETH MDC
 * #define ETH_TYPE          ETH_PHY_LAN8720
 * #define ETH_CLKMODE       ETH_CLOCK_GPIO0_IN
 * #define ETH_ADDR          1
 *
\*********************************************************************************************/

Seems GPIO18 and 23 are common. In the Olimex board I use GPIO12 as "Ethernet Power pin:"
I wonder if it is as simple as choosing GPIO16 as on arendst's code above ?

[TD-er]

Have you tried the ETH builds?
I do have all Olimex ETH boards running here for months and all configurations they use are working very well in ESPEasy.

[iron]

Have you tried the ETH builds?
I do have all Olimex ETH boards running here for months and all configurations they use are working very well in ESPEasy.

Seems like you missed the last part of my post below the code.

The eth bins work great on the Olimex ESP32-PoE units I have on hand.

I am now expecting to receive the WT32-ETH01 units and was wondering on the GPIO settings for that, therefore I looked into arendst's code.

[TD-er]

Judging the code you posted from Tasmota, it indeed looks like the GPIO16 pin may be connected as power enable pin.
But I wonder why it is marked for the Olimex as "ETH POWER" and on the WT32-ETH01 as "Force Hi".
That sounds like it may be a bit different.

Here it is suggested it is indeed the power pin: https://community.home-assistant.io/t/e ... /110390/65

[Rub87]

Hi,

Im pretty fresh to these iot stuff but I admire it. I have a domoticz setup running but would now like to expand it in areas without wifi or zwave coverage, like a gate and in basement and in my garden to control rgbw led fllood lights. The PoE makes it also very versatile for my needs.

Is there a chance the espeasy would also run onto the wesp32? I read the blog of the creator and it seems for the novice eye perfect for my needs and I would like to support him also using his boards. But ffcourse I am not into programming so as a almost end user I would need to have some feeling how good the ESPEasy firmware would suit this hardware.

https://hackaday.io/project/85389-wesp3 ... et-and-poe
https://wesp32.com/

If not I will need to use the Olimex ISO esp32 board.

thanks in advance

[TD-er]

Taken from the product brief: https://wesp32.com/files/wESP32-Product-Brief.pdf (page 8)

• Ethernet PHY type is Microchip LAN8720
• PHY address is 0
• EMAC clock mode is GPIO0 input
• Use PHY power pin is disabled
• SMI MDC pin is 16, SMI MDIO pin is 17

So based on that I would expect it will work just fine with ESPEasy.

[enesbcs]

Checking on Tasmota's work in an effort to save me any headache if possible on the WT32-ETH01 (should be coming in soon)

Code: Select all

 * {"NAME":"WT32-ETH01","GPIO":[1,1,1,1,1,1,0,0,1,0,1,1,3840,576,5600,0,0,0,0,5568,0,0,0,0,0,0,0,0,1,1,0,1,1,0,0,1],"FLAG":0,"BASE":1}
 * GPIO16 = Force Hi
 * GPIO18 = ETH MDIO
 * GPIO23 = ETH MDC
 * #define ETH_TYPE          ETH_PHY_LAN8720
 * #define ETH_CLKMODE       ETH_CLOCK_GPIO0_IN
 * #define ETH_ADDR          1
 *
\*********************************************************************************************/

Seems GPIO18 and 23 are common. In the Olimex board I use GPIO12 as "Ethernet Power pin:"
I wonder if it is as simple as choosing GPIO16 as on arendst's code above ?

Yes, i have tested with ESP_Easy_mega_20201102_custom_ESP32_4M316k_ETH-factory.bin binary and WT32-ETH01 works fine.

Code: Select all

Preferred network: Ethernet
Ethernet PHY type: LAN8710
Ethernet PHY Address: 1
GPIO MDC: GPIO-23
GPIO MIO: GPIO-18
GPIO POWER: GPIO-16
Ethernet Clock: External crystal oscillator