The basis of mesh networking involves self-forming, redundant communication paths and self-healing. A mesh network gets stronger and more robust by any additional node that is included in the network. Each node will add new optional routing paths for safe connectivity and reliable data communication in changing environments.
Last Update: August 8, 2017
December 21, 2016
1775
Tinymesh Q&A Related Knowledge Base Posts - [TINYMESH] “How can I understand, when the CTS goes low, if the data have been delivered or not? If you have an alternative way to understand if the data have been delivered or not, please let me know (data going from the routers to the gateway).” [TINYMESH] some breaks in data tranfer which can take up to 0,5 second. Transmition of 8kB file takes 10 minutes. Are you able to help somehow and recommend settings to speed I up? [TINYMESH] “We have a doubt about the connections dynamic and network architecture. Consider the image below: 1 – Gateway, Router and End device ar configured with the same RF Power 2 – Gateway signal can reach directly to End Device 3 – Router can reach to Gateway and End Device 4 – The End Device only can reach the Router when transmitting, but receive the signal from Gateway directly Although the end device can receive the signal from the Gateway (above RSSI acceptance level), once the End Device can’t reach the Gateway directly, the connection is never established and the second way through Router is never choosed. The tiny mesh algorithm favors the shortly way to gateway if the rssi level is above acceptance level. If the end device receive the signal from Gateway above acceptance level, but is not able to reach the gateway directly, even if we have a router between Gateway and End Device the connection is never establish. Do you have any explanation to this behavior and a way to improve and avoid this kind of scenario? “
