The ESP32-PoE-ISO_AP is based on Olimex ESP32-POE-ISO-WROVER(-EA) https://www.olimex.com/Products/IoT/ESP32/ESP32-POE-ISO/open-source-hardware
It has a SD Card slot that is used to store all filesystem data on SD. Use the prepare_sdcard.sh script to copy all needed data to an empty SD card that is formatted with FAT filesystem. The AP firmware will format the SD if an unformatted or from formatted card is used. This can be used to intially prepare an empty SD card for usage.
For tag communication a ESP32-C6-WROOM-1(U) is used with the following connection scheme:
| ESP32-PoE-ISO | ESP32-C6-WROOM-1 |
|---|---|
| GPIO5 EN | |
| GPIO13 | GPIO9 |
| GPIO36 | GPIO3 |
| GPIO4 | GPIO2 |
| GPIO33 | GPIO24 |
| GPIO32 | GPIO25 |
| GPIO8 pullup 5.1k |
The ESP32_C6 can be mounted like this to get a compact assembly:
The AP has support for PoE/Ethernet, for that the new added Ethernet support allows to make the network/internet connection via LAN cable instead of WiFi. LAN is preferred, if a LAN cable is connected and a valid IP configuration via DHCP can be obtained, WiFi is switched off. If the LAN cable is disconnected, a fall back to WiFi is done.
Use those defines in platform.ini for PHY settings:
- ETHERNET_PHY_POWER: IO pin where the PHY can be switched of/on, can be -1 if not used.
- ETHERNET_CLK_MODE: PHY clock mode, see eth_clock_mode_t in ETH.h0
- ETHERNET_PHY_MDC: PHY MDC pin
- ETHERNET_PHY_MDIO: PHY MDIO pin
- ETHERNET_PHY_TYPE: PHY type, see eth_phy_type_t in ETH.h
Limitations:
only DHCP is supported, no static IP configuration for LAN so far. If GPIO0 is used for one of the ETHERNET_CLK_MODE modes, then GPIO0 cannot be used to clear the WiFi configuration.