Wireless MCUのトピックRe: jn5169 Zigbee Route reply

jn5169 Zigbee Route reply

hariprasad_anum — Thu, 20 Feb 2020 04:56:48 GMT

We have configured jn5169 zigbee as co-ordinator.

We have connected the same to multiple sensors including gas leak sensor. We notice that in some cases co-ordinator stops sending route reply to route request received from end node.

Why does co-ordinator not respond to route request ?

Can you point to route reply API in SDK ?

Is there any configuration that needs to be set in co-ordinator for sending route replies.

Re: jn5169 Zigbee Route reply

Sebastian_Del_Rio — Tue, 25 Feb 2020 18:44:31 GMT

Hi Hariprasad, I hope you're doing well!

Could you please let me know which Application Note are you using for your devices?

And is it possible for you to provide the full sniffer log in an attachment to your comment?

Best regards,

Sebastian

Re: jn5169 Zigbee Route reply

hariprasad_anum — Wed, 26 Feb 2020 10:29:15 GMT

Hi Sebastian,

Pls find attached sniffer log .

Re: jn5169 Zigbee Route reply

Sebastian_Del_Rio — Wed, 26 Feb 2020 17:14:52 GMT

Hi Hariprasad,

Thank you for providing the screen capture of the sniffer log. Is it possible for you to provide the sniffer log file itself as an attachment? Additional file formats can be attached to a reply using the advanced comment editor:

Also, could you please let me know which JN-AN are you using as a base to develop your application?

Best regards,

Sebastian

Re: jn5169 Zigbee Route reply

hariprasad_anum — Wed, 26 Feb 2020 17:28:35 GMT

Hello Sebastian,

Pls check attached log

Re: jn5169 Zigbee Route reply

Sebastian_Del_Rio — Tue, 03 Mar 2020 17:59:23 GMT

Hi Hariprasad,

If you're able to, could you please provide the link key to decrypt the ZigBee sniffer log you provided?

Best regards,

Sebastian

Re: jn5169 Zigbee Route reply

hariprasad_anum — Tue, 03 Mar 2020 18:08:07 GMT

Pls find sniffer log and its corresponding key

Network key: 26 73 1c 71 82 1f d8 fd 9e 8b 54 49 7a b7 90 55

Re: jn5169 Zigbee Route reply

Sebastian_Del_Rio — Mon, 09 Mar 2020 16:48:02 GMT

Hi Hariprasad,

I went through the sniffer log and found that there's a device with the short address 0x8D50 that doesn't seem to be receiving the Route Request commands from the coordinator, and its Route Request commands aren't reaching the coordinator either.

In the Link Status packets, after a certain point, the coordinator no longer reports the 0x8D50 device, while the latter still reports that the coordinator is in range.

Could you please check for possible physical obstructions and/or interference from other devices that could be causing your coordinator and router to be missing messages?

Best regards,

Sebastian

Re: jn5169 Zigbee Route reply

hariprasad_anum — Mon, 09 Mar 2020 17:05:51 GMT

Thanks Sebstian for feedback on the attached log.

There are no physical obstructions during the whole test setup and the gas leak sensor is also placed with in 5-10 meters of co-ordinator.

Any other reason that can cause the route drop ?

Re: jn5169 Zigbee Route reply

Sebastian_Del_Rio — Thu, 12 Mar 2020 17:53:38 GMT

Hi Hariprasad,

The Route Request seems to be happening because, for some reason, the devices are not finding each other.

Could you please try changing your network's channel? It seems like there's a lot of different networks on the channel you're using, and it could be causing communication issues between the devices.

Best regards,

Sebastian