![]() |
nRF5 SDK
v15.3.0
|
Choose documentation: | nRF5 SDK | S112 SoftDevice API | S132 SoftDevice API | S140 SoftDevice API | S212 SoftDevice API | S312 SoftDevice API | S332 SoftDevice API | S340 SoftDevice API |
Important: Before you run this example, make sure to program the SoftDevice.
The BLE Heart Rate Collector application implements the Heart Rate Collector Role.
GAP role implemented is the Central role. GATT role implemented is the Client role.
The Heart Rate Collector application implements the Collector role for the Heart Rate Profile. It scans peripheral devices, connects to the device advertising with Heart Rate Service UUID in its advertisement report, and discovers and configures the Heart Rate Service to start sending Notifications of Heart Rate Measurement. The Heart Rate Measurement received is logged on UART interface. This application will also discover and configure Battery Service at the peer.
The application includes the two services in the Heart Rate profile:
This example demonstrates the use of Low Energy Secure Connections (LESC). The default cryptographic backend used for LESC is CC310 (when run on nRF52840) or Oberon (for other SoCs). To use micro-ecc instead, follow the steps in Enabling micro-ecc support in selected examples.
You can find the source code and the project file of the example in the following folder: <InstallFolder>\examples\ble_central\ble_app_hrs_c
Button assignments: BSP BLE Button Assignments
The application uses the following UART settings:
Two boards are needed to perform this test:
The application running on the Sensor board is intended to serve as a peer (i.e. Heart Rate Sensor role) to this Heart Rate Collector application.
Test the BLE Heart Rate Collector Example application by performing the following steps: