4 ms·
Would be interesting to know about things like latency, packet loss, maximum throughput etc (and how these properties change over larger distances). Also, how
by JosephRedfern 9y ago
Would be interesting to know about things like latency, packet loss, maximum throughput etc (and how these properties change over larger distances).
Also, how in an "in the wild" setup works with 802.15.4e, especially with moving nodes -- how would routing table normally be determined? Signal strength alone, or is it possible to discover how central a neighboring node is to the network and use that to inform the choice too? Really interesting subject.
- bipson 9y agoMoving nodes are summarized under the term mobility, and in RPL it is usually handled by reconstruction from the top or re-discovery of parents by the node itself. Timers play an important role, and mobility is a known weak spot of RPL. The choice of preferred parent is governed by the objective function OF, which could be anything, but usually is the rank of the node (relative to the DODAG root). If you are really interested, RPL is an open IETF internet standard, so are the underlying protocols and principles. Down the rabbit hole it is.
- ejanus 9y agoI am trying to code neighbor discovery, you be willing to answer some technical questions? Maybe via email.
- fredrik4943 9y agoFredrik, Thingsquare CTO here. We have a bit more detailed information about how we use mesh and RPL here: http://www.thingsquare.com/docs/mesh/ http://www.thingsquare.com/docs/mesh/ Regarding mobility, we're using a number of tricks and custom solutions to discover and quickly join new networks/parents - in vanilla RPL networks it sometimes takes a long time to drop a bad or distant parent, causing long delays for mobile devices.