How should I reset peer manager ranking

RE: How should I reset peer manager ranking

T IJ — Mon, 04 Oct 2021 12:36:12 GMT

Thank you, I think I will try to implement something that will correct this.

I've been told that if you do something and think this situation will never happen that it will happen. Even though it is very unlikely.

RE: How should I reset peer manager ranking

Einar Thorsrud — Mon, 04 Oct 2021 12:29:49 GMT

Good questions. I guess it made sense to document corner cases and assumptions when writing API documentation. If you really want to do this, then you can implement something suggested, by updating the FDS records. But the only consequence will be adding dead code that worst case contributes to unnecessary bugs and best case has no use at all.

RE: How should I reset peer manager ranking

T IJ — Mon, 04 Oct 2021 12:21:51 GMT

If it theoretically never happens why is it mentioned in the error code? This would suggest me that there is a possibility that it will occur during operation and that I have to make a way to reset the rank levels from the start.

 * @retval NRF_ERROR_RESOURCES      If the highest rank is UINT32_MAX, so the new rank would wrap
 *                                  around to 0. To fix this, manually update all ranks to smaller
 *                                  values, while still keeping their order.

RE: How should I reset peer manager ranking

Einar Thorsrud — Mon, 04 Oct 2021 12:14:29 GMT

Hi,

The SDK does not have any support for resetting the peer rank as this is not considered a relevant problem. For this to be a problem the you would have to establish connection to bonded peers 2^32-1 = 4294967295 times (UINT32_MAX as you write) and it is difficult to see how this could ever happen in practice. For instance, if you connect to a bonded peer every second it will take 136 years for this to manifest itself as an issue. So in practice any code you add to do this will just add to the complexity without ever being useful.