ESP8266 Community Forum

- Wed Oct 26, 2016 2:11 pm #57172 [quote]This node: C2823 Received from 138CFE msg=1967Hello from node 6a82f

This node: C2823 Received from 138CFE msg=368Hello from node 138cfe

This node: C2823 Received from 138CFE msg=369Hello from node 138cfe

This node: C2823 Received from 138CFE msg=1968Hello from node 6a82f

This node: C2823 Received from 138CFE msg=1969Hello from node 6a82f

This node: C2823 Received from 138CFE msg=370Hello from node 138cfe

This node: C2823 Received from 138CFE msg=1970Hello from node 6a82f

This node: C2823 Received from 138CFE msg=371Hello from node 138cfe

This node: C2823 Received from 138CFE msg=1971Hello from node 6a82f

This node: C2823 Received from 138CFE msg=1972Hello from node 6a82f

This node: C2823 Received from 138CFE msg=372Hello from node 138cfe

This node: C2823 Received from 138CFE msg=373Hello from node 138cfe

This node: C2823 Received from 138CFE msg=1973Hello from node 6a82f

This node: C2823 Received from 138CFE msg=1974Hello from node 6a82f

This node: C2823 Received from 138CFE msg=374Hello from node 138cfe[/quote]

As you can see from the above after about an hour one esp falls off 1500 messages after having been within a few counts of the messages of the others
All 3 devices have identical code and have almost equal opportunity to get the message out..in other words their message counts are within 10 counts of each other but it never lasts for long.

below is a point of failure
[quote]
This node: C2823 Received from 138CFE msg=1460Hello from node 138cfe

This node: C2823 Received from 138CFE msg=1461Hello from node 138cfe

This node: C2823 Received from 138CFE msg=1462Hello from node 138cfe


Exception (29):
epc1=0x40204a23 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000

ctx: cont
sp: 3fff04b0 end: 3fff07b0 offset: 01a0

>>>stack>>>
3fff0650: 3fff0630 3fff06a0 3fff1fa8 40204a23
3fff0660: 3fff235c 0000003f 00000031 00138cfe
3fff0670: 00138cfe 00000005 3fff06e0 00000005
3fff0680: 3fff06e0 3fff1fa8 3ffef5a0 40204c8c
3fff0690: 3fff2414 00000002 3ffef788 00000030
3fff06a0: 3fffbfb4 0000003f 00000031 3fff3804
3fff06b0: 00138cfe 3fff1fa8 00000001 00138cfe
3fff06c0: 000246b0 ffeb6335 3ffef5a0 3fff1fa8
3fff06d0: 3fffdad0 3ffef5a0 3fff1fa8 40205ff3
3fff06e0: 3fff2414 0000000f 00000002 40205fb0
3fff06f0: bb7c8274 3fff1fe0 3ffef5a0 40205362
3fff0700: 40207e1e 3ffef5a0 00000000 3fffdad0
3fff0710: 40208c9f 00000000 00000201 000246a6
3fff0720: 3fff10ec 40205a82 3ffef5a0 3ffef788
3fff0730: 3fffdad0 00000000 3ffef5a0 40204724
3fff0740: 00000000 3ffef59c 3ffef5a0 402020a7
3fff0750: 00000000 00000000 00000000 00000000
3fff0760: 00000000 00000000 00000000 00000000
3fff0770: 00000000 00000000 00000000 00000000
3fff0780: 00000000 00000000 00000001 3ffef788
3fff0790: 3fffdad0 00000000 3ffef781 40203ec8
3fff07a0: feefeffe feefeffe 3ffef790 40100718
<<<stack<<<

ets Jan 8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v40106ea4
~ld
setDebugTypes 0x3
0x2 init():
0x2 apInit(): Starting AP with SSID=Mainship796707 IP=192.168.35.1 GW=192.168.35.1 NM=255.255.255.0
0x2 DHCP server started
0x2 AP tcp server established on port 5555
0x2 stationInit():
startHere: New Connection, adopt=1

This node: C2823 Received from 138CFE msg=3Hello from node 138cf[/quote]

The above is a trace for a single esp in the mesh it is highly probable that the other devices also fell off the mesh but they did get back on.
I don't think it is a power issue since I have other esp's squawking GPS information wrapped in UDP packets that stay up for days at a time.

- Wed Oct 26, 2016 2:57 pm #57176 Yes there is a reliability problem. Lost messages are one issue. Work is being done to fix the issues.

- Wed Oct 26, 2016 3:13 pm #57177

Exception (29):
epc1=0x40204a23 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000

ctx: cont
sp: 3fff04b0 end: 3fff07b0 offset: 01a0

This actually is pointing to simplelist

Code: Select allDecoding 1 results
0x40204a23: SimpleList ::AllocOneBlock(bool) at /home/user/Arduino/libraries/SimpleList/SimpleList.h line 230
:  (inlined by) SimpleList ::push_back(String) at /home/user/Arduino/libraries/SimpleList/SimpleList.h line 77
:  (inlined by) easyMesh::sendPackage(meshConnectionType*, String&) at /home/user/Arduino/libraries/easyMesh/src/easyMeshComm.cpp line 89

I think I'm going to look at dumping simplelist ...

- Wed Oct 26, 2016 4:53 pm #57181

Yes I have a devel version of this code located here: https://github.com/sfranzyshen/easyMesh/tree/devel
It use a single ssid for the mesh ...

Sweet! Let me know if you need any help on this. I can spare sometime on these.

Here's a list of items I am trying to workout today ... to push to github for tonight ...

- code not loop friendly breakup scancb & connectbestap use flag ...
- create an even simpler application for no-timing ... trying to eliminate application bugs ...
- figure out the relationship with nodeSyncRequest(uint32), nodeSyncStatus(enum), and needsNodeSync(bool)
- eliminate os_timer ... create if->then loop or scans ...
- STA ... handle AP tcp timeout(dropping) better -> if wifi good try to reconnect ... blah blah
- evaluate the timing code ... for possible rollover problems ... and other gottchas ... work it back in to code
- demotoy change yerp ?? maybe look for delays in the rest of code...
- messages backing up in the sendQueue causing wdt resets ... dump messages instead of run out of memory