ESP8266 Community Forum

- Wed Dec 24, 2014 4:33 pm #5638 Quick item for you..


Server starting at port:9999
OK

Server Tomeout :600 sec
OK


I guess that should be "Timeout".

Peter Scargill - http://tech.scargill.net

- Wed Dec 24, 2014 4:38 pm #5639 Erm.. . CIFSTATUS - use of this quickly results in failure...

I managed to get a response out of the first monitored unit... once.. then...

Code: Select allOK

SEND OK

 << AP GOOD ...>
+IPD,251,7:NO IP

OK

SEND OK
CIFSTATUS


ERROR

 << AP GOOD ...

Ok so I'm starting to get FAIL a lot now...

Code: Select allERROR
+CWJAP:1

FAIL

  Scan starting...Data Scan Completed
Short Neighbors(1):"MESH-13404",-23,1a:fe:34:9f:4e:ef
Short Neighbors(2):"MESH-91551",-25,1a:fe:34:9a:59:bf
Short Neighbors(3):"MESH-80435",-40,1a:fe:34:9d:fb:00
 Connecting...>>>>>>>>>>>> +CWJAP:1

FAIL

  Scan starting...Data Scan Completed
Short N

These units incidentally are all in one room.

..... Use CIFSR to check links. Use CIFSTATUS to check link-id. Its 251!!!
connect ur computer with any AP. i

Peter Scargill - http://tech.scargill.net

- Wed Dec 24, 2014 4:42 pm #5640

Ok so I'm starting to get FAIL a lot now...

Code: Select allERROR
+CWJAP:1

FAIL

  Scan starting...Data Scan Completed
Short Neighbors(1):"MESH-13404",-23,1a:fe:34:9f:4e:ef
Short Neighbors(2):"MESH-91551",-25,1a:fe:34:9a:59:bf
Short Neighbors(3):"MESH-80435",-40,1a:fe:34:9d:fb:00
 Connecting...>>>>>>>>>>>> +CWJAP:1

FAIL

  Scan starting...Data Scan Completed
Short N

I have the same result

ESP8266.com Moderator
Lets get the party started and +1

[url=https://www.banggood.com/custlink/KvGGhGF4wG[/url]

I like ESP8266 and ESP8285 and ESP32

- Thu Dec 25, 2014 4:58 pm #5700 It is difficult to re-create the problem and debug it, however, I have modified couple of parts.

The problem is happening with "Time to connect" with AP. I have increased the time with periodic checking. Also, channel shifted to 1 from 11.
Please try the new binary.

Try at 115200.
As I mentioned earlier, "Only self-joining and self-healing has been implemented". The data-communication happening (between clients and server is the part of Link info sharing will be used in routing table]

A generic protection may give better result, "if an AP cant be joined after N tries, ignore it and move to next best one". However, that part is coded but not enabled because of debugging. If the current release creates the problem, that may be enabled.

Thanks.

Attachments

bin_0.3.rar

(136.77 KiB) Downloaded 276 times