This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

What distinguishes an ACK packet on-air from a regular packet?

I would like to implement a simple wireless sensor network, using Enhanced Shockburst with Auto-ACK. The idea is that there will be many sensor nodes (SNs) reporting to one master node (MN). The MN will listen on address P0 (say 0x0011223344) and all SNs will transmit to this address on an intermittent, periodic basis.

Assume I have auto-ack enabled everywhere.

  1. Node SN0 transmits a packet with PID=1, it begins listening on P0 for an ACK from MN.
  2. Before the ACK can be sent, a second node SN1 transmits a packet with PID=1 also.
  3. Since SN0 is listening on P0 while SN1 is transmitting on P0, will SN0 mistakenly identify SN1's data packet as an ack from MN?

As far as I can tell, for the same PID, there is no difference between a regular data packet and an ack-with-payload: I am assuming that ACKs are always sent with the NO_ACK bit of the PCF set to 1, and that a PTX detects a valid ack if ((ack_pid == last_tx_pid) && (ack_nak == 0)) ???

If this is the case, then I can assume that the answer to my question above is "no", but what about this:

  1. Node SN0 transmits a packet with PID=1, it begins listening on P0 for an ACK from MN.
  2. Before the ACK can be sent, a second node SN1 transmits a packet with PID=1 also, and listens
  3. MN sends ACK on P0 with PID=1.
  4. Presumably both SN0 and SN1 will interpret this as a valid ACK, even though it was meant for only one of them?

This would seem to make sense; I am happy to burn some payload bytes to identify individual transmitters, I'd just like to verify that my assumptions are correct.

Parents
  • Hi,

    You will get collisions in this scenario. It is not recommended to have several devices using the same pipe (w/ACKing) communicating with one host. An ACK payload is just a normal payload with no data. This will then include such things as PID/Addr/CRC etc. Note that you cannot read out the PID values from the radio. If a valid packet has been received, you will only get the actual payload.

    You will have certain corner cases where Device#1 can get interference from Device#x. If you were to build up a system like this, then you will have to time-slice the transmission from each device to make sure that they do not collide, which is a complicated thing to implement properly.

    The easiest way is to open more pipes, and have each device communicate using different RF addresses.

    -H

Reply
  • Hi,

    You will get collisions in this scenario. It is not recommended to have several devices using the same pipe (w/ACKing) communicating with one host. An ACK payload is just a normal payload with no data. This will then include such things as PID/Addr/CRC etc. Note that you cannot read out the PID values from the radio. If a valid packet has been received, you will only get the actual payload.

    You will have certain corner cases where Device#1 can get interference from Device#x. If you were to build up a system like this, then you will have to time-slice the transmission from each device to make sure that they do not collide, which is a complicated thing to implement properly.

    The easiest way is to open more pipes, and have each device communicate using different RF addresses.

    -H

Children
No Data
Related