Re: easyMesh
Posted: Fri Oct 07, 2016 3:39 pm
Do you think this is being caused by a bug in the example ino code or in the core src code? Maybe you should open an issue on the developer’s github site https://github.com/Coopdis/easyMesh/issues
I think it is a bug in the core src and it is related to the timestamps that I believe roll over after 71 minutes which is coincidental to the time that the mesh break apart broke apart.
The timestamps seem to influence the prominence a device gets in the mesh like becoming the master or the slave. EasyMesh has the goal of being self configurable so depending on exactly when a device joins sets its prominence.
I have a UDP network but is has fixed prominence in that each device has a designated roll. EasyMesh represents a good alternative and can survive a device going offline.
I think it is a bug in the core src and it is related to the timestamps that I believe roll over after 71 minutes which is coincidental to the time that the mesh break apart broke apart.
The timestamps seem to influence the prominence a device gets in the mesh like becoming the master or the slave. EasyMesh has the goal of being self configurable so depending on exactly when a device joins sets its prominence.
I have a UDP network but is has fixed prominence in that each device has a designated roll. EasyMesh represents a good alternative and can survive a device going offline.