- Sun Oct 16, 2016 1:17 pm
#56601
the next part of the client device side stuff would be a captive portal with a popup "login to network" dialog ... that will open the user web browser ... perform a dns redirect to http://MyMesh ... opening our web user interface ... regardless of which AP the client device connects to ...
- Wed Oct 19, 2016 6:53 pm
#56810
Hi Sfranzyshen,
Been following Coop's and your Git repos for the easyMesh. Kudos to you folks for bringing it this far. Kudos to you in particular for further spearheading the further development for this.
Ran your start-here example on 5 nodes. I spaced out the time delay between each to be about 2sec to better observe the packets on the terminal. Works like a charm! Although, I see some nodes dropping off every now and then. Will double check to make sure it isn't a power related issue.
Work for tomorrow:
1. Have one node control all the LEDs to better visualize the synchronization.
2. Increase overall mesh broadcast rate.
Regards,
NJ
Test Setup
COM Port Screenshot showing node dropping
Been following Coop's and your Git repos for the easyMesh. Kudos to you folks for bringing it this far. Kudos to you in particular for further spearheading the further development for this.
Ran your start-here example on 5 nodes. I spaced out the time delay between each to be about 2sec to better observe the packets on the terminal. Works like a charm! Although, I see some nodes dropping off every now and then. Will double check to make sure it isn't a power related issue.
Work for tomorrow:
1. Have one node control all the LEDs to better visualize the synchronization.
2. Increase overall mesh broadcast rate.
Regards,
NJ
Attachments
- Thu Oct 20, 2016 7:36 pm
#56875
changes to the way destId was being set have been made in both nodesync and timesync functions and a fix in easyMeshConnection to correct data corruption that might correct some of the problems we have been having ... have a look at the changes in https://github.com/sfranzyshen/easyMesh/tree/devel
- Fri Oct 21, 2016 10:01 am
#56900
I ran this code over night with no resets or mesh loss ... can anyone else confirm this?
sfranzyshen wrote:changes to the way destId was being set have been made in both nodesync and timesync functions and a fix in easyMeshConnection to correct data corruption that might correct some of the problems we have been having ... have a look at the changes in https://github.com/sfranzyshen/easyMesh/tree/devel
I ran this code over night with no resets or mesh loss ... can anyone else confirm this?
