Zigbee Stack 3.0 - sequence number not same

gokul_bhalodiya — Wed, 02 Nov 2022 14:23:55 GMT

Hello,

ZIGBEE STACK 3.0
JN5179 module

Below listed steps are getting followed for WRITE_REQUEST, DATA_CONFIRM, WRITE_RESPONSE:

1. WRITE_ATTRIBUTE_REQUEST:
JN Co-ordintor side, the data is sent in an Application Protocol Data Unit (APDU) instance, allocated using the PDUM function PDUM_hAPduAllocateAPduInstance() and then written to using PDUM_u16APduInstanceWriteNBO(), and then ZPS_eAplAfUnicastDataReq() function submits a request to send data to a remote node (unicast).
- In this case sequence number is passed with WRITE_ATTRIBUTE_REQUEST.

2. DATA_CONFIRM event:
After this stack-supplied callback function APP_vGenCallback() will handle the ZPS_EVENT_XXX (like ZPS_EVENT_APS_DATA_INDICATION, ZPS_EVENT_APS_DATA_CONFIRM, ZPS_EVENT_APS_DATA_ACK)
In this, sequence number u8SequenceNum will be received
- In this case sequence number is not same with WRITE_ATTRIBUTE_REQUEST's sequence number.

3. WRITE_ATTRIBUTES_RESPONSE
After this, E_ZCL_CBET_WRITE_ATTRIBUTES_RESPONSE event will be received through callback function.
- In this case sequence number is received which is same with WRITE_ATTRIBUTE_REQUEST's sequence number.

- I want to do retry for the event with non-zero status of ZPS_EVENT_APS_DATA_CONFIRM(Faied events)
- How can i verify that the ZPS_EVENT_APS_DATA_CONFIRM is of which WRITE_ATTRIBUTE_REQUEST as the ZPS_EVENT_APS_DATA_CONFIRM's sequence number is not matching with the the WRITE_ATTRIBUTE_REQUEST's sequence number?

Please guide for the same!!
Prompt response would be much appreciated.

Wireless MCUのトピックZigbee Stack 3.0 - sequence number not same

Zigbee Stack 3.0 - sequence number not same