[JN5189] Permit join not happening on ZigBee routers connected tp JN5189 coordinator

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

[JN5189] Permit join not happening on ZigBee routers connected tp JN5189 coordinator

1,769 Views
devaiah
Contributor II

We are unable to add a new ZigBee end device via a router when using JN5189 as the coordinator.

1. The coordinator is sending a beacon response with the 'association permit' flag set to true  2.  The router node is receiving the beacons.

3. Router is relaying the beacon to the end node with an 'association permit' flag set to false instead of true.

Hence, we are unable to provide the end node via a router.

Is there any configuration setting that needs to be enabled on the coordinator?

 

Kindly find the attached Wireshark logs.

 

- Devaiah

 

Labels (1)
  • JN

0 Kudos
6 Replies

1,735 Views
EduardoZamora
NXP TechSupport
NXP TechSupport

Hello Devaiah,

Could you please clarify which command are you using for "association permit"?

Also, a diagram of your network/topology or failing section, and a sniffer log of the specific devices involved in this failure would be very helpful.

Please, try the Control Bridge Application Note (JN-AN-1247); this AN provides a means of controlling Zigbee devices via serial link and a Graphical User Interface, which simulates a host, to operate the Zigbee network. By this method you can do a quick test for "permit joining" to your router.

You can find more information about the Zigbee Stack inside the JN5189 SDK folder > docs > wireless > Zigbee.

Regards,
Eduardo.

1,693 Views
devaiah
Contributor II

Thank you Eduarado, Appreciate your prompt and timely response!!

The permit join is working now through routers as well. The problem was the address issued in the permit join command, target address was 0x0000 instead of a broadcast address 0xFFFC. 

There is one problem that I have observed though, 'Device Announcement' packet for nodes added to routers doesn't always reach the coordinator because of which we are unable to know if any new node is added to the network. 

Could you please let us know the exact stack event which notifies the new device addition event when a node is added to an another router in the network? 

Also, we could see 'device update' packet with the short address in wireshark capture which the router sends to the coordinator but somehow we are unable to capture this stack event at the application layer.

0 Kudos

1,676 Views
EduardoZamora
NXP TechSupport
NXP TechSupport

Hi,

It is good to know permit join is working.

Regarding to the stack, source code for our Zigbee stack is not publicly available. Modifications of the available Zigbee stack is limited to the files and code outside pre-compiled, encrypted libraries. I apologize for any inconvenience this may cause you.

Regards,
Eduardo.

0 Kudos

1,634 Views
devaiah
Contributor II

Thank you for the response!

But one question I have is isn't the Coordinator supposed to get the 'Device Announcement' from the ZigBee node even when it gets added to through another router in the network? From our observation, if the newly added device is quite far from the coordinator then we aren't receiving the 'Device Announcement' from the node most of the time. Could, you please let us know if there is anything we missing here? Also, is there any other alternate way for the coordinator to know when a device gets added to the network through a router?

 

Regards,

Devaiah

=

0 Kudos

1,622 Views
EduardoZamora
NXP TechSupport
NXP TechSupport

Hi,

Just to confirm, are you using an example project from the SDK or an Application Note as base for your application?

Also, could you please help us with more details about the method you are using to verify receipt of the "Device Announcement" message on the Coordinator? Are you trying to catch this event or packet with a sniffer o are you doing this in your code/application?

Regards,
Eduardo.

0 Kudos

1,290 Views
devaiah
Contributor II
We are using the IoT control bridge application. And we are unable to receive the Device announcement in the application itself. This very intermittent though.
0 Kudos