Device pairing

This project requires a host running the Host pairing example as counterpart.

The application sends packets continuously. If a packet transmission fails (either times out or encryption failed), the Device will attempt pairing to a Host by sending a pairing request, consisting of an "address request" and a "Host ID" request.

If the Device is paired to a Host, pairing data will be stored in non volatile memory.

Before adding a packet to the TX queue, the contents of the GPIO Port BUTTONS is copied to the first payload byte (byte 0). When an ACK is received, the contents of the first payload byte of the ACK are output on GPIO Port LEDS.

The application alternates between sending the packets encrypted through the pairing library or directly as plaintext using pipe UNENCRYPTED_DATA_PIPE.

The name of the example is gzp_device_dynamic_pairing_pca10028. If you are not using the Keil Pack Installer, you can find the source code and project file of the example in the following folder: <InstallFolder>\Nordic\nrf51\examples\properitary_rf\gzll\gzp_dynamic_pairing

Host pairing

This project requires a device running the Device pairing example as counterpart.

The application listens for packets continuously, monitoring for pairing requests as well as normal user data.

The Gazell pairing library uses pipe 0 and pipe 1 for encrypted communication. The application will grant any request for a Host ID, thus granting pairing. Unencrypted packets can be received on pipe 2.

When DATA is received, the contents of the first payload byte of the are output on GPIO Port LEDS.

The name of the example for PCA10028 is gzp_host_dynamic_pairing_pca10028, and for PCA10031 it is gzp_host_dynamic_pairing_pca10031. If you are not using the Keil Pack Installer, you can find the source code and project file of the example in the following folder: <InstallFolder>\Nordic\nrf51\examples\properitary_rf\gzll\gzp_dynamic_pairing