Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No packet ACK on Coordinator #40

Closed
garvamel opened this issue Dec 1, 2016 · 1 comment
Closed

No packet ACK on Coordinator #40

garvamel opened this issue Dec 1, 2016 · 1 comment

Comments

@garvamel
Copy link

garvamel commented Dec 1, 2016

Hello!
I'm connecting 2 Xbees with the examples Series2_Rx_Nss and Series2_Tx. Communication is working great, but I never get a positive ACK on the coordinator. On the end device, the delivery status returns "succesful". The relevant excerpt from the Series2_Rx example is:

      // got something
           
      if (xbee.getResponse().getApiId() == ZB_RX_RESPONSE) {
        // got a zb rx packet
        
        // now fill our zb rx class
        xbee.getResponse().getZBRxResponse(rx);
      
        nss.println("Got an rx packet!");
            
        if (rx.getOption() == ZB_PACKET_ACKNOWLEDGED) {
            // the sender got an ACK
            nss.println("Sender got and ACK");
        } else {
          nss.println("Sender didn't get an ACK");
        }

Which always prints "Sender didn't get an ACK". Any insight on this is much appreciated.

Thank you all in advance!

@garvamel
Copy link
Author

garvamel commented Dec 1, 2016

I'm an idiot for posting right before finding my mistake. The ACK validation had to be done against 0x41 and not 0x01 (ZB_PACKET_ACKNOWLEDGED). Because the message came from an End Device directly. Closed!

@garvamel garvamel closed this as completed Dec 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant