-
Notifications
You must be signed in to change notification settings - Fork 13.3k
AP mode module get chock and continuous LmacRxBlk:1 #2176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I might add this also happened when nothings connected to AP module , so it is not related to any cause from browser multi connection trafficking which is mentioned in this issue |
Could you please post the sketch code which exhibits this issue? Thanks. |
dear @igrr do you have any suggestion? is it possible in case of chocking, internal routine or watchdog timer close all connection and flush all stack ? something like reset TCP routing |
I've got the same effect when client is abruptly disconnected (for example when power failure occurs). When power is restored connection to AP seems established but TCP server goto havoc like this : last line repeating over and over, WifiServer is not working and need restart. My question is how to detect such problem in server code and close client releasing TCP stack ? At least wdt reset would be nice |
that would be good solution if @igrr have any offer for that , however I use the EEPROM for store data and restore it in startup I think this issue related to memory disorder , following is the decode exception ` |
I disable EEPROM and use the simpler code but still LmacRxBlk:1 gonna kill me |
There is some UDP listener in your code, and you aren't processing incoming On Sat, Jun 25, 2016, 15:55 mehrdad [email protected] wrote:
|
Probably you have initialized DNSServer library but aren't calling On Sat, Jun 25, 2016, 15:57 [email protected] wrote:
|
I did Ivan, |
oh boy you were right , somehow in my code MyMode[0] not be AP mode , thanks , very thank you dear Ivan, |
following is new debug , but still have terrified error LmacRxBlk:1, what would be optimize solution to let the TCP not chocked |
If you need to serve lots of stuff at the same time, you probably need to use ESPAsyncWebServer library instead of ESP8266WebServer. |
thanks @igrr Ivan , you are right and I'm starting to go with this magnificent me-now-dev repo, unfortunately it not has much example as your repo , however sometimes my module network icon (in windows)get busy whereas debug shows nothings and debug level set to all |
Basic Infos
Hardware
Hardware: ESP-12E
Core Version: 2.2
Description
Problem description
Settings in IDE
Module: NodeMCU rev 1
Flash Size: ?4MB/1MB?
CPU Frequency: ?80Mhz?
Flash Mode: ?qio?
Flash Frequency: ?40Mhz?
Upload Using: ?OTA / SERIAL?
Reset Method: ?ck / nodemcu?
hi @igrr , I made sketch can sweitch bettwen AP mode and Station mode , but most of time when back to AP mode, module get chock and issue endless LmacRxBlk:1,
is there any way to break this loop and free the wifi resource for normal operation
following the debugging message and image of operation
`
Entering the Station Mode
%%scandone
no 2010 found, reconnect after 1s
reconnect
f 0, %%%%%scandone
no 2010 found, reconnect after 1s
reconnect
f -180, %%%%scandone
no 2010 found, reconnect after 1s
reconnect
f r0, %%%%scandone
no 2010 found, reconnect after 1s
%reconnect
f 0, %%%%scandone
no 2010 found, reconnect after 1s
reconnect
f -180, scandone
del if0
usl
ets Jan 8 2013,rst cause:2, boot mode:(3,6)
load 0x4010f000, len 1264, room 16
tail 0
chksum 0x0f
csum 0x0f
~ld
my sketch automatically back to AP mode in case not connect to modem successfully
scandone
del if0
usl
mode : softAP(5e:cf:7f:05:fb:a8)
add if1
dhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1)
bcn 100
AP IP address: 192.168.4.1
HTTP server started
add 1
aid 1
station: b8:76:3f:45:64:43 join, AID = 1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
`
The text was updated successfully, but these errors were encountered: