Home/Support/Support Forum/network ACK failure in API response
New and improved user forum site going live on 12/6 (All users will need to reset their password when the new forum is active)

network ACK failure in API response

0 votes
while trying to communicate with a router node in api mode the controller returns the status with 0x21 corresponding to ntwrk ack failure...can any one shed some light on this..?
thanks in advance
asked Aug 27, 2014 in IEEE 802.15.4 by sarathtv2 New to the Community (2 points)

Please log in or register to answer this question.

1 Answer

0 votes
What this means is that one of the ACKs within the Zigbee protocol failed to indicate that the packet was received. In this case, it is the Network ACK that failed. unless you are using Application level Acks and have received the corresponding ACK, I would suggest re-transmitting the packet.
answered Aug 27, 2014 by mvut Veteran of the Digi Community (15,515 points)
What if there is no packet to re-transmit?

I'm receiving 0x21 = Network ACK Failure when I leave the network (by changing the EPID). But I'm not sending anything before changing the EPID so I'm not sure why I'm receiving this.
If you are using API mode, then you had to had provided a frame for it to transmit.  It is that packet that you would need to re-transmit.