• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 56 subscribers
  • Views 627 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

APS Acknowledge Response From a Fragmented Message in a SE Device

Kiwi
Prodigy 120 points

Hi,

In an SE system with ZStack 2.5.0 The ESP incorrectly replies with an APS Acknowledge (with an extended header) to a Fragmented message and the End device is expecting the extended header.

For the SE system the extended header should not be generated by the ESP and the End Device should expect an APS Acknowledge without the extended header.

How can we change the ZStack to respond with the correct APS Acknowledge without the extended header as required by Zigbee SE?

Thanks

  • 0
    TI__Genius 10650 points

    Hello Kiwi,

    I do not think the ESP is reponding incorrectly, for inter-pan messages, according to section 5.3.8 of the SE specification the apsMaxWindowSize = 1, that is there can be only one block of message sent over the air until an acknowledgement is recieved. So the end-device will wait for acknowledgment before transmitting next fragmented block. Also, according to ZigBee spec when acknowleding to a Fragmented message with an extended header, extended header should be present in the acknowledged frame as well.

    Also, the extended header for the APS should be set to zero in case of intra - PAN messages for the SE profile Appendix B.4. But in case of interpan message there is no recommendation on that but

    Please let me know if you have any questions.

    Regards,

     

  • 0 in reply to Suyash Jain
    Prodigy 120 points

    Thankyou for your response.

    I am just trying to relay the issue from our test lab. They won't budge as their golden units do not send the extended header.

    Referring to 5.3.8, Logically if the end device is waiting for an acknowledge before transmitting the next fragment there is NO need for the acknowledge to include the extended header (with the block number).

    Our test lab refers us to Zigbee Specification 053474r19 section 2.2.5.1.8. Simply put the acknowledge is not a fragmented transmission so does not require the extended header.

    Please can you specify exactly where in the Zigbee specification you fount the following: "according to ZigBee spec when acknowleding to a Fragmented message with an extended header, extended header should be present in the acknowledged frame as well'

    In section 2.2.5.2.2.1 It says that the PAS frame shall not be fragmented and the extended field shall not be present.

    Thanks,

  • 0 in reply to Kiwi
    TI__Genius 10650 points

    Hello Kiwi,

    I was looking at the r19 section 2.2.5.2.3.1 - Acknowledgement Frame APS Header Fields  - "In the frame control field, the frame type sub-field shall contain the value that indicates an acknowledgement frame, as shown in Table 2.20. The extended header present sub-field shall contain the same value as in the frame to which this frame is an acknowledgement. All other sub-fields shall be set appropriately according to the intended use of the acknowledgement frame."

    So for a frame with extended header the acknowledgment will be with extended header. Please let me know the response from the test house. Thanks

    Regards,

     

     

  • 0 in reply to Suyash Jain
    Prodigy 120 points

    Hi,

    Thanks for this I am still waiting for a response from our Test lab however I think no matter what they will say the golden units do not do it so we have to follow that.

    In the meantime can you tell me where in the code I code of the end device I could alter it to accept either type of response. i.e. with or without extended header.

    Thanks,