This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Gazell pairing how to add payload to the acknowledgement

Hi I did not quit yet understand the Gazell Pairing library.

If an encrypted message is send, how do I add some payload to the acknowledgement. And how will I be able to read this payload from the acknowledgement?

What is the maximum size of the data that can be send at once to the host, and what is the maximum payload I can put in the acknowledgement?

If the two devices are paired does this mean they can send encrypted and unencrypted data to eachother without interference from a third device that isn't paired with the host but still broadcasting?

I already looked into the "gzp_dynamic_pairing" example but still these questions remains.

Parents
  • Hi,

    Q1: Unfortunately, when using the encrypted pipe 1 with GZP, it will consume the ACK payload for key exchange. You will not be able to use ACK_PAYLOAD when an encrypted pipe is in use with GZP, as it will flush the TXFIFO to ensure there's space in the FIFO for doing the key update.

    Q2: With Gazell you can send 32 bytes payload over-the-air, both in forward and reverse (ie: in the ACK-payload).

    Q3: Only one encrypted pipe is supported with GZP. This means that other devices connected to the same host must use an unencrypted RF pipe for communicating. If you have the same configuration on the third device, it will try to pair with the host, and it will not spam due to the pairing sequence (there's loads of delays in there) if it fails to pair up properly.

    Cheers, Håkon

Reply
  • Hi,

    Q1: Unfortunately, when using the encrypted pipe 1 with GZP, it will consume the ACK payload for key exchange. You will not be able to use ACK_PAYLOAD when an encrypted pipe is in use with GZP, as it will flush the TXFIFO to ensure there's space in the FIFO for doing the key update.

    Q2: With Gazell you can send 32 bytes payload over-the-air, both in forward and reverse (ie: in the ACK-payload).

    Q3: Only one encrypted pipe is supported with GZP. This means that other devices connected to the same host must use an unencrypted RF pipe for communicating. If you have the same configuration on the third device, it will try to pair with the host, and it will not spam due to the pairing sequence (there's loads of delays in there) if it fails to pair up properly.

    Cheers, Håkon

Children
No Data
Related