ZIGBEE association problem

[Hardy Bismark]

HI,

I'm using the zigbee CLI example as coordinator and have another CLI device for reference as router. With my sniffer I can log the association sequence with the cli router and everything works fine. But with my device under development (not using the nRF-IEEE- 802.15.4-radio-driver but another 3rd party radio driver) everything works until the coordinator sends the association response, which I send an ACK within 1ms but the coordinator keeps sending the association response. The ACK I send is shown in the sniffer, and has the right sequence number. Could there be any reason why the coordinator doesn't receive the ACK? I'm using DEBUG_TRACE in the coordinator and since the dump tools are no longer there, I manual looked to the dump data and I can see the ACK from the association request, the association response, but not the ACK from the association response. The attached pictures show the sniffer log from the failing association and the good one from the reference device.

Do you have any idea why the ACK might not be received?

BR, Hardy

[Edvin]

Hello Hardy,

 

But with my device under development (not using the nRF-IEEE- 802.15.4-radio-driver but another 3rd party radio driver)

 So is this device under development an nRF? Why is it not using the radio driver from the SDK? Is it an option to test using the nRF-IEEE driver if it is an nRF device? If only for debugging purposes, to check whether the issue is radio driver related or application level related?

And in case I need to run this by our zigbee team, can you please upload the .pcapng sniffer trace here? If you need to capture a new sniffer trace because the old one isn't saved, can you please write a short description of the relevant packets?

Best regards,

Edvin