Hi Yves,
Thanks for reply.
I perfectly got your suggestions.
I will attach another image to explain better my tecnhical doubt.
Consider this situation as an example (it’s not my real case).
I installed a network with 30 anchors (in the image, green squares with seat numbers for each anchor)
At some point in time, I want to add another anchor that would be the 31th (light blue square).
The blue circle is the 31th-anchor range.
The red circle is the top-left anchor range (with the seat number equal to 0).
We said that to let the 31th anchor come into the pre-existing network no anchor within the network should be able to see two anchors sharing the same seat number.
The 31th anchor can “see” anchor 6, anchor 7, anchor 8, anchor 14, anchor 9, anchor 10, anchor 11, anchor 12, anchor 15. It does not see anchor 0, so potentially seat number 0 is available to be taken from 31th anchor. But, as we can see from circumference intersection, if 31th anchor assumes seat number 0 there would be some anchors (6,7,9,10) that see 2 anchors with seat number 0 (the top-left anchor and the 31th anchor). This is prohibited and the new anchor will not be able to come into the network.
If I could assign manually seat number for sure I would not assing seat number 0 to the 31th anchor (maybe I could assign for example seat number 29 to avoid collision).
I do not know if the system manages the problem in a smart way (like humans) or just assign available seat numbers to new anchors and then, if there is a collision like in case I assign seat number 0 to 31th anchor, just push new anchor out from the network and do not let it come in.
I hope I have explained my doubt succesfully, I did my best.
Thank you for your time and consideration,
David