This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Connecting End device to authorized Parent

Other Parts Discussed in Thread: Z-STACK

How can my  End device will join to particular Coordinator/Parent , if two or more coordinator is there.

  • First, you can disable permit join of all your ZC and ZR. Then, enable the one (ZC or ZR) that you want your ZED to join and start the association process. After your ZED finishes join to the specified ZC or ZR, disable the permit join.

  • If there are any other coordinator in the surrounding which we doesn't know, which enable the permit join. How can i proceed

  • If the coordinator is made by you, you can disable permit join. If not, most of coordinator disable permit join by default as I know.

  • I have set a PAN id in Coordinator and Enddevice. I read the zigbee stack. I need to change the  -DZDAPP_CONFIG_PAN_ID=? in both coordinator and End device for example, DZDAPP_CONFIG_PAN_ID= 0x012E3. Coordinator will create a network with this panid and Enddevice will sends a beacon request with this panId. End device should join the Coordinator whose panid is  0x012E3. But my end device is joining to other coordinator with panid 0xFFFF among two coordinator's.

  • Do you use packet sniffer to check what happens?

  • Can i Hard-code the MAC Address of Coordinator in the End device, So that while Sending the Beacon Request,the End device will search to that MAC address and join to it?If this possible, Can you suggest me, where to Hard-Code The MAC Address of Coordinator in the End device. 

  • No, you can't do this.

  • So, there is no Method in the Zigbee to join the End device to Particular Parent other than PAN ID?. Because, there is a possibility to have same PAN ID in the other Coordinator also, at that time my End device Should not Join to that Coordinator. I hope you understand my Scenario.

  • According to Zigbee spec, coordinator will choose a different PANID when it forms a new zigbee network if it finds there  is another coordinator with the same PANID. Basicaaly, you can' t have two zigbee network with the same PANID in  radio range.

  • So what happen with this Scenario.

     I am having Coordinator with PAN ID 0x1E73. And End device also i have Set a PAN ID 0x1E73 to join this PAN ID, when device is ON. But Before  Powering ON my Coordinator, There is another Coordinator with same PAN ID. After Power ON my Coordinator, it will see the same PAN ID and then i create different PAN ID. But my End device doesn't know that it's real parent PAN ID has changed. So After power ON the End device, it will join to other Coordinator instead of My coordinator. 

    How can i rid off this Scenario

  • If you assign a fixed and the same PANID to all of your coordinators, you need to avoid starting them under radio coverage. 

  • No, i am talking about other 's Coordinator,which is not mine.. in the radio coverge

  • You make me confused. You mean you have a ZED joins a ZC with PANID (0x1234 for example) in the beginning. Then, you turn of this ZC and find there is another ZC with the same PANID in the radio range? Do you really have this experience? In ZStack implementation, ZC will scan current environment to make sure its PANID is not conflict with others. I doubt why you have this situation.

  • Let me clear, i am having one event, where i need to show a demo on zigbee. There will be different Coordinator's in the radio coverage.. Though i set a PANID for coordinator nd Enddevice,while Starting the network, if My coordinator seen that PAN ID,which i told it to start a network, but fails to do that, because there is a coordinator, which is having the same PAN ID. So my Coordinator starts with new PAN ID. After that my END device power ON,it will join to other's coordinator,right? which matches the same PAN ID.Hope now you understand the scenario

  • Is this a real case or just your worry? If this is a read case already, why don't you change your coordinator and end device to another PANID?

  • Mr.Yikai, I though the method to join particular parent. Suppose i am having two coordinator, my Intention is to join either two of them, it should not join to other, i am not enabling the NV_RESTORE. Because If he lost it's parent. It won't join to other Coordinator. But i want to join with my another Coordinator. 

      So, i will hardcode the MAC Address in the End device. After joining to any Coordinator, it will request for MAC address of it's current parent. Then it should compare with it's list. If it is not founding in the list, it should come out of that network and it should search for other network, till he finds his real parent.

    I found problem without enabling the NV_RESTORE, if Coordinator power off, it is sending beacon request though other Coordinator is there, why it is not joining to that Coordinator.

    This is very urgent, so please can you suggest me.

  • I would suggest you to SW restart the device if the device detects itself under orphan status.

  • That only i don't want to do. The device should be handle by non-technical person(User or Consumer). They might not know when the device goes orphan. So in the software itself i should be able to join the other parent. If i am handling this device means, i will sw restart the device. For that scenario only i asked a suggestion from Experts like you.

    Again let me clear the question. My End device should search his real parent(IEEE is hard coded in End device). Any way it will join to any network which is in the range, after joining it, i will request a MAC address, if it is not found in the list. End device itself should leave that network and start to search other network till it get real parent.

    I hope this you have done in your experience, i request to suggest me also. 

  • When end device becomes orphan, you can have the notification in ZED event loop. So, you can restart it automaticaaly without people to restart device. That is what I mean SW reset. Donyou allow to restart ZED?

  • 1)Can you tell me how to reset the device automatically, if it is in orphan state. 

    2)And If End device want to Leave the network, what should it do? I

  • 1)Can you tell me how to reset the device automatically, if it is in orphan state. 

    2)And If End device want to Leave the network, what should it do? I mean what should i do?

  • 1. you can use SystemResetSoft API.

    2. You can use ZDP_MgmtLeaveReq API.

  • 1. If there is one Coordinator and Multiple router's, will router decide the shortest path to Connect the network to other router or may be Coordinator, if Coordinator is near compare with the other router.

    2. How can connect  End Device in a start network to router.

  • 1. If there is one Coordinator and Multiple router's, will router decide the shortest path to Connect the network to other router or may be Coordinator, if Coordinator is near compare with the other router.

    2. How can connect  End Device in a start network to router.Will End Device also find shortest path for parent Node.

  • You can refer to Chapter 5.  Routing in Z-Stack Developer's Guide.pdf

  • 1) So ZStack does the job of Mesh and Star topology??

    2) If End Device is connected to Coordinator through 2 or 3 router, and wants to send a data to coordinator. how can it send? if i give the destination Address as 0x0000 means, it will send to Coordinator through router? or i need to send from router to router?

    3)How will coordinator know the short Address of End device which is connected with 2 or 3 router? In order to send a data to it. Sorry to ask this silly questions, because i worked with one coordinator and different End Device, not router.

  • 1. Yes, ZStack does the job.

    2. all you need to do is put 0x0000 as short address and zstack does the job.

    3. When ZED joins zigbee network, it will broadcast an end node announcement and you can keep its short address then.

  • Since End device is not in the range of Coordinator, then i how can i keep the short address of End device? Since router is in the range? So router can store, how about Coordinator?

  • Since end node announcement is a broadcast message, it will reach all routers and coordinator in radio coverage.

  • 1) You mean, If the structure is like this Coordinator->Router1->Router2->Router3->End Device. After End Device is joined to Router3, it will make an End node announcement, SInce Router3 is in the radio Coverage it will get an announcement in Device_Annouce. At the same time it will come to all Router's and Coordinator which is connected to this network.

    2)One last query, Say for example End Device is joined to Coordinator. After that i moved the End Device out of Radio Coverage. Then i placed Router in between the Coordinator and End Device. Whether the Short Address of the End Device will change or remain same. I am working on custom, where no LCD,if it is there, i might be check on it.

  • 1. Yes.

    2. The shot address will remain the same.