Save此ESP_AT_WIFIMANAGER庫基於,修改,錯誤固定和改進:
Tzapu WiFiManagerKen Taylor WiFiManagerKhoi Hoang's ESP_WiFiManager為了支持NRF52,SAM Due,SAMD,STM32F/L/H/G/WB/MP1,Raspberry_pi_pico等。使用ESP8266/ESP32-AT-Command Shields板。
目前,使用Earle Fillhower的Arduino-Pico Core或Arduino-Mbed RP2040 Core提供了基於RP2040的板,例如Nano_RP1040_Connect Raspberry_pi_pico ,具有Blynk /wifimanager功能,使用了Earle Fillhower的Arduino-PiCo Core或Arduino-Mbed RP2040 Core。
由於沒有足夠的內存來運行Config Portal Weberver,因此不支持AVR家庭板(Mega,Uno,Nano等)。
這是帶有後備Web配置門戶的憑證 / WiFi連接管理器。
Web配置門戶網站,從ESP8266/ESP32-AT-command shields提供的訪問點(AP),帶有可配置的靜態IP地址或使用192.168.4.1的默認IP地址
您還可以指定靜態AP和STA IP。配置門戶將被自動調整以匹配動態自定義參數的數量。憑據保存在EEPROM, FlashStorage_SAMD , FlashStorage_STM32 , DueFlashStorage或nrf52/rp2040 littlfs中。
此ESP_AT_WIFIMANAGER庫當前支持以下董事會:
NRF52板,例如Adafruit Feather NRF52832,NRF52840 Express,Bluefruit Sense,Itsy-Bitsy NRF52840 Express,Metro NRF52840 Express,NINA_B302_UBROX,NINA_B112_UBROX等
山姆到期
SAMD21
Teensy(4.1、4.0、3.6、3.5、3,2、3.1、3.0,LC)
STM32F/L/H/G/WB/MP1板(帶有64+K閃存)
基於RP2040的板,例如Nano RP2040 Connect ,使用Arduino Mbed OS作為納米板。
使用Arduino-Mbed RP2040 Core或Earle Fillhower的Arduino-Pico Core,例如RASPBERRY_PI_PICO,ADAFRUET_FEATER_RP2040和GENTIC_RP2040等基於RP2040的董事會。
Wiznet_wizfi360_evb_pico使用earle fillhower's arduino-pico核心

ESP8266-AT-command ShieldESP32-AT-command ShieldW600和WIS600-01S AT-Command ShieldWizFi360 AT-Command Shield 
Arduino IDE 1.8.19+ for Arduino。Arduino AVR core 1.8.6+ for Arduino(使用Arduino董事會經理),用於AVR板。Arduino Core for STM32 v2.4.0+ sTM32F/L/H/G/WB/MP1板(nucleo-144 nucleo_f767zi,nucleo-64 nucleo_l053r8等)。Teensy core v1.57+ Teeensy 4.1。Arduino SAM DUE core v1.6.12+ SAM餘臂Cortex-M3板。Arduino SAMD core 1.8.13+ 。Adafruit SAMD core 1.7.11+用於SAMD ARM Cortex-M0+和M4板(Nano 33 IoT等)。Seeeduino SAMD core 1.8.3+ 。Adafruit nRF52 v1.3.0對於NRF52板,例如Adafruit NRF52840_Feather,nrf52832_feather,nrf52840_feather_sense,nrf52840_itsybitsy NRF52840_METRO,NRF52840_PCA10056,erentar_xenon, nina_b302_ublox ,等等。Arduino mbed_rp2040 core 3.5.4+用於Arduino RP2040的板,例如Arduino Nano RP2040 Connect,Raspberry_pi_pico等。Earle Philhower's arduino-pico core v2.7.1+用於RP2040的董事會,例如Raspberry_pi_pico,adafruit_feather_feather_rp2040和generic_rp2040 ,等等。ESP8266_AT_WebServer library v1.7.1+能夠支持ESP32-AT盾牌。要安裝,請檢查FlashStorage_SAMD library v1.3.2+ samd21和samd51板(零,mkr,nano_33_iot,m0,m0,m0 pro,adafruit ity-bitsy m4等)。 。或Platform.io FlashStorage_SAMD library v1.0.0+ samd21和samd51板(零,mkr,nano_33_iot,m0,m0,m0 pro,adafruit ity-bitsy m4等)FlashStorage_STM32 library v1.2.0+ for stm32f/l/h/h/g/wb/mp1板。安裝。查看DueFlashStorage library v1.0.0+ SAM Due。要安裝,請檢查Adafruit's LittleFS/InternalFS 。Ai-Thinker AT Firmware v1.5.4或AT Firmware v1.7.4.0的AI-INCHER,用於ESP8266-AT Shields。AT version_2.1.0.0_dev用於ESP32-AT盾牌。AT version_1.1.4 。 Ai-Thinker AT Firmware v1.5.4
AT version: 1.1.0.0 (May 11 2016 18 : 09 : 56 )
SDK version: 1.5.4 (baaeaebb)
Ai-Thinker Technology Co. Ltd.
Jun 13 2016 11 : 29 : 20 AT Firmware v1.7.4.0
AT version: 1.7.4.0 (May 11 2020 19 : 13 : 04 )
SDK version: 3.0.4 (9532ceb)
compile time:May 27 2020 10 : 12 : 17
Bin version (Wroom 02 ):1.7.4 WIS600-01S和W600使用ESP8266或ESP32-AT命令和庫存固件
AT version: 1.1.4 (Dec 05 2018 11 : 06 : 45 )
SDK version: 3.0.0
Dec 05 2018 11 : 06 : 45 AT version_2.1.0.0_dev
AT version: 2.1.0.0 -dev(4f6b92c - Jun 10 2020 10 : 36 : 54 )
SDK version:v4 .0.1 - 193 -ge7ac221b4
compile time (b85a8df):Jun 18 2020 14:00:59
Bin version:2.0.0(WROOM- 32 )請參閱command core和esp_at_get_started的說明
AT Firmware v1.7.4.0上載bin文件以糾正以下位置: # BOOT MODE
### Flash size 8Mbit: 512KB+512KB
boot_v1.2+.bin 0x00000
user1.1024.new.2.bin 0x01000
esp_init_data_default.bin 0xfc000
blank.bin 0x7e000 & 0xfe000
### Flash size 16Mbit-C1: 1024KB+1024KB
boot_v1.2+.bin 0x00000
user1.2048.new.5.bin 0x01000
esp_init_data_default.bin 0x1fc000
blank.bin 0xfe000 & 0x1fe000
最好和最簡單的方法是使用Arduino Library Manager 。搜索ESP_AT_WiFiManager ,然後選擇 /安裝最新版本。您也可以使用此鏈接以獲取更詳細的說明。
ESP_AT_WiFiManager-master.zip 。ESP_AT_WiFiManager-master目錄ESP_AT_WiFiManager-master文件夾到Arduino庫的目錄,例如~/Arduino/libraries/ 。要能夠在NRF52840/NRF52832板上進行編譯,運行和自動檢測和顯示board_name ,您必須將整個NRF52 packages_patches目錄複製到Adafruit NRF52 Directory(〜/.arduino15/packages/packages/adafruit/adafruit/hardware/nrff52/1.3.0)中。
假設Adafruit NRF52版本為1.3.0。這些文件必須複製到目錄中:
~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/platform.txt~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/boards.txt~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/cores/nRF5/Udp.h~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/cores/nRF5/Print.h~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/cores/nRF5/Print.cpp~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/variants/NINA_B302_ublox/variant.h~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/variants/NINA_B302_ublox/variant.cpp~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/variants/NINA_B112_ublox/variant.h~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/variants/NINA_B112_ublox/variant.cpp~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/cores/nRF5/Udp.h每當安裝新版本時,請記住將這些文件複製到新版本目錄中。例如,新版本是x.yy.z,這些文件必須複製到目錄中:
~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/platform.txt~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/boards.txt~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/cores/nRF5/Udp.h~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/cores/nRF5/Print.h~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/cores/nRF5/Print.cpp~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/variants/NINA_B302_ublox/variant.h~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/variants/NINA_B302_ublox/variant.cpp~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/variants/NINA_B112_ublox/variant.h~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/variants/NINA_B112_ublox/variant.cpp~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/cores/nRF5/Udp.h為了能夠在Teensy板上編譯和運行,您必須將TeenSy目錄中的文件複製到Teensy Hardware Directory(./arduino-1.8.19 /hardware/hardware/teensy/teensy/avr/boards.txt)中。
假設Arduino版本為1.8.19。這些文件必須複製到目錄中:
./arduino-1.8.19/hardware/teensy/avr/boards.txt./arduino-1.8.19/hardware/teensy/avr/cores/teensy/Stream.h./arduino-1.8.19/hardware/teensy/avr/cores/teensy3/Stream.h./arduino-1.8.19/hardware/teensy/avr/cores/teensy4/Stream.h每當安裝新版本時,請記住將此文件複製到新版本目錄中。例如,新版本是X.yy.zz這些文件必須複製到目錄中:
./arduino-x.yy.zz/hardware/teensy/avr/boards.txt./arduino-x.yy.zz/hardware/teensy/avr/cores/teensy/Stream.h./arduino-x.yy.zz/hardware/teensy/avr/cores/teensy3/Stream.h./arduino-x.yy.zz/hardware/teensy/avr/cores/teensy4/Stream.h為了能夠在SAM欠董事會上進行編譯並運行,您必須將整個SAM Due Directory複製到Arduino Sam Directory(〜/.Arduino15/packages/packages/arduino/hardware/hardware/sam/1.6.12)中。
假設Arduino Sam Core版本為1.6.12。該文件必須複製到目錄中:
~/.arduino15/packages/arduino/hardware/sam/1.6.12/platform.txt每當安裝新版本時,請記住將此文件複製到新版本目錄中。例如,新版本是X.yy.zz,必須將此文件複製到目錄中:
~/.arduino15/packages/arduino/hardware/sam/x.yy.zz/platform.txtTo be able to compile, run and automatically detect and display BOARD_NAME on Arduino SAMD (Nano-33-IoT, etc) boards , you have to copy the whole Arduino SAMD Packages_Patches directory into Arduino SAMD directory (~/.arduino15/packages/arduino/hardware/samd/1.8.13).
假設Arduino SAMD版本為1.8.13。現在,只能將一個文件複製到目錄中:
~/.arduino15/packages/arduino/hardware/samd/1.8.13/platform.txt每當安裝新版本時,請記住將此文件複製到新版本目錄中。例如,新版本是x.yy.zz
該文件必須複製到目錄中:
~/.arduino15/packages/arduino/hardware/samd/x.yy.zz/platform.txt假設Arduino SAMD版本為1.8.9。這些文件必須複製到目錄中:
~/.arduino15/packages/arduino/hardware/samd/1.8.9/platform.txt~/.arduino15/packages/arduino/hardware/samd/1.8.9/cores/arduino/Arduino.h每當安裝新版本時,請記住將這些文件複製到新版本目錄中。例如,新版本是x.yy.z
這些文件必須複製到目錄中:
~/.arduino15/packages/arduino/hardware/samd/x.yy.z/platform.txt~/.arduino15/packages/arduino/hardware/samd/x.yy.z/cores/arduino/Arduino.h這是必須修復臭名昭著的Arduino SAMD編譯器錯誤的必要條件。請參閱提高與STL(最小值和最大宏)的Arduino兼容性
...arm-none-eabiincludec++7.2.1bitsstl_algobase.h:243:56: error: macro "min" passed 3 arguments, but takes just 2
min(const _Tp& __a, const _Tp& __b, _Compare __comp)
每當使用新的Arduino SAMD版本解決上述編譯器錯誤問題時,您就無需複制Arduino.h文件。
為了能夠在Adafruit SAMD(ITSY-BITSY M4等)板上進行編譯,運行和自動檢測和顯示board_name ,您必須將整個Adafruit Samd packages_patches目錄複製到Adafruit SAMD Directory(〜/.arduino15/packages/packages/adafruit/hardware/hardware/samd/1.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.7.11)。
假設Adafruit SAMD Core版本為1.7.11。這些文件必須複製到目錄中:
~/.arduino15/packages/adafruit/hardware/samd/1.7.11/platform.txt~/.arduino15/packages/adafruit/hardware/samd/1.7.11/cores/arduino/Print.h~/.arduino15/packages/adafruit/hardware/samd/1.7.11/cores/arduino/Print.cpp每當安裝新版本時,請記住將此文件複製到新版本目錄中。例如,新版本是X.yy.zz這些文件必須複製到目錄中:
~/.arduino15/packages/adafruit/hardware/samd/x.yy.zz/platform.txt~/.arduino15/packages/adafruit/hardware/samd/x.yy.zz/cores/arduino/Print.h~/.arduino15/packages/adafruit/hardware/samd/x.yy.zz/cores/arduino/Print.cpp要能夠在Seeeduino Samd(Xiao M0,Wio Terminal等)上進行編譯,運行和自動檢測和顯示board_name ,您必須將整個Seeeduino Samd packages_patches目錄複製到Seeeduino samd packages_patches目錄中seeeduino samd Directory(〜/.Arduino15/packeed/packeDuino15/packeeduino/seeeduino/hardware/hardware/samd/samd/samd/samd/samd/samd/1.8.8.8.8.8.8.8.8.8.3)
假設Seeeduino SAMD Core版本為1.8.3。這些文件必須複製到目錄中:
~/.arduino15/packages/Seeeduino/hardware/samd/1.8.3/platform.txt~/.arduino15/packages/Seeeduino/hardware/samd/1.8.3/cores/arduino/Arduino.h~/.arduino15/packages/Seeeduino/hardware/samd/1.8.3/cores/arduino/Print.h~/.arduino15/packages/Seeeduino/hardware/samd/1.8.3/cores/arduino/Print.cpp每當安裝新版本時,請記住將此文件複製到新版本目錄中。例如,新版本是X.yy.zz這些文件必須複製到目錄中:
~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/platform.txt~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/cores/arduino/Arduino.h~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/cores/arduino/Print.h~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/cores/arduino/Print.cpp在某些STM32板上使用LAN8720
您必須將文件STM32F4XX_HAL_CONF_DEFAULT.H和STM32F7XX_HAL_HAL_CONF_DEFAULT.H複製到STM32 STM32 Directory(〜/.arduino15/packages/stm32/stm32/hardware/hardware/stm32/2.32/2.0/系統)中,以覆蓋舊文件。
假設STM32 STM32核心版本為2.3.0。這些文件必須複製到目錄中:
~/.arduino15/packages/STM32/hardware/stm32/2.3.0/system/STM32F4xx/stm32f4xx_hal_conf_default.h for stm32f4。~/.arduino15/packages/STM32/hardware/stm32/2.3.0/system/STM32F7xx/stm32f7xx_hal_conf_default.h用於nucleo-144 STM32F7。每當安裝新版本時,請記住將此文件複製到新版本目錄中。例如,新版本是x.yy.zz,這些文件必須複製到相應的目錄中:
~/.arduino15/packages/STM32/hardware/stm32/x.yy.zz/system/STM32F4xx/stm32f4xx_hal_conf_default.hTo use Serial1 on some STM32 boards without Serial1 definition (Nucleo-144 NUCLEO_F767ZI, Nucleo-64 NUCLEO_L053R8, etc.) boards , you have to copy the files STM32 variant.h into STM32 stm32 directory (~/.arduino15/packages/STM32/hardware/stm32/2.3.0).您必須修改與董事會相對應的文件,這只是一個插圖。
假設STM32 STM32核心版本為2.3.0。這些文件必須複製到目錄中:
~/.arduino15/packages/STM32/hardware/stm32/2.3.0/variants/STM32F7xx/F765Z(GI)T_F767Z(GI)T_F777ZIT/NUCLEO_F767ZI/variant.h for Nucleo-144 NUCLEO_F767ZI.~/.arduino15/packages/STM32/hardware/stm32/2.3.0/variants/STM32L0xx/L052R(6-8)T_L053R(6-8)T_L063R8T/NUCLEO_L053R8/variant.h for Nucleeo-64 nucleo-64444453。每當安裝新版本時,請記住將此文件複製到新版本目錄中。例如,新版本是x.yy.zz,這些文件必須複製到相應的目錄中:
~/.arduino15/packages/STM32/hardware/stm32/x.yy.zz/variants/STM32F7xx/F765Z(GI)T_F767Z(GI)T_F777ZIT/NUCLEO_F767ZI/variant.h~/.arduino15/packages/STM32/hardware/stm32/x.yy.zz/variants/STM32L0xx/L052R(6-8)T_L053R(6-8)T_L063R8T/NUCLEO_L053R8/variant.h要能夠在基於RP2040的董事會(raspberry_pi_pico,adafruit_feather_rp2040,generic_rp2040等)上自動檢測和顯示board_name ,您必須複製文件rp2040 Platform.txt (〜/.arduino15/packages/rp2040/hardware/rp2040/1.4.0)。
假設RP2040核心版本為1.4.0。該文件必須複製到目錄中:
~/.arduino15/packages/rp2040/hardware/rp2040/1.4.0/platform.txt每當安裝新版本時,請記住將此文件複製到新版本目錄中。例如,新版本是X.yy.zz,必須將此文件複製到目錄中:
~/.arduino15/packages/rp2040/hardware/rp2040/x.yy.zz/platform.txt借助V1.5.0之後的Core,由於PR add -Dboard_name =“ {build.board}”#136,因此不再需要此步驟。
某些庫,例如Adafruit DHT-Sensor-library,需要微秒stoclockcycles()的定義。要能夠在基於RP2040的板上編譯和運行,您必須將RP2040 Arduino.H中的文件複製到RP2040目錄中(〜/.arduino15/packages/packages/rp2040/hardware/rpware/rp2040/1.4.0)。
假設RP2040核心版本為1.4.0。必須複製此文件以替換:
~/.arduino15/packages/rp2040/hardware/rp2040/1.4.0/cores/rp2040/Arduino.h每當安裝新版本時,請記住將此文件複製到新版本目錄中。例如,新版本是x.yy.zz必須複製此文件以替換:
~/.arduino15/packages/rp2040/hardware/rp2040/x.yy.zz/cores/rp2040/Arduino.h在V1.5.0之後的Core中,由於兼容性#142的PR添加DEFS,因此不再需要此步驟。
要能夠在Linux(Ubuntu等)中使用Arduino IDE上傳固件到portenta_h7 ,您必須將文件portenta_post_install.sh複製到mbed_portenta目錄(〜/.arduino15/packages/packages/packages/arduino/arduino/ardware/ardware/ardware/mbed_portenta/3.4.4.1/portenta_4.1/portenta__porst_post_post)。
然後使用sudo運行以下命令
$ cd ~/.arduino15/packages/arduino/hardware/mbed_portenta/3.4.1
$ chmod 755 portenta_post_install.sh
$ sudo ./portenta_post_install.sh
這將創建file /etc/udev/rules.d/49-portenta_h7.rules如下:
# Portenta H7 bootloader mode UDEV rules
SUBSYSTEMS=="usb", ATTRS{idVendor}=="2341", ATTRS{idProduct}=="035b", GROUP="plugdev", MODE="0666"
假設Arduinocore-Mbed Core版本為3.4.1。現在,只能將一個文件複製到目錄中:
~/.arduino15/packages/arduino/hardware/mbed_portenta/3.4.1/portenta_post_install.sh每當安裝新版本時,請記住將此文件複製到新版本目錄中。例如,新版本是x.yy.zz
該文件必須複製到目錄中:
~/.arduino15/packages/arduino/hardware/mbed_portenta/x.yy.zz/portenta_post_install.sh為避免與ProgMem有關的編譯錯誤,您必須將文件Realtek amebad core pgmspace.h複製到Realtek amebad目錄(〜/.arduino15/packages/packages/realtek/hardware/amebad/3.1.4/cores/cores/cores/cores/cores/cores/cores/cores/cores/cores/cores/cores/cores/cores/cores/cores/cores/cores/cores/cores/cores/core/core/cores/arm ambd/ambd/avr/avr/avr/pgmspace.h)。
假設Realtek Amebad Core版本為3.1.4。該文件必須複製到目錄中:
~/.arduino15/packages/realtek/hardware/AmebaD/3.1.4/cores/ambd/avr/pgmspace.h每當安裝新版本時,請記住將此文件複製到新版本目錄中。例如,新版本是X.yy.zz,必須將此文件複製到目錄中:
~/.arduino15/packages/realtek/hardware/AmebaD/x.yy.zz/cores/ambd/avr/pgmspace.h為了避免與SAMD21/SAMD51有關的編譯錯誤,您必須將文件複製到arduinocore-fab-sam core pgmspace.h中添加到ArduinoCore-fab-sam samd Directory(〜/.arduino15/packegages/packegages/fab_sam_sam_ardwarino/hardware/hardware/hardware/hardware/samd/samd/samd/boards.txt)。
假設ArduinoCore-fab-sam SAMD Core版本為1.9.0。該文件必須複製到目錄中:
~/.arduino15/packages/Fab_SAM_Arduino/hardware/samd/1.9.0/boards.txt每當安裝新版本時,請記住將此文件複製到新版本目錄中。例如,新版本是X.yy.zz,必須將此文件複製到目錄中:
~/.arduino15/packages/Fab_SAM_Arduino/hardware/samd/x.yy.zz/boards.txt要能夠在Seeeduino RP2040(Xiao RP2040,Wio RP2040 Mini)板上進行編譯,運行和自動檢測和顯示board_name ,您必須將整個Seeeduino RP2040 Packages_patches_patches_patches目錄複製到Seeeduino seeeduino Samd Directory(〜/seeduino samd directory(〜/see/packages/packaiges/seeduino)中,
假設Seeeduino RP2040核心版本為2.7.2。這些文件必須複製到目錄中:
~/.arduino15/packages/Seeeduino/hardware/rp2040/2.7.2/boards.txt~/.arduino15/packages/Seeeduino/hardware/rp2040/2.7.2/variants/Seeed_XIAO_RP2040/pins_arduino.h每當安裝新版本時,請記住將此文件複製到新版本目錄中。例如,新版本是X.yy.zz這些文件必須複製到目錄中:
~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/boards.txt~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/variants/Seeed_XIAO_RP2040/pins_arduino.h要能夠在Xiao NRF52840板上編譯和運行,您必須將整個NRF52 1.0.0目錄複製到Seeeduino NRF52 Directory(〜/.arduino15/packages/seeeduino/seeeduino/hardware/hardware/hardware/nrrf52/1.0.0)。
假設Seeeduino NRF52版本為1.0.0。這些文件必須複製到目錄中:
~/.arduino15/packages/Seeeduino/hardware/nrf52/1.0.0/platform.txt~/.arduino15/packages/Seeeduino/hardware/nrf52/1.0.0/cores/nRF5/Print.h~/.arduino15/packages/Seeeduino/hardware/nrf52/1.0.0/cores/nRF5/Print.cpp~/.arduino15/packages/Seeeduino/hardware/nrf52/1.0.0/cores/nRF5/Udp.h每當安裝新版本時,請記住將這些文件複製到新版本目錄中。例如,新版本是x.yy.z,這些文件必須複製到目錄中:
~/.arduino15/packages/Seeeduino/hardware/nrf52/x.yy.z/platform.txt~/.arduino15/packages/Seeeduino/hardware/nrf52/x.yy.z/cores/nRF5/Print.h~/.arduino15/packages/Seeeduino/hardware/nrf52/x.yy.z/cores/nRF5/Print.cpp~/.arduino15/packages/Seeeduino/hardware/nrf52/x.yy.z/cores/nRF5/Udp.hESP8266/ESP32-AT shield將在電源電源時啟動WiFi配置門戶,並將配置數據保存在主機的非揮發性內存中。此後,只有在主機板上按下按鈕時,配置門戶才會再次啟動。Save 。ESP8266/ESP32-AT shield將嘗試連接。如果成功,則在配置門戶中將顯示動態DHCP或配置的靜態IP地址。ESP8266/ESP32-AT shield WIFI配置門戶網絡和Web服務器將關閉以返回控件到草圖代碼。 // Select depending on board
# define EspSerial Serial1
// Must be before #include <ESP_AT_WiFiManager.h>
// To store Credentials / WiFi Data
# define EEPROM_START 0
# include < ESP_AT_WiFiManager.h > // https://github.com/khoih-prog/ESP_AT_WiFiManager
// Your Board <-> ESP8266 baud rate:
# define ESP8266_BAUD 115200
String ssid = " ESP_AT_ " + String( 0x1ABCDEF , HEX);
const char * password = " ESP_AT_PW " ;
IPAddress staticAP_IP = IPAddress( 192 , 168 , 100 , 1 );
// SSID and PW for your Router
String Router_SSID;
String Router_Pass;
// Onboard LED I/O pin on board
const int LOCAL_PIN_LED = 13 ; // Pin 13, Controls the onboard LED.
# define LED_ON HIGH
# define LED_OFF LOWESP_AT_WiFiManager ESP_AT_wiFiManager;ESP_AT_wiFiManager.setAPChannel(newChannel);ESP_AT_WiFiManager-> setAPChannel ( 0 );ESP_AT_wiFiManager.setSTAStaticIPConfig(IPAddress(xxx,xxx,xxx,xxx));192.168.4.1 ),請致電ESP_AT_wiFiManager.setAPStaticIPConfig(IPAddress(xxx,xxx,xxx,xxx));ESP_AT_XXXXXX ,請致電ESP_AT_wiFiManager.startConfigPortal()ESP_AT_wiFiManager.startConfigPortal(( const char *) ssid.c_str(), password);在AP模式下,使用其SSID (ESP_AT_XXXXX) / Password (“ ESP_AT_PW”)連接到它,然後打開一個瀏覽器到Portal AP IP,默認為192.168.4.1 ,配置WiFi然後保存。憑據 / WiFi連接信息將保存在非易失性內存中。然後將自動連接。
一旦將憑據 / WiFi網絡信息保存在主機非易失性內存中,它將嘗試每次啟動時自動連接到wifi,而無需在草圖中需要任何函數調用。
在Configuration Portal Mode下,它啟動了一個稱為ESP_AT_XXXXXX的AP。使用configurable password連接到它,您可以在代碼中定義。例如, ESP_AT_PW (請參閱示例):
// SSID and PW for Config Portal
String ssid = " ESP_AT_ " + String( 0x1ABCDEF , HEX);
const char * password = " ESP_AT_PW " ;連接後,請訪問http://192.168.4.1或新配置的AP IP,您將看到此Main :

選擇以輸入將顯示董事會信息的Information頁面

選擇Configuration以輸入此頁面,您可以在其中選擇AP並指定其WiFi憑據

輸入您的憑據,然後單擊Save 。 WiFi憑據將保存,板連接到所選的WiFi AP。
如果您已經連接到列出的WiFi AP,並且不想更改任何內容,則只需從Main中選擇Exit即可重新啟動板並連接到先前存儲的AP。 WiFi憑據仍然完整。
您可以密碼保護配置AP。只需將SSID作為第一個參數和密碼作為第二個參數,如下startConfigPortal :
ESP_AT_wiFiManager.startConfigPortal(SSID , password);使用具有8個以上字符的密碼。
指南是WiFi密碼必須由8至63個ASCII編碼的字符組成,範圍為32至126(十進制)
您可以設置一個超時(以秒為單位),以便ESP8266/ESP32-AT shield不會掛在等待永遠配置。
ESP_AT_WiFiManager.setConfigPortalTimeout( 60 );這將等待1分鐘(60秒)。
當時間過去時,除非您要訪問配置門戶,否則StartConfigportal功能將返回並繼續草圖。在這種情況下, startConfigPortal功能將保留,直到您保存配置數據或退出配置門戶。
許多應用程序需要配置參數,例如MQTT host and port ,Blynk或Emoncms令牌等。雖然可以使用ESP_AT_WiFiManager來收集其他參數,但一旦使用ESP_AT_AT_WIFIMANAGER已使用ESP_AT_AT_WIFIMANAGER讀取這些參數,但已使用ESP_AT_WiFiManager來連接到Internet。這使ESP_AT_WiFiManager易於編碼和使用,可以在常規的Web服務器上編輯參數,並且可以在部署後進行遠程更改。
您可以為AP(訪問點,配置模式)和STA(站模式,客戶端模式,普通項目狀態)設置自定義IP
如果您需要/想要這樣的功能,這將把您的圈養門戶設置為特定的IP。在startConfigPortal()之前添加以下片段
// Default AP IP is 192.168.4.1. Uncomment to use different AP IP
ESP_AT_wiFiManager.setAPStaticIPConfig(IPAddress( 192 , 168 , 100 , 1 ));這將使用指定的IP配置,而不是在站模式下使用DHCP。
// Set static STA IP
ESP_AT_wiFiManager.setSTAStaticIPConfig(IPAddress( 192 , 168 , 2 , 114 ));您可以通過多種方式將自定義HTML,CSS或JavaScript注入配置門戶。
選項是:
您可以將其用於配置門戶頭的任何HTML位。如果添加<style>元素,請記住它會覆蓋隨附的CSS,而不是替換。
ESP_AT_wiFiManager.setCustomHeadElement( " <style>html{filter: invert(100%); -webkit-filter: invert(100%);}</style> " );ESP_AT_WMParameter custom_text ( " <p>This is just a text paragraph</p> " );
ESP_AT_wiFiManager.addParameter(&custom_text);只需將要添加為最後一個參數的位添加到自定義參數構造函數中即可。
ESP_AT_WMParameter custom_mqtt_server ( " server " , " mqtt server " , " iot.eclipse " , 40 , " readonly " );您可以根據信號質量過濾網絡並顯示/隱藏重複網絡。
ESP_AT_wiFiManager.setMinimumSignalQuality( 10 );不會顯示低於10%的信號質量的網絡。如果省略參數,則默認為8%;
ESP_AT_wiFiManager.setRemoveDuplicateAPs( false );ESP_AT_WIFIMANAGER/示例/configonswitch/configonswitch.ino
4D54139中的第25至241行
ESP_AT_WIFIMANAGER/示例/configonswitch/defines.h
4D54139中的第15至395行
This is the terminal output when running ConfigOnSwitch example on Adafruit Itsy-BItsy nRF52840 with ESP8266-AT shield :
Start ConfigOnSwitch on NRF52840_ITSYBITSY
ESP_AT_WiFiManager v1.4.0
Opening Config Portal. *WM: LoadCfgFile
*WM: OK
*WM: ======= Start Stored Config Data =======
*WM: Header = SHD_ESP8266, SSID = HueNet1, PW = ****
*WM: Host Name =
*WM: CCSum=0x8df,RCSum=0x0
*WM: InitCfgFile,sz=108
*WM: SaveCfgFile
*WM: WCSum=0x7f4
*WM: OK
*WM: SaveBkUpCfgFile
*WM: OK
*WM: LoadCfgFile
*WM: OK
*WM: ======= Start Stored Config Data =======
*WM: Header = ESP_AT, SSID = blank, PW = blank
*WM: Host Name = blank
*WM: CCSum=0x7f4,RCSum=0x7f4
No stored Credentials. No timeout
Start Config Portal, SSID = ESP_AT_ABCDEF, Pass = ESP_AT_PW: Custom AP IP: 192.168.100.1
*WM: AP IP: 192.168.100.1
*WM: HTTP server on channel 1
*WM: Handle root
*WM: LoadCfgFile
*WM: OK
*WM: Handle WiFi
*WM: Scan Network
*WM: DUP AP:
*WM: DUP AP:
*WM: HueNet1 / -28
*WM: bacau / -74
*WM: guest_24 / -77
*WM: Sent config page
*WM: WiFi save
*WM: SaveCfgFile
*WM: WCSum=0x9c7
*WM: OK
*WM: SaveBkUpCfgFile
*WM: OK
*WM: Sent wifisave page
*WM: Connect to new AP
*WM: LoadCfgFile
*WM: OK
*WM: ======= Start Stored Config Data =======
*WM: Header = ESP_AT, SSID = HueNet1, PW = ****
*WM: Host Name = blank
*WM: CCSum=0x9c7,RCSum=0x9c7
*WM: Header = ESP_AT, SSID = HueNet1, PW = ****
*WM: Host Name = blank
*WM: Connect wifi with new params
*WM: Data cleared
*WM: Static IP : 192.168.2.114
*WM: Connect result: WL_CONNECTED
WiFi connected...yeey
After waiting 0 secs in setup(), connect result is connected. Local IP: 192.168.2.114
HH
Save Start ConfigOnSwitch on NRF52840_ITSYBITSY
ESP_AT_WiFiManager v1.4.0
Opening Config Portal. *WM: LoadCfgFile
*WM: OK
*WM: ======= Start Stored Config Data =======
*WM: Header = ESP_AT, SSID = HueNet1, PW = ****
*WM: Host Name = blank
*WM: CCSum=0x9c7,RCSum=0x9c7
*WM: Header = ESP_AT, SSID = HueNet1, PW = ****
*WM: Host Name = blank
Got stored Credentials. Timeout 60s
Start Config Portal, SSID = ESP_AT_ABCDEF, Pass = ESP_AT_PW
*WM: Configure AP: ESP_AT_ABCDEF
*WM: AP PW: ESP_AT_PW
*WM: Custom AP IP: 192.168.100.1
*WM: AP IP: 192.168.100.1
*WM: HTTP server on channel 1
*WM: Static IP : 192.168.2.114
*WM: Timeout, connect result: WL_CONNECTED
WiFi connected...yeey
After waiting 0 secs in setup(), connect result is connected. Local IP: 192.168.2.114
HHHHHHHHHH HHHHHHHHHH HHHHHHHHHH HHHHHHHHHH HHHHHHHHHH HHHHHHHHHH HHHHHHHHHH HHHHHHHHHH
HHHHHHHHHH HHHHHHHHHH HHHHHHHHHH HHHHHHHHHH HHHHHHHHHH HHHHHHHHHH HHHHHHHHHH HHHHHHHHHH
This is the terminal output when running ConfigOnStartup example using SAM-DUE with ESP32-AT shield . The ESP32-AT firmware is AT version:2.1.0.0-dev / SDK version:v4.0.1-193-ge7ac221b4:
Start ConfigOnStartup on SAM DUE
ESP_AT_WiFiManager v1.4.0
[ESP_AT] AT+RST
[ESP_AT] ATE0
[ESP_AT] Use ESP32-AT Command
[ESP_AT] AT+CWMODE=1
[ESP_AT] AT+CIPMUX=1
[ESP_AT] AT+CIPDINFO=1
[ESP_AT] AT+CWAUTOCONN=0
[ESP_AT] AT+CWDHCP=1,1
[ESP_AT] AT+GMR
[ESP_AT] Firmware Init OK - v4.0.
[ESP_AT] AT+CIPSTATUS
Opening Config Portal. *WM: CCSum=0x7f4,RCSum=0x0
*WM: CCSum=0x7f4,RCSum=0x0
No stored Credentials. No timeout
Start Config Portal, SSID = ESP_AT_ABCDEF, Pass = ESP_AT_PW
*WM: Configure AP: ESP_AT_ABCDEF
*WM: AP PW: ESP_AT_PW
*WM: Custom AP IP: 192.168.100.1
[ESP_AT] AT+CWMODE=2
[ESP_AT] AT+CWDHCP=0,3
[ESP_AT] AT+CIPAP= 192.168.100.1
[ESP_AT] IP address set 192.168.100.1
[ESP_AT] AT+CWMODE= 3
AT+CWSAP= ESP_AT_ABCDEF ESP_AT_PW
AT+CWSAP= 1 3
[ESP_AT] AT+CWDHCP=1,3
[ESP_AT] Access point started ESP_AT_ABCDEF
*WM: AP IP: [ESP_AT] AT+CIPAP?
192.168.100.1
AT+CIPSERVER= 1 80
*WM: HTTP server on channel 1
*WM: Handle WiFi
*WM: Scan Network
[ESP_AT] AT+CWLAP
*WM: HueNet / -33
*WM: HueNet1 / -40
*WM: HueNetTek / -43
*WM: Sent config page
*WM: WiFi save
*WM: SaveDueFlash, CSum=2503
*WM: Sent wifisave page
*WM: Connect to new AP
*WM: CCSum=0x9c7,RCSum=0x9c7
*WM: Header = ESP_AT, SSID = HueNet1, PW = ****
*WM: Host Name = blank
*WM: Connect wifi with new params
*WM: Data cleared
[ESP_AT] AT+CWQAP
[ESP_AT] AT+CIPSTATUS
[ESP_AT] AT+RST
[ESP_AT] ATE0
[ESP_AT] Use ESP32-AT Command
[ESP_AT] AT+CWMODE=1
[ESP_AT] AT+CIPMUX=1
[ESP_AT] AT+CIPDINFO=1
[ESP_AT] AT+CWAUTOCONN=0
[ESP_AT] AT+CWDHCP=1,1
[ESP_AT] AT+CWDHCP=0,1
[ESP_AT] AT+CIPSTA= 192.168.2.114
[ESP_AT] IP address set 192.168.2.114
*WM: Static IP : 192.168.2.114
AT+CWJAP= HueNet1 ****
[ESP_AT] Connected to HueNet1
[ESP_AT] AT+CIPSTATUS
*WM: Connect result: WL_CONNECTED
[ESP_AT] AT+CIPSTATUS
WiFi connected...yeey
[ESP_AT] AT+CIPSTATUS
After waiting 0 secs in setup(), connect result is [ESP_AT] AT+CIPSTATUS
connected. Local IP: [ESP_AT] AT+CIFSR
192.168.2.114
[ESP_AT] AT+CIPSTATUS
H[ESP_AT] AT+CIPSTATUS
H
This is the terminal output when running ConfigOnStartup example using STM32 Nucleo-144 NUCLEO_F767ZI with ESP8266-AT shield .
Start ConfigOnStartup on NUCLEO_F767ZI
ESP_AT_WiFiManager v1.4.0
[ESP_AT] Use ES8266-AT Command
Opening Config Portal. *WM: EEPROMsz:1024
*WM: CCSum=0x65a0,RCSum=0xffffffff
*WM: EEPROMsz:1024
*WM: CCSum=0x7f4,RCSum=0x0
No stored Credentials. No timeout
Start Config Portal, SSID = ESP_AT_ABCDEF, Pass = ESP_AT_PW
*WM: Configure AP: ESP_AT_ABCDEF
*WM: AP PW: ESP_AT_PW
*WM: Custom AP IP: 192.168.100.1
*WM: AP IP: 192.168.100.1
*WM: HTTP server on channel 1
*WM: Handle root
*WM: EEPROMsz:1024
*WM: CCSum=0x7f4,RCSum=0x0
*WM: EEPROMsz:1024
*WM: CCSum=0x7f4,RCSum=0x0
*WM: Info
*WM: EEPROMsz:1024
*WM: CCSum=0x7f4,RCSum=0x0
*WM: EEPROMsz:1024
*WM: CCSum=0x7f4,RCSum=0x0
*WM: Sent info page
*WM: Handle root
*WM: EEPROMsz:1024
*WM: CCSum=0x7f4,RCSum=0x0
*WM: EEPROMsz:1024
*WM: CCSum=0x7f4,RCSum=0x0
*WM: Handle WiFi
*WM: Scan Network
*WM: HueNet / -22
*WM: HueNetTek / -36
*WM: HueNet1 / -46
*WM: Sent config page
*WM: WiFi save
*WM: SaveEEPROM,CSum=2503
*WM: Sent wifisave page
*WM: Connect to new AP
*WM: EEPROMsz:1024
*WM: CCSum=0x9c7,RCSum=0x9c7
*WM: Header = ESP_AT, SSID = HueNet1, PW = password
*WM: Host Name = blank
*WM: Connect wifi with new params
*WM: Data cleared
[ESP_AT] Use ES8266-AT Command
*WM: Static IP : 192.168.2.114
*WM: Connect result: WL_CONNECTED
WiFi connected...yeey
After waiting 0 secs in setup(), connect result is connected. Local IP: 192.168.2.114
HHHHHHHHH
This is the terminal output when running ConfigOnStartup example using Seeeduino SEEED_XIAO_M0 with ESP8266-AT shield .
Start ConfigOnStartup on SEEED_XIAO_M0
ESP_AT_WiFiManager v1.4.0
[ESP_AT] Use ES8266-AT Command
Opening Config Portal. *WM: CCSum=0x0,RCSum=0x0
*WM: CCSum=0x7f4,RCSum=0x0
No stored Credentials. No timeout
Start Config Portal, SSID = ESP_AT_ABCDEF, Pass = ESP_AT_PW
*WM: Configure AP: ESP_AT_ABCDEF
*WM: AP PW: ESP_AT_PW
*WM: Custom AP IP: 192.168.100.1
*WM: AP IP: 192.168.100.1
*WM: HTTP server on channel 1
*WM: Handle root
*WM: CCSum=0x7f4,RCSum=0x0
*WM: CCSum=0x7f4,RCSum=0x0
*WM: Info
*WM: CCSum=0x7f4,RCSum=0x0
*WM: CCSum=0x7f4,RCSum=0x0
*WM: Sent info page
*WM: Handle root
*WM: CCSum=0x7f4,RCSum=0x0
*WM: CCSum=0x7f4,RCSum=0x0
*WM: Handle WiFi
*WM: Scan Network
*WM: DUP AP:
*WM: HueNetTek / -25
*WM: HueNet1 / -32
*WM: HueNet2 / -42
*WM: Sent config page
*WM: WiFi save
*WM: SaveFlash,CSum=2504
*WM: Sent wifisave page
*WM: Connect to new AP
*WM: CCSum=0x9c8,RCSum=0x9c8
*WM: Header = ESP_AT, SSID = HueNet2, PW = password
*WM: Host Name = blank
*WM: Connect wifi with new params
*WM: Data cleared
[ESP_AT] Use ES8266-AT Command
*WM: Static IP : 192.168.2.114
*WM: Connect result: WL_CONNECTED
WiFi connected...yeey
After waiting 0 secs in setup(), connect result is connected. Local IP: 192.168.2.114
HHHHHHHHH
This is the terminal output when running ConfigOnStartup example using STM32 Nucleo-144 NUCLEO_F767ZI with ESP8266-AT shield .
Start ConfigOnStartup with ESP8266-AT WiFi module on NUCLEO_F767ZI
ESP_AT_WiFiManager v1.4.0
[ESP_AT] Use ES8266-AT Command
Opening Config Portal.
*WM: EEPROMsz:1024
*WM: CCSum=0x9c7,RCSum=0x9c7
*WM: Header = ESP_AT, SSID = HueNet1, PW = password
*WM: Host Name = blank
*WM: Connect wifi with new params
*WM: Data cleared
[ESP_AT] Use ES8266-AT Command
*WM: Static IP : 192.168.2.114
*WM: Connect result: WL_CONNECTED
Got stored Credentials. Try to connect first
After waiting 0 secs in setup(), connect result is connected. Local IP: 192.168.2.114
H
Start ConfigOnStartup with ESP8266-AT WiFi module on NUCLEO_F767ZI
ESP_AT_WiFiManager v1.4.0
[ESP_AT] Use ES8266-AT Command
Opening Config Portal.
*WM: EEPROMsz:1024
*WM: CCSum=0x9c7,RCSum=0x9c7
*WM: Header = ESP_AT, SSID = HueNet1, PW = password
*WM: Host Name = blank
*WM: Connect wifi with new params
*WM: Data cleared
[ESP_AT] Use ES8266-AT Command
*WM: Static IP : 192.168.2.114
*WM: Connect result: WL_DISCONNECTED
Got stored Credentials but can't connect. Timeout 60s
Start Config Portal, SSID = ESP_AT_ABCDEF, Pass = ESP_AT_PW
*WM: Configure AP: ESP_AT_ABCDEF
*WM: AP PW: ESP_AT_PW
*WM: Custom AP IP: 192.168.100.1
*WM: AP IP: 192.168.100.1
*WM: HTTP server on channel 1
*WM: WiFi save
*WM: SaveEEPROM,CSum=2503
*WM: Sent wifisave page
*WM: Connect to new AP
*WM: Connect wifi with new params
*WM: Data cleared
[ESP_AT] Use ES8266-AT Command
*WM: Static IP : 192.168.2.114
*WM: Connect result: WL_CONNECTED
WiFi connected...yeey
After waiting 0 secs in setup(), connect result is connected. Local IP: 192.168.2.114
HHHHHH
This is the terminal output when running ConfigOnSwitch example using RASPBERRY_PI_PICO with ESP8266-AT shield .
Start ConfigOnSwitch with ESP8266-AT WiFi module on RASPBERRY_PI_PICO
ESP_AT_WiFiManager v1.4.0
[ESP_AT] Use ES8266-AT Command
Opening Config Portal.
*WM: LoadCfgFile
*WM: failed
*WM: LoadBkUpCfgFile
*WM: failed
*WM: ======= Start Stored Config Data =======
*WM: Header = , SSID = , PW =
*WM: Host Name =
*WM: CCSum=0x1df0,RCSum=0xffffffff
*WM: InitCfgFile,sz=140
*WM: SaveCfgFile
*WM: WCSum=0x7f4
*WM: OK
*WM: SaveBkUpCfgFile
*WM: OK
*WM: LoadCfgFile
*WM: OK
*WM: ======= Start Stored Config Data =======
*WM: Header = ESP_AT, SSID = blank, PW = blank
*WM: Host Name = blank
*WM: CCSum=0x7f4,RCSum=0x7f4
No stored or not valid Credentials. No timeout
Start Config Portal, SSID = ESP_AT_ABCDEF, Pass = ESP_AT_PW
*WM: Configure AP: ESP_AT_ABCDEF
*WM: AP PW: ESP_AT_PW
*WM: Custom AP IP: 192.168.100.1
*WM: AP IP: 192.168.100.1
*WM: HTTP server on channel 1
*WM: Handle root
*WM: LoadCfgFile
*WM: OK
*WM: ======= Start Stored Config Data =======
*WM: Header = ESP_AT, SSID = blank, PW = blank
*WM: Host Name = blank
*WM: CCSum=0x7f4,RCSum=0x7f4
*WM: Handle WiFi
*WM: Scan Network
*WM: DUP AP:
*WM: HueNet1 / -32
*WM: HueNetTek / -37
*WM: dlink-4F96 / -79
*WM: Sent config page
*WM: WiFi save
*WM: SaveCfgFile
*WM: WCSum=0x9c7
*WM: OK
*WM: SaveBkUpCfgFile
*WM: OK
*WM: Sent wifisave page
*WM: Connect to new AP
*WM: LoadCfgFile
*WM: OK
*WM: ======= Start Stored Config Data =======
*WM: Header = ESP_AT, SSID = HueNet1, PW = password
*WM: Host Name = blank
*WM: CCSum=0x9c7,RCSum=0x9c7
*WM: Header = ESP_AT, SSID = HueNet1, PW = password
*WM: Host Name = blank
*WM: Connect wifi with new params
*WM: Data cleared
[ESP_AT] Use ES8266-AT Command
*WM: Static IP : 192.168.2.114
*WM: Connect result: WL_CONNECTED
WiFi connected...yeey
After waiting 0 secs in setup(), connect result is connected. Local IP: 192.168.2.114
HHH
Start ConfigOnSwitch with ESP8266-AT WiFi module on RASPBERRY_PI_PICO
ESP_AT_WiFiManager v1.4.0
[ESP_AT] Use ES8266-AT Command
Opening Config Portal.
*WM: LoadCfgFile
*WM: OK
*WM: ======= Start Stored Config Data =======
*WM: Header = ESP_AT, SSID = HueNet1, PW = password
*WM: Host Name = blank
*WM: CCSum=0x9c7,RCSum=0x9c7
*WM: Header = ESP_AT, SSID = HueNet1, PW = password
*WM: Host Name = blank
*WM: Connect wifi with new params
*WM: Data cleared
[ESP_AT] Use ES8266-AT Command
*WM: Static IP : 192.168.2.114
*WM: Connect result: WL_CONNECTED
Got stored Credentials. Try to connect first
After waiting 0 secs in setup(), connect result is connected. Local IP: 192.168.2.114
H
Config Portal requested.
Opening Config Portal.
*WM: LoadCfgFile
*WM: OK
*WM: ======= Start Stored Config Data =======
*WM: Header = ESP_AT, SSID = HueNet1, PW = password
*WM: Host Name = blank
*WM: CCSum=0x9c7,RCSum=0x9c7
*WM: Header = ESP_AT, SSID = HueNet1, PW = password
*WM: Host Name = blank
Forced CP, No stored or not valid Credentials. No timeout
Start Config Portal, SSID = ESP_AT_ABCDEF, Pass = ESP_AT_PW
*WM: Configure AP: ESP_AT_ABCDEF
*WM: AP PW: ESP_AT_PW
*WM: Custom AP IP: 192.168.100.1
*WM: AP IP: 192.168.100.1
*WM: HTTP server on channel 1
*WM: Handle root
*WM: Info
*WM: Sent info page
*WM: Handle root
*WM: Handle WiFi
*WM: Scan Network
*WM: DUP AP: Waterhome
*WM: HueNet1 / -30
*WM: HueNetTek / -34
*WM: HueNet2 / -55
*WM: Sent config page
*WM: WiFi save
*WM: SaveCfgFile
*WM: WCSum=0x9c7
*WM: OK
*WM: SaveBkUpCfgFile
*WM: OK
*WM: Sent wifisave page
*WM: Connect to new AP
*WM: Connect wifi with new params
*WM: Data cleared
[ESP_AT] Use ES8266-AT Command
*WM: Static IP : 192.168.2.114
*WM: Connect result: WL_CONNECTED
WiFi connected...yeey
H
Start ConfigOnSwitch with ESP8266-AT WiFi module on RASPBERRY_PI_PICO
ESP_AT_WiFiManager v1.4.0
[ESP_AT] Use ES8266-AT Command
Opening Config Portal.
*WM: LoadCfgFile
*WM: OK
*WM: ======= Start Stored Config Data =======
*WM: Header = ESP_AT, SSID = HueNet1, PW = password
*WM: Host Name = blank
*WM: CCSum=0x9c7,RCSum=0x9c7
*WM: Header = ESP_AT, SSID = HueNet1, PW = password
*WM: Host Name = blank
*WM: Connect wifi with new params
*WM: Data cleared
[ESP_AT] Use ES8266-AT Command
*WM: Static IP : 192.168.2.114
*WM: Connect result: WL_CONNECTED
Got stored Credentials. Try to connect first
After waiting 0 secs in setup(), connect result is connected. Local IP: 192.168.2.114
H
This is the terminal output when running ConfigOnStartup example using MBED RASPBERRY_PI_PICO with ESP8266-AT shield .
Start ConfigOnStartup with ESP8266-AT WiFi module on MBED RASPBERRY_PI_PICO
ESP_AT_WiFiManager v1.4.0
[ESP_AT] Use ES8266-AT Command
Opening Config Portal.
*WM: LittleFS size (KB) = 64
*WM: LittleFS Mount OK
*WM: LoadCfgFile
*WM: failed
*WM: LoadBkUpCfgFile
*WM: failed
*WM: CCSum=0x1d51,RCSum=0xd
*WM: InitCfgFile,sz=140
*WM: SaveCfgFile
*WM: WCSum=0x899
*WM: OK
*WM: SaveBkUpCfgFile
*WM: OK
*WM: LittleFS size (KB) = 64
*WM: LittleFS Mount OK
*WM: LoadCfgFile
*WM: OK
*WM: CCSum=0x899,RCSum=0x899
No stored or not valid Credentials. No timeout
Start Config Portal, SSID = ESP_AT_ABCDEF, Pass = ESP_AT_PW
*WM: Configure AP: ESP_AT_ABCDEF
*WM: AP PW: ESP_AT_PW
*WM: Custom AP IP: 192.168.100.1
*WM: AP IP: 192.168.100.1
*WM: HTTP server on channel 1
*WM: Handle root
*WM: LittleFS size (KB) = 64
*WM: LittleFS Mount OK
*WM: LoadCfgFile
*WM: OK
*WM: CCSum=0x899,RCSum=0x899
*WM: LittleFS size (KB) = 64
*WM: LittleFS Mount OK
*WM: LoadCfgFile
*WM: OK
*WM: CCSum=0x899,RCSum=0x899
*WM: Handle WiFi
*WM: Scan Network
*WM: DUP AP:
*WM: DUP AP:
*WM: HueNetTek / -28
*WM: HueNet1 / -32
*WM: / -81
*WM: Sent config page
*WM: WiFi save
*WM: SaveCfgFile
*WM: WCSum=0xa6c
*WM: OK
*WM: SaveBkUpCfgFile
*WM: OK
*WM: Sent wifisave page
*WM: Connect to new AP
*WM: LittleFS size (KB) = 64
*WM: LittleFS Mount OK
*WM: LoadCfgFile
*WM: OK
*WM: CCSum=0xa6c,RCSum=0xa6c
*WM: ======= Start Stored Config Data =======
*WM: Header = ESP_AT, SSID = HueNet1, PW = password
*WM: Host Name = MBED-RP2040
*WM: Connect wifi with new params
*WM: Data cleared
[ESP_AT] Use ES8266-AT Command
*WM: Static IP : 192.168.2.114
*WM: Connect result: WL_CONNECTED
WiFi connected...yeey
After waiting 2 secs in setup(), connect result is connected. Local IP: 192.168.2.114
HHHHHHHHHH HHHHHHHHHH HHHHHHHHHH HHHHHHHHHH HHHHHHHHHH HHHHHHHH
This is the terminal output when running AutoConnect example using MBED RASPBERRY_PI_PICO with ESP8266-AT shield .
Start AutoConnect with ESP8266-AT WiFi module on MBED RASPBERRY_PI_PICO
ESP_AT_WiFiManager v1.4.0
[ESP_AT] Use ES8266-AT Command
Opening Config Portal.
*WM: LittleFS size (KB) = 64
*WM: LittleFS Mount OK
*WM: LoadCfgFile
*WM: OK
*WM: ======= Start Stored Config Data =======
*WM: Header = ESP_AT, SSID = HueNet1, PW = password
*WM: Host Name = MBED-RP2040
*WM: CCSum=0x9c7,RCSum=0x9c7
*WM: Header = ESP_AT, SSID = HueNet1, PW = password
*WM: Host Name = MBED-RP2040
*WM: Connect wifi with new params
*WM: Data cleared
[ESP_AT] Use ES8266-AT Command
*WM: Static IP : 192.168.2.114
*WM: Connect result: WL_CONNECTED
Got stored Credentials. Try to connect first
Exit Config Portal
HHHHHHHHH
This is the terminal output when running ConfigOnStartup example using WIZNET_WIZFI360_EVB_PICO with WIZFI360 shield .
Start ConfigOnStartup with ESP32-AT WiFi module on WIZNET_WIZFI360_EVB_PICO
ESP_AT_WiFiManager v1.4.0
[ESP_AT] Using ESP32-AT Command
Opening Config Portal.
*WM: LoadCfgFile
*WM: OK
*WM: CCSum=0x8f6,RCSum=0x8f6
*WM: ======= Start Stored Config Data =======
*WM: Header = ESP_AT, SSID = HueNet, PW = 12345678
*WM: Host Name = RP2040
*WM: Connect wifi with new params
*WM: Data cleared
[ESP_AT] Using ESP32-AT Command
*WM: Static IP : 192.168.2.114
*WM: Connect result: WL_CONNECTED
Got stored Credentials. Try to connect first
After waiting 0 secs in setup(), connect result is connected. Local IP: 192.168.2.114
HHHHHHHHH
Debug is enabled by default on Serial. To disable, add before startConfigPortal()
ESP_AT_wiFiManager.setDebugOutput( false );If you get compilation errors, more often than not, you may need to install a newer version of the board's core, ESP8266/ESP32-AT shield AT-command or this library version.
Sometimes, the library will only work if you update the ESP8266/ESP32-AT shield core to the newer or older version because some function compatibility.
Submit issues to: ESP_AT_WiFiManager issues
WizFi360 , such as WIZNET_WIZFI360_EVB_PICO using arduino-pico core![]() tzapu | ![]() Ken Taylor | ![]() Miguel Wisintainer |
如果您想為這個項目做出貢獻:
Copyright (C) 2020- Khoi Hoang