Nodes stuck in (re-)connection-establishment

Lukas F.
Posts: 5
Joined: Tue May 02, 2017 8:59 pm

Nodes stuck in (re-)connection-establishment

Postby Lukas F. » Fri May 19, 2017 9:22 pm

So one more new topic from me today,

I have two technical questions (or rather observations):

1. Once a connection is established in LOCAL or ONLINE mode and the router disconnects (e.g. because of a blackout), the mesh-nodes won't re-connect to it even if the WiFi is back up but rather get stuck in the scanning-/connection-establishment-process. Is there another way to catch such an error besides cyclically checking, if the node is still enabled via a timer?

2. The nodes bahaviour whilst the enabling process seems to be kinda random. In some occasions, the devices connect to the router almost instantaeously, but often, the connection-establishment-process takes veeeeeery long (up to 5-10mins I think) or the nodes get even stuck in it. Log:

Code: Select all

SDK ver: 1.5.3 compiled @ Nov  4 2016 23:20:14

phy ver: 1104, pp ver: 9.9
 
user_init: Starting the initialization-process!
mesh version: v1.3.3
mode : sta(18:fe:34:d4:08:2c) + softAP(1a:fe:34:d4:08:2c)
add if0
add if1
dhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1)
bcn 100
scan-ch:0
f r0, scandone
sssid:testNetwork, ssid:testNetwork, set:0, sbssi:00:00:00:00:00:00  bssid:62:01:94:0b:d8:5blast:1
connect_dest_chan:1
f r0, espconn_mesh_scan_done connect testNetwork
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)

state: 3 -> 5 (10)
add 0
aid 1
cnt
state: 5 -> 0 (2)
rm 0
connect_dest_chan:1
f r0, scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 1
cnt
state: 5 -> 0 (2)
rm 0

connect_dest_chan:1
f r0, scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 1
cnt
state: 5 -> 0 (0)
rm 0
scan-ch:1
f r0, connect_dest_chan:1
scandone
f r0, scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)

add 0
aid 1
cnt
state: 5 -> 0 (0)
rm 0
scan-ch:1
f r0, connect_dest_chan:1
scandone
f r0, scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 1

cnt
state: 5 -> 0 (0)
rm 0
scan-ch:1
f r0, connect_dest_chan:1
scandone
f r0, scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 1
cnt

state: 5 -> 0 (0)
rm 0
scan-ch:1
f r0, scandone
connect_dest_chan:1
f r0, scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 1
cnt
state: 5 -> 0 (2)
rm 0
connect_dest_chan:1
f r0, scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 1
cnt
state: 5 -> 0 (2)
rm 0

connect_dest_chan:1
f r0, scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 1
cnt
state: 5 -> 0 (0)
rm 0
scan-ch:1
f r0, connect_dest_chan:1
scandone
f r0, scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)

add 0
aid 1
cnt
state: 5 -> 0 (0)
rm 0
scan-ch:1
f r0, connect_dest_chan:1
scandone
f r0, scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 1

cnt
state: 5 -> 0 (0)
rm 0
scan-ch:1
f r0, connect_dest_chan:1
scandone
f r0, scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 1
cnt



Does anybody know, why this happens and what I can do to prevent this kind of behaviour?

Ah and while I'm already at it: mesh won't compile with SDK v2.1.0 yet (always leaves me with "undefined reference to uart_div_modify), just for your information.

Greetings,

Lukas

PS: SDKs tried: 2.0.0 as well as 1.5.3
Mesh-Versions tried: 1.3.3 (latest release on GitHub), 1.3.1 as well as the latest debug-for-light-version

Who is online

Users browsing this forum: No registered users and 4 guests