/fota_test

Primary LanguageC

Bluetooth: Peripheral LBS

The peripheral LBS sample demonstrates how to use the :ref:`lbs_readme`.

Requirements

The sample supports the following development kits:

.. table-from-sample-yaml::

The sample also requires a smartphone or tablet running a compatible application. The Testing instructions refer to `nRF Connect for Mobile`_, but you can also use other similar applications (for example, `nRF Blinky`_ or `nRF Toolbox`_).

Note

|thingy53_sample_note|

Overview

When connected, the sample sends the state of Button 1 on the development kit to the connected device, such as a phone or tablet. The mobile application on the device can display the received button state and control the state of LED 3 on the development kit.

You can also use this sample to control the color of the RGB LED on the nRF52840 Dongle or Thingy:53.

User interface

The user interface of the sample depends on the hardware platform you are using.

nRF52840 Dongle

Green LED:
Blinks, toggling on/off every second, when the main loop is running and the device is advertising.
RGB LED:

The RGB LED channels are used independently to display the following information:

  • Red - If Dongle is connected.
  • Green - If user set the LED using Nordic LED Button Service.
Button 1:
Send a notification with the button state: "pressed" or "released".

Thingy:53

RGB LED:

The RGB LED channels are used independently to display the following information:

  • Red - If the main loop is running (that is, the device is advertising). The LED blinks with a period of two seconds, duty cycle 50%.
  • Green - If the device is connected.
  • Blue - If user set the LED using Nordic LED Button Service.

For example, if Thingy:53 is connected over Bluetooth, the LED color toggles between green and yellow. The green LED channel is kept on and the red LED channel is blinking.

Button 1:
Send a notification with the button state: "pressed" or "released".

Development kits

LED 1:
Blinks when the main loop is running (that is, the device is advertising) with a period of two seconds, duty cycle 50%.
LED 2:
Lit when the development kit is connected.
LED 3:
Lit when the development kit is controlled remotely from the connected device.
Button 1:
Send a notification with the button state: "pressed" or "released".

Building and running

Minimal build

You can build the sample with a minimum configuration as a demonstration of how to reduce code size and RAM usage, using the -DCONF_FILE='prj_minimal.conf' flag in your build.

See :ref:`cmake_options` for instructions on how to add this option to your build. For example, when building on the command line, you can add the option as follows:

west build samples/bluetooth/peripheral_lbs -- -DCONF_FILE='prj_minimal.conf'

Testing

After programming the sample to your dongle or development kit, test it by performing the following steps:

  1. Start the `nRF Connect for Mobile`_ application on your smartphone or tablet.
  2. Power on the development kit or insert your dongle into the USB port.
  3. Connect to the device from the application. The device is advertising as Nordic_LBS. The services of the connected device are shown.
  4. In Nordic LED Button Service, enable notifications for the Button characteristic.
  5. Press Button 1 on the device.
  6. Observe that notifications with the following values are displayed:
    • Button released when Button 1 is released.
    • Button pressed when Button 1 is pressed.
  7. Write the following values to the LED characteristic in the Nordic LED Button Service. Depending on the hardware platform, this produces results described in the table.
Hardware platform Value Effect
Development kit OFF Switch the LED3 off.
ON Switch the LED3 on.
nRF52840 Dongle OFF Switch the green channel of the RGB LED off.
ON Switch the green channel of the RGB LED on.
Thingy:53 OFF Switch the blue channel of the RGB LED off.
ON Switch the blue channel of the RGB LED on.

Dependencies

This sample uses the following |NCS| libraries:

In addition, it uses the following Zephyr libraries:

The sample also uses the following secure firmware component: