LAUNCHXL-CC26X2R1: Can not get end device report messages

I would suggest you to use sniffer to check what exactly happens over the air.

Thanks for your quick reply. I did that, but I will do it again and send the logs here.

But can you please check my log file and tell me if I did something wrong, or missed doing something?

It's difficult to check Ztool log to find the issue. Please do the test again and attach both Ztool log and sniffer log so we can try to check what exactly happens.

Ok, Thank you. I will send them soon.

I had checked your Z_2D00_Tool.rtf. I suspect you use wrong endien order in binding request SrcAddress: 0x3C6A2CFFFED14603. You can try to reverse endien oder of SrcAddress to see if it works.

Here are Z-Tool and Wireshark log files./cfs-file/__key/communityserver-discussions-components-files/158/4784.logs.zip

YiKai Chen said:

I had checked your Z_2D00_Tool.rtf. I suspect you use wrong endien order in binding request SrcAddress: 0x3C6A2CFFFED14603. You can try to reverse endien oder of SrcAddress to see if it works.

I have seen your reply just right now, I will try the reverse order and inform you about the result.

In your sniffer log, there is no binding request sent over the air. When you test again with reverse order of SrcAddress, please also use sniffer to check it. If you still cannot make it work, please attach new sniffer log.

YiKai Chen said:

In your sniffer log, there is no binding request sent over the air. When you test again with reverse order of SrcAddress, please also use sniffer to check it. If you still cannot make it work, please attach new sniffer log.

John Rock said:

I checked the reverse order, no change. I don't think that the SrcAddress is in the wrong endian order. 
/resized-image/__size/320x240/__key/communityserver-discussions-components-files/158/hex_2D00_to_2D00_dec.JPG 
/resized-image/__size/320x240/__key/communityserver-discussions-components-files/158/ztool_2D00_bind.JPG

Maybe the BindAddr is in the wrong Indian order? I will check this and inform you.

No change! Can you please show me an example of a bind request?

YiKai Chen said:

In your sniffer log, there is no binding request sent over the air. When you test again with reverse order of SrcAddress, please also use sniffer to check it. If you still cannot make it work, please attach new sniffer log.

I checked all of the possible orders! /cfs-file/__key/communityserver-discussions-components-files/158/orders.zip

YiKai Chen said:

In your sniffer log, there is no binding request sent over the air. When you test again with reverse order of SrcAddress, please also use sniffer to check it. If you still cannot make it work, please attach new sniffer log.

These logs (/cfs-file/__key/communityserver-discussions-components-files/158/4784.logs.zip) have been generated with this setup (https://sunmaysky.blogspot.com/2015/10/how-to-do-device-binding-from-ti-ztool.html).

Hi Rayn. Thanks for your reply.
Why should we see an over-the-air Bind Request and Response? I have just one coordinator and an end device. So as I know, the parent of the end device is up to handling the bind requests, and here is the coordinator itself!

Also, I have set up the sniffer using this https://software-dl.ti.com/simplelink/esd/simplelink_cc13x2_26x2_sdk/3.20.00.68/exports/docs/zigbee/html/zigbee/packet_sniffer.html, but I'm going to double-check it!