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.

ZIGBEE_FRAGMENTATION bug? Wrong radius in reassembled message

Other Parts Discussed in Thread: Z-STACK

Hello everybody,

We are using Z-Stack Mesh 1.0.0.

It seems that the value of afIncomingMSGPacket_t.radius field is random for fragmented packet reassembled by APSF_ProcessEvent() task.

Details:

The message of 86 payload bytes is send unicast to the destination 1-hop apart by using AF_DataRequest() with AF_DEFAULT_RADIUS of 30. The message is correctly fragmented by the sender and reassembled by receiver, but the radius field is incorrect (sometimes 0, sometimes 2 etc.). The Other-The-Air capture with the sniffer shows radius field of the both fragment to be 30.

Any comments?

Best regards,

Edgar