The General Interest forum is for non-support discussion only. If you have a question about, or need help with a Silicon Labs product, please visit one of the individual product forums.
After the same panid and channel number, the panid changes after the conflict occurs, resulting in the original network being unavailable. How can I solve the problem?
08/241/2018 | 01:16 PM
Excuse me, a coordinator A and n terminals have already set up a network and communicate normally. At this time, the channel number and PanID setting of the coordinator B are the same as those of the coordinator A, which causes the coordinator to generate a collision, and then the coordinator's PanID changes, and the original terminal cannot communicate normally. In short, the addition of the same coordinator will destroy the entire network and make it embarrassing.
May I ask how this can be solved, or is there any solution?
Discussion Forums
Unanswered
When coordinator B forms network, it should broadcast its PANID and if there is conflict, coordinator B should increase its PANID to avoid collision. Do you manually force coordinator B to use the same PANID as coordinator A and cause this issue?
After the same panid and channel number, the panid changes after the conflict occurs, resulting in the original network being unavailable. How can I solve the problem?
Excuse me, a coordinator A and n terminals have already set up a network and communicate normally. At this time, the channel number and PanID setting of the coordinator B are the same as those of the coordinator A, which causes the coordinator to generate a collision, and then the coordinator's PanID changes, and the original terminal cannot communicate normally. In short, the addition of the same coordinator will destroy the entire network and make it embarrassing.
May I ask how this can be solved, or is there any solution?