-
Notifications
You must be signed in to change notification settings - Fork 85
Troubleshooting Access Points
When you make your own Access Point consisting of an ESP32 or ESP32-S2, and a epaper tag, some things can go wrong. This page lists the most common errors.
Disable 'BSS Transition' on a Unify WiFi Access Point, because enabling seems to cause this. The WiFi stack of the esp32 is very simple, so sophisticated WiFi protocol enhancements might confuse it.
Pay very good attention on the correct wiring. If you use the pins as predefined in platformio.ini, you will be able to do OTA updates, which saves you a lot of time.
Pinout for ESP32 (Lolin32 lite): Use environment "Simple_AP":
| ESP32 pin | connect to tag pin |
|---|---|
| 5 | SS |
| 18 | CLK |
| 23 | MOSI |
| 19 | MISO |
| 2 | RESET |
| 13 + 15 | VCC |
| 17 | RX |
| 16 | TX |
| GND | GND |
Pinout for ESP32-S2 (Wemos S2 mini): Use environment "OpenEPaperLink_Mini_AP"
| ESP32-S2 pin | connect to tag pin |
|---|---|
| 11 | SS |
| 9 | CLK |
| 10 | MOSI |
| 8 | MISO |
| 13 | RESET |
| VCC | VCC |
| 6 | RX |
| 7 | TX |
| 12 | TEST |
| GND | GND |
There are many Wemos S2 mini clones with faults. Some of them reset during the establishment of the Wi-Fi connection. The reason for this is that the ENable line is not very stable. Luckily, it's easy to fix. You can place a capacitor of around 22uF between the legs of the reset switch or between EN and GND.
For a more in-depth explanation, you can refer to the following forum thread: Wemos S2 Mini Wi-Fi connection reset issue
Troubleshooting access points can be most easily done by viewing the UART log output using a method of your choice. If you are not familiar with getting log output, connect the access point to a computer using a USB cable with data support (if unsure, use a cable that you can reliably use to transfer files from your phone). Then use Chrome or another supported browser to go to the web flasher, press connect and select the USB Serial device that shows up. Then press Logs & Console.
Note: if your device is not recognized, you might need the relevant drivers. More instructions can be found here.
Can be seen by this log entry:
I wasn't able to connect to the AP radio. Did you flash it?
The build of this firmware expects an AP tag with TXD/RXD on ESP32 pins 18 and 17, does this match with your wiring?
Try to re-flash the AP itself. Go to Settings - Update and press Update ESP32-XX (for example ESP32-C6).
| Color Pattern | Meaning | UART Log Entry | Possible Solution |
|---|---|---|---|
| Aqua, Aqua, Red | Required power cycle | Please power-cycle your AP/device | Manually power-cycle your device |
| Red, Yellow, Red | Failed to bring up AP after flashing | Failed to bring up the AP after flashing seemed successful... | |
| Red, Yellow, Red | Unable to connect to AP radio | I wasn't able to connect to the AP radio. Did you flash it? | Go to settings -> update -> update ESP32 |
| Red, Yellow, Red | Soft power control issue | The firmware you're using expects soft power control over the AP tag; if it can't power-cycle the AP-tag using GPIO pin %d, this can cause this very same issue. | |
| Red, Red, Red | Failed to update version on AP | Failed to update version on the AP :( | |
| Yellow, Yellow, Red | Failed to reset AP | No related log entry found |