CC2538: Network Scanning for End Devices in a Zigbee Network

Jawad Butt

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

Hi guys,

I am keen to know that is there any way to scan a network from a Coordinator or Router device (ZDO_COORDINATOR or RTR_NWK) for potential end points (same cluster) in ZStack 3.0? I would like to have a list of potential end points before issuing/initiating any join permits or binding requests to them. I couldn't find any thing particular in BDB Api (as used in example projects).

I have tried using bdb_StartCommissioning with BDB_COMMISSIONING_MODE_NWK_STEERING mode only but I believe join permits are issued at the end if the node is on a network. Are we, as a user, supposed to have any input at that stage or is it the intrinsic design of a Zigbee network formation? I have tried to explore the ZDO api but couldn't find anything discrete.

My apologies if I am missing something fundamental about Zigbee networks here as I am not really well-versed about the underlying working of them. Any pointer would be greatly appreciated!

Cheers

Jawad

over 6 years ago

0 YiKai Chen over 6 years ago

Guru 735695 points

You can use ZDP_ActiveEPReq to do active endpoint request from coordinator or router.

0 Ryan Brown1 over 6 years ago

TI__Guru**** 221057 points

Hi Jawad,

In addition to what YK has suggested, you can also parse incoming device announces to retain the short address of the node you are inquiring about. I suggest that you read the Z-Stack 3.0 Developer's & API Guide as well as review this SLA (although designed for SimpleLink devices): http://dev.ti.com/tirex/explore/node?node=AJeGnyIqlkquNAYMtLtovQ__pTTHBmu__LATEST

Regards,
Ryan

0 Jawad Butt over 6 years ago in reply to YiKai Chen

Prodigy 210 points

Thank you for your pointer YiKai, it really helped me on my way.

Cheers

0 Jawad Butt over 6 years ago in reply to Ryan Brown1

Prodigy 210 points

Hello Ryan,

That was actually a bit of a challenge for me to use the method pointed by YiKai as the documentation doesn't really tell much about it. Your nudge about device announce parsing really helped a lot. (I also ended up ordering a CC26x2R LaunchPad to test the Zigbee network as per the SLA shared by you)

I do have one similar sort of question. Once an end point has joined a network but has not been 'bound' yet, can a coordinator remove (kick out) this node from the network altogether? What I mean is if this is some rogue node it can act as a packet sniffer, right? Also is there a way in ZStack to disable/ban the rejoining of these devices or of new devices?

Apart from ZStack Developer's and API guides, which are really useful, I found one other document that helped me a lot and can be found at this link.

Cheers

Jawad

0 YiKai Chen over 6 years ago in reply to Jawad Butt

Guru 735695 points

Try to refer to sunmaysky.blogspot.com/.../how-to-handle-end-node-announcement.html

0 Jawad Butt over 6 years ago in reply to YiKai Chen

Prodigy 210 points

Thank you YiKai,

That was pretty spot on, exactly I was looking for. Do you have any info regarding kicking out a joined device and ban the rejoin?

Cheers

Jawad

0 YiKai Chen over 6 years ago in reply to Jawad Butt

Guru 735695 points

You can use API ZDP_MgmtLeaveReq to kicking out a joined device.

Zigbee & Thread

Zigbee & Thread forum

CC2538: Network Scanning for End Devices in a Zigbee Network