packet handling

[snoop]

As I am getting further into my star network deployment, I am seeing that it is harder to differentiate what packets go to what responses. For example, when I send a packet out and listen for an ACK, many other packets are coming in at the same time. I want to make sure the receiver got it or otherwise I would resend it. I do not understand how to act on another packet coming in (lets say its a command to turn on an LED) while not leaving that for loop checking for the ACK.  I have yet to see an example online that deals with this issue.  Any direction would be of great help.

[Andrew Rapp]

It would help if you could provide some code or psuedo-code. You can use the frame id in an ACK response for correlation

On Fri, May 18, 2012 at 10:11 AM, snoop <alexande...@gmail.com> wrote:

As I am getting further into my star network deployment, I am seeing that it is harder to differentiate what packets go to what responses. For example, when I send a packet out and listen for an ACK, many other packets are coming in at the same time. I want to make sure the receiver got it or otherwise I would resend it. I do not understand how to act on another packet coming in (lets say its a command to turn on an LED) while not leaving that for loop checking for the ACK.  I have yet to see an example online that deals with this issue.  Any direction would be of great help.

--
You received this message because you are subscribed to the Google Groups "xbee-api" group.
To view this discussion on the web visit https://groups.google.com/d/msg/xbee-api/-/KLAPKepD4LgJ.
To post to this group, send email to xbee...@googlegroups.com.
To unsubscribe from this group, send email to xbee-api+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/xbee-api?hl=en.