Strange Neighbourg table

[zigbee1]

We are currently maintaining a  Zigbee controller out of JN5169.
We are using the JN-SW-4170 SDK.
We have of course a good understanding of JN-AN-1216
Application Note: JN-AN-1216 ZigBee 3.0 IoT Control Bridge,

I'm using the LQI Management  Request ( APP_eZdpMgmtLqiRequest()  ) to query the neighbourg table of the Controler as well as the Routers.

I'm currently seen very strange behvaiour at the Controler side

Here after is an output of the Neighbourg query of the controller, which I don't understand !! How can the controler 0000 and an othet Router can be Sibling !!!

Node Node Relation Type Deepth LQI Rx-Idle
0000 56fb Child End Device 1 203 Rx-Off
0000 f8d7 Child End Device 1 154 Rx-Off
0000 50e0 Child Router 1 161 Rx-On
0000 cd45 Sibling Router 0 84 Rx-On
0000 5cbe Sibling Router 0 87 Rx-On
0000 ad66 Sibling Router 0 120 Rx-On
0000 50ad Sibling Router 0 77 Rx-On
0000 129a Sibling Router 0 84 Rx-On
0000 cdd5 Sibling Router 0 111 Rx-On

[mario_castaneda]

Hi @zigbee1,

I hope you are doing great.

I am not sure if I am following your question. 

What is the command that you are sending? the APP_eZdpMgmtLqiRequest, but what is the device that you are sending this command? to the coordinator? router?

Do you have the terminal logs and the sniffer log for this issue?

Regards,

Mario

[zigbee1]

Hello Mario,

hope you are doing well to.

yes indeed this is based on

case (E_SL_MSG_MANAGEMENT_LQI_REQUEST):
{
uint8 u8StartIndex;
u16TargetAddress = ZNC_RTN_U16 ( au8LinkRxBuffer, 0 );
u8StartIndex = au8LinkRxBuffer[2];
u8Status = APP_eZdpMgmtLqiRequest ( u16TargetAddress
u8StartIndex,
&u8SeqNum );
}

this occurred already by just queering the controller Neighbour table as you can see in the initial post,

NO I don't have any sniff as anyhow it won't help since the query is just asking for the Neighbour table of the Zigbee controler

The code is coming from the JN-AN-1216-ZigBee-3-0-IoT-ControlBridge

All code is based with the "ZigbeeNodeControlBridge"

[mario_castaneda · Accepted solution]

Hi,

I hope you are doing great.

It is ok that the coordinator and the router could be Sibling, because in the Zigbee network the coordinator is a router but it is the one that it has the Trust Center, in this case. 

Regards,

Mario

[zigbee1]

Hi Mario hope you are doing well.

Glad to see that is possible, however this doesn't help me in my drawing of a topology report.
As if a Controller and a or several routers are Sibling, what does that mean from a relationship standpoint ?

I'm quiet lost here , would appreciate NXP insight

[mario_castaneda]

Hi @zigbee1,

As you know the Zigbee protocol is based on the 802.15.4 Specification.

Please look at the next user guide https://www.nxp.com/docs/en/user-guide/JN-UG-3024.pdf

1.4.3 Mesh Topology

Regards,

Mario

[zigbee1]

Of course I know that documentation, but at any place they are documenting a Controler/Router Sibling relation - where there is no parent -, so please tell us how we should handle such relation in a Mesh network ?

[mario_castaneda]

Hi @zigbee1,

It depends on your Zigbee network, which is the feature of the mesh. The devices, in this case, routers and the coordinator, if they found out a direct connection, they will be neighbour and that is part of the stack.

Also, with the command that you are using you can move on the index value and you will get all the neighbour table for that device.

Regards,

Mario

[zigbee1]

Any update , thanks ?