You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have comparably big rpl-classic network (100 nodes). My devices are modified cc1310 controllers.
Sometimes network starts changing its routes frenquently, and it causes link problems.
I discovered something interesting:
Log of one device showed, that it probed parent candidate, selected it as new parent, but after 10 seconds parent rank got increased by 200, so parent now is not preferred, and node starts searching new parent, causing more traffic. Seems like when traffic rises, nodes don't keep up their "true" rank, and advertise their old rank, causing children switch to them (and switch back after updating rank).
Worth mentioning that this network have about half devices, using old contiki (about 2017 year release) due to some updating issues, so maybe this "bug" was fixed and caused by outdated firmware.
The text was updated successfully, but these errors were encountered:
I have comparably big rpl-classic network (100 nodes). My devices are modified cc1310 controllers.
Sometimes network starts changing its routes frenquently, and it causes link problems.
I discovered something interesting:
Log of one device showed, that it probed parent candidate, selected it as new parent, but after 10 seconds parent rank got increased by 200, so parent now is not preferred, and node starts searching new parent, causing more traffic. Seems like when traffic rises, nodes don't keep up their "true" rank, and advertise their old rank, causing children switch to them (and switch back after updating rank).
Here I have some logs and configurations:
Some config contents (I can share more configs if needed):
Worth mentioning that this network have about half devices, using old contiki (about 2017 year release) due to some updating issues, so maybe this "bug" was fixed and caused by outdated firmware.
The text was updated successfully, but these errors were encountered: