ESP8266 Community Forum

- Sat Oct 29, 2016 4:22 pm #57358 [quote]
This node: C2823 Received from 6A82F msg=5983Hello from node b5596

This node: C2823 Received from 6A82F msg=2857Hello from node 6a82f

This node: C2823 Received from 6A82F msg=2858Hello from node 6a82f

This node: C2823 Received from 6A82F msg=5984Hello from node b5596

This node: C2823 Received from 6A82F msg=5985Hello from node b5596

This node: C2823 Received from 6A82F msg=2859Hello from node 6a82f[/quote]

I suspect that we aren't there yet.

Info
3 devices and it looks like one dropped of and restarted ( message number is reset to zero).
The above listing is for a device that didn't drop off.

- Sat Oct 29, 2016 4:30 pm #57359 Maybe it could be useful to use a predictive approach.
Each device has a list of devices that are on line and the last message number from each device.
Now when a device goes offline and there is at least one other device that remained the dropped device
could get from the surviving device the last message number it sent so it could predict the number of its next message.

- Sat Oct 29, 2016 7:04 pm #57367

What information would you get? Maybe I can send it to the LCD in a place that doesn't get overwritten.

I'm looking for anything memory related ... like "out of memory" ... or "failed" in both memcpy memset and json and simplelist

I just got an exception and I tried the Decoder but I got this error.

paths have changed in newer Arduino ide. your arduino ide builds your sketch at a location like C:\Users<username>\AppData\Local\Temp\arduino_build_NNNN\ EspExceptionDecoder creates a directory at C:\Users<username>\AppData\Local\Temp\buildNNNNN.tmp\ It is looking for the files in that directory, so copy all the files from the \arduino_build_XXX to the \buildNNNNN.tmp EspExceptionDecoder directory ... and you should be able to open the Exception window ... Where NNNN are random numbers generated by the arduino ide ...

- Sat Oct 29, 2016 7:32 pm #57369

This node: C2823 Received from 6A82F msg=5983Hello from node b5596

This node: C2823 Received from 6A82F msg=2857Hello from node 6a82f

This node: C2823 Received from 6A82F msg=2858Hello from node 6a82f

This node: C2823 Received from 6A82F msg=5984Hello from node b5596

This node: C2823 Received from 6A82F msg=5985Hello from node b5596

This node: C2823 Received from 6A82F msg=2859Hello from node 6a82f

I suspect that we aren't there yet.

Info
3 devices and it looks like one dropped of and restarted ( message number is reset to zero).
The above listing is for a device that didn't drop off.

what does this data show? what code are you running?

I dropped back to just running the easyMesh core (no-timing) code and a simple application layer for a reason. because the very core of this code has problems. If we can not get two nodes running simple code to manage to stay connected to each other ... than what good is trying to get 100 nodes running with all sorts of other stuff going on in the application layer (right now).

we need to take baby steps ... and we have been ... the rollover is not an issue anymore (unless it pops back up in the timing code) ... the wifi scanning is working as expected ... as well as other clean ups that have improved it's stability ... I will continue working on things as I have ...

BTW I have now been running the current code (no-timing) for over 24 hrs with out any hiccups ... on two nodes ... running the testHere example (see the source ... it does nothing at all) just passing nodesync messages back and forth ... while the unconnected STA node keeps scanning the network over and over ... So ... how sure are you about exactly what is causing your resets? what information (logging) can you share outside of the application layer ??can you set you debugging to include more information ...

Code: Select allmesh.setDebugMsgTypes( ERROR | MESH_STATUS | CONNECTION | SYNC | COMMUNICATION );

??