CC2530: Some question about PANID confilct

Daniel Fang

Part Number: CC2530
Other Parts Discussed in Thread: Z-STACK

Zstack-cc2530-2.5.1

Zigbee can automatically change PADID after a conflict is detected. Open it by enable NWK_MANAGER definition. Some question about it.

1. In a PAN network, can only one route enable this definition?

2. Zstack uses non-beacon network. Normally, no beacon are send on the air. How does Zstack detect the PANID conflict?

3. When PANID is switching, one router is moved out of the PAN range. Then take the route back again after PANID is changed. Right now, the route disconnect from the original network for a time. How to solve it? Thanks.

over 7 years ago

0 YiKai Chen over 7 years ago

Guru 735685 points

When you set PANID=0xFFFF in f8wconfig.cfg, coordinator would choose a random PANID and broadcast/scan to collect PANID over the air to make sure its PANID won't conflict with others. After PANID is choose and network is formed, PANID won't change. So, case 3 shouldn't happen.

0 haipeng xiong over 7 years ago in reply to YiKai Chen

Intellectual 350 points

Could you please look at this question: https://e2e.ti.com/support/wireless_connectivity/zigbee_6lowpan_802-15-4_mac/f/158/p/638167/2354124?tisearch=e2e-sitesearch

There are also the following questions:

1) how to use the "nwk_manager"?

2)What is the process of detecting panid conflicts after using nwk_manager?

3)Who will send a beacon notification for detect panid conflict in non-beacon networks?

0 YiKai Chen over 7 years ago in reply to haipeng xiong

Guru 735685 points

From application point of view, you shouldn't touch nwk_manager. Can you elaborate why you want to do this?

0 Ryan Brown1 over 7 years ago in reply to haipeng xiong

TI__Guru**** 216717 points

Please refer to the ZDO Network Manager section of the Z-Stack API documentation. Only one device in a given network (either coordinator for centralized or router for distributed) can be set as the Zigbee Network Manager. PAN ID conflict detection and resolution does not occur in a non beacon-enabled network where the coordinator cannot send beacon requests, please see the Scenarios section of the 802.15.4 MAC API documentation for more details. The Z-Stack Developer's Guide describes the PAN ID conflict process.

Regards,
Ryan

0 haipeng xiong over 7 years ago in reply to Ryan Brown1

Intellectual 350 points

( PAN ID conflict detection and resolution does not occur in a non beacon-enabled network where the coordinator cannot send beacon requests)

The zstack we used is the ZSTACK-CC2530-2.5.1a, it seems to only support non beacon-enabled network, refer to :https://e2echina.ti.com/question_answer/wireless_connectivity/zigbee/f/104/t/63050

Under this premise, how to detect and avoid panid conflicts?

0 haipeng xiong over 7 years ago in reply to YiKai Chen

Intellectual 350 points

Could you please look at this question: https://e2e.ti.com/support/wireless_connectivity/zigbee_6lowpan_802-15-4_mac/f/158/p/638167/2354124?tisearch=e2e-sitesearch

what can we do when the scenarios described in the problem happened?

0 YiKai Chen over 7 years ago in reply to haipeng xiong

Guru 735685 points

If it is intended to set same PANID in all of your ZCs and turn on them to form Zigbee network when the others are off, it won't be able to detect PANID conflicts and you cannot avoid the trouble.

0 haipeng xiong over 7 years ago in reply to YiKai Chen

Intellectual 350 points

Thanks for your reply!

0 haipeng xiong over 7 years ago in reply to YiKai Chen

Intellectual 350 points

( PAN ID conflict detection and resolution does not occur in a non beacon-enabled network where the coordinator cannot send beacon requests)

The zstack we used is the ZSTACK-CC2530-2.5.1a, it seems to only support non beacon-enabled network, refer to :e2echina.ti.com/.../63050

Under this premise, how to detect and avoid panid conflicts?

0 YiKai Chen over 7 years ago in reply to haipeng xiong

Guru 735685 points

"PAN ID conflict detection and resolution does not occur in a non beacon-enabled network where the coordinator cannot send beacon requests"???

I think it should be "PAN ID conflict detection and resolution does not occur in a beacon-enabled network"

0 haipeng xiong over 7 years ago in reply to YiKai Chen

Intellectual 350 points

TI's employee, Ryan Brown1 , told me that "PAN ID conflict detection and resolution does not occur in a non beacon-enabled network where the coordinator cannot send beacon requests".

I still have a problem：
The zstack we used is the ZSTACK-CC2530-2.5.1a, it seems to only support non beacon-enabled network,
After two coordinators, which have the same panid ，have established the network and work normally . First, their RF does not overlap; Then move one of them, make their RF overlap.

Under this premise, I think the "nwk_manager"mechanism does not work, how to detect and avoid panid conflicts? Do you have any good suggestions?

0 Ryan Brown1 over 7 years ago in reply to haipeng xiong

TI__Guru**** 216717 points

Since you're hung up on it, please let me re-phrase my original statement: PAN ID conflict detection does not AUTOMATICALLY occur in a non beacon-enabled network. You can read this in Section 16.3 of the Developer's Guide. There's no synchronization, as described in the 802.15.4 MAC API. For networks that have grown over time and begin to overlap, you are free to implement ZDP_MgmtNwkDiscReq() in your application. Upon manual detection of the conflict you would reference the Z-Stack API and issue a NLME_SendNetworkReport() to the Network Manager, which would then broadcast a NLME_SendNetworkUpdate() with the updated PAN ID info before it changes its own PAN ID using macUpdatePanID()

Regards,
Ryan

0 haipeng xiong over 7 years ago in reply to Ryan Brown1

Intellectual 350 points

thanks for your reply!

Zigbee & Thread

Zigbee & Thread forum

CC2530: Some question about PANID confilct