Multichannel networks - Separate channels for different levels about rf24network HOT 4 CLOSED

Added a branch. There is still a bit of code lacking when doing a direct write to a node, it needs to figure out the node level and set the channel accordingly, but everything else should be functional for basic RF24Mesh and Network libs.

I don't currently do any waiting after setting the channel, but I need to test this out further etc.

There would be a way to blacklist channels, right now it just uses a base channel and adds 5 for each level.

from rf24network.

This is intriguing! I'm curious to see the code, namely if you wait after the switching channels. Can you create a branch or is it still too early?

Would there be a way to blacklist channels for envs that have specifically noisy channels?

from rf24network.

I'm having no luck with this, going to abandon the idea for now. It seems like any sort of channel hopping on these devices is doomed lol.

from rf24network.

Yeah, channel hopping is typically done with time slots/intervals. After a couple hours of theorizing this idea, I couldn't imagine it working with the same/current reliability.

If channel hopping is the underlying goal, then

1. network.update() would have to encompass managing the channel as time elapses.
2. RF24Network would need a new network-reserved message type to handle clock syncing. This message could be a multicast from master or an individual call->response between child nodes and their parents.

This added complexity would inherently cost in speed and/or reliability though.

from rf24network.