Z-stack binary calls afDataConfirm with rubbish transID when tx message is fragmented

Hi all,

My application relies on transID in the AF_DATA_CONFIRM_CMD event.  Application works flawlessly when my tx data is transmitted as one single packet (no fragmentation), but z-stack binary gives rubbish transID as soon as the data is fragmented.

Just to clarify, when z-stack gave the rubbish transID, it still managed to send out all parts of the fragmented data and the destination APS acked all the fragments.  I think z-stack successfully processed the APS acks because it called afDataConfirm with a success status.

When all the APS acks have been received, this is the code path z-stack takes (I'm using Router54xx.lib):

1. nwk_data_ind_processing (binary blob)
2. NLDE_DataIndication (binary blob)
3. apsProcessAck (binary blob)
4. APSF_ProcessAck (binary blob)
5. afDataConfirm (gets called with rubbish transID)

Unfortunately, it goes through a few functions in the binary blob and it is difficult to pin point exactly where the rubbish transID is introduced.

Can anyone confirm that this is indeed a z-stack binary blob issue?

Does anyone know of a workaround?

Thanks in advance.