mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 09:05:56 +03:00
[GH-ISSUE #350] Accespoint Config Mode does not work well #293
Labels
No labels
📶 WiFi
🕸️ HTTP
Branch
DEV Help Wanted
Discussion
Documentation
ESP32
Example
Good First Issue
Hotfix
In Progress
Incomplete
Needs Feeback
Priority
QA
Question
Task
Upstream/Dependancy
bug
duplicate
enhancement
invalid
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/WiFiManager#293
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bobybobybob on GitHub (Apr 7, 2017).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/350
Hello, I have four eps12E. I put these in Accespoint Config mode to display Accespoint.
With two I can connect and adjust everything.
For the other two, a stable connection is not possible. The signal travels in a few seconds so I do not see the config page.
The script code is the same for all four. Also the same firmware. Identical current source.
In serial print, writes on the non workung one something like reset ets Jan 8 2013, rst cause: bootmode:
Wdt reset
Is this a Software Bug oder Hardware problem?
á
mounting FS...
mounted file system
192.168.1.60
Standortname
24
*WM: Adding parameter
*WM: blynk
*WM: Adding parameter
*WM: STUNDEN_H
*WM:
*WM: AutoConnect
*WM: Connecting as wifi client...
*WM: Custom STA IP/GW/Subnet
*WM: 192.168.1.60
*WM: Using last saved values, should be faster
*WM: Connection result:
*WM: 0
*WM: SET AP STA
*WM:
*WM: Configuring access point...
*WM: AutoConnectAP
*WM: AP IP address:
*WM: 192.168.4.1
*WM: HTTP server started
ets Jan 8 2013,rst cause:4, boot mode:(3,1)
wdt reset
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v3de0c112
~ld
á
mounting FS...
mounted file system
192.168.1.60
Standortname
24
*WM: Adding parameter
*WM: blynk
*WM: Adding parameter
*WM: STUNDEN_H
*WM:
*WM: AutoConnect
*WM: Connecting as wifi client...
*WM: Custom STA IP/GW/Subnet
*WM: 192.168.1.60
*WM: Using last saved values, should be faster
*WM: Connection result:
*WM: 0
*WM: SET AP STA
*WM:
*WM: Configuring access point...
*WM: AutoConnectAP
*WM: AP IP address:
*WM: 192.168.4.1
*WM: HTTP server started
@maxdd commented on GitHub (Apr 14, 2017):
Have you checked your hw pins configuration of the second device?
@javieryanez commented on GitHub (Sep 21, 2017):
I have the same problem with a Witty Cloud (ESP-12F)
@tablatronix commented on GitHub (Sep 21, 2017):
Could be power supply could be corrupt memory try esptool erase flash?
@bobybobybob commented on GitHub (Sep 21, 2017):
Super Power 3.4V 3A, many Capacitators and that Pullup, Pulldown rubish for improve Stability helps not much.
I found out that the instabile ESP need one connection to WLAN and after upload new script, the problem script work without problems and most stabile. It is maybe a Hardwarebug.
@tablatronix commented on GitHub (Sep 21, 2017):
what sketch ? Does the sketch cause the reset on purpose, if so it is probably this issue
I noticed connection result 0
#425
@bobybobybob commented on GitHub (Sep 21, 2017):
Excample
I buy a new RAW ESP12E or ESP12F. The lite one no wemos. I upload a script likte
in the loop
int blabla = 0
blabla = blabla + 1
serial.print blabla
it will count up maybe up to 2000 then the watchdog Reset come and it start again new
When i upload the same sketch again, it count not as much in first flash. Maybe in first it count up to 8000, in the second upload it count only to 5000 and after some more upload most counting end ner 1000-2000.
But if i upload a script that make hardcoded wlan connection and then overwrite it withh the counter script without wlan, it count up to endlees or one some ESP the watchdog again but in very higher numbers where a litte capacitator realy help stability.
That is the moment where Wifi Manager work very well even in AP Mode. But after Upload the same code again it can make trouble so it is better upload a manual wlan again and then the script with wifimanager.
Is that ESP12 one time in his life connected with wlan, it is stability. Stability go away when flash firmware new + erase.
@tablatronix commented on GitHub (Sep 21, 2017):
I don't understand, Why is it resetting ? Are you resetting it on purpose ? I cannot follow your logic without code. What happens with a simple example.
@bobybobybob commented on GitHub (Sep 21, 2017):
do you can read german? if yes i can write Deutsch