CC2652P: Why Zigbee 3.0's Rejoining can't support ALL-channels scanning?

Aries Lord

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

I have found that in both SDK 6.4.0 and Z-stack 3.0.2. When end device rejoin into new parent-node, it can only scan the channel which it has joined. It mean that the end-device can't recover it network by rejoining when the coordinator has change the channel of network.

over 3 years ago

0 Ryan Brown1 over 3 years ago

TI__Guru**** 223107 points

Hi Aries,

Please refer to the MODE_REJOIN processing during ZDO_StartDevice where NLME_NetworkDiscoveryRequest is called. Currently only the runtimeChannel is used but you can modify this behavior for a channelList if desired. Note the MANAGED_SCAN define (currently not included in quarterly tests) and that in some cases the runtimChannel will become MAX_CHANNELS_24GHZ.

Regards,
Ryan

0 Aries Lord over 3 years ago in reply to Ryan Brown1

Genius 5400 points

It is no use, NLME_ReJoinRequest can only select 1 channel.

0 Ryan Brown1 over 3 years ago in reply to Aries Lord

TI__Guru**** 223107 points

You can try to perform a similar method I described for bdb_rejoinNwk. For either rejoin or orphan functionality, Z-Stack only intends to only search the channel saved in its NIB/NV memory by default. This feature is not a requirement of the Zigbee Specification.

Regards,
Ryan

Zigbee & Thread

Zigbee & Thread forum

CC2652P: Why Zigbee 3.0's Rejoining can't support ALL-channels scanning?