![]() |
nRF5 SDK
v15.0.0
|
Choose documentation: | nRF5 SDK | S112 SoftDevice API | S132 SoftDevice API | S140 SoftDevice API | S212 SoftDevice API |
Important: Before you run this example, make sure to program the SoftDevice.
The BLE Running Speed and Cadence Collector application implements the Running Speed and Cadence Collector Role using the S13x SoftDevice.
The GAP role implemented is the Central role. The GATT role implemented is the Client role.
The Running Speed and Cadence Collector application implements the Collector role for the Running Speed and Cadence Profile. It scans peripheral devices, connects to the device advertising with Running Speed and Cadence Service UUID in its advertisement report, and discovers Running Speed and Cadence Service and Device Information Service. The device information is logged on the UART interface right after the service discovery. The application also configures the RSCS to start sending notifications of Running Speed and Cadence measurements. The received measurements are also logged on the UART interface.
The application includes two services from the Running Speed and Cadence profile:
You can find the source code and the project file of the example in the following folder: <InstallFolder>\examples\ble_central\ble_app_rscs_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. Running Speed and Cadence Sensor role) to this Running Speed and Cadence Collector application.
Test the BLE Running Speed and Cadence Collector Example application by performing the following steps: