Thread: CoAP Client

The Thread CoAP Client sample demonstrates controlling light resources of other nodes within an OpenThread network. To show this interaction, the sample requires a server sample that is compatible with the OpenThread network and has a light resource available. The recommended server sample referenced on this page is Thread: CoAP Server.

This sample supports optional Multiprotocol Bluetooth LE extension and Minimal Thread Device variant, which can be turned on or off. See Snippets for details.

Requirements

The sample supports the following development kits:

Hardware platforms	PCA	Board name	Build target
nRF5340 DK	PCA10095	nrf5340dk_nrf5340	nrf5340dk_nrf5340_cpuapp_ns nrf5340dk_nrf5340_cpuapp
nRF52840 DK	PCA10056	nrf52840dk_nrf52840	nrf52840dk_nrf52840
nRF21540 DK	PCA10112	nrf21540dk_nrf52840	nrf21540dk_nrf52840

You can use one or more of the development kits listed above as the Thread CoAP Client. You also need one or more compatible development kits programmed with the Thread: CoAP Server sample.

When built for an _ns build target, the sample is configured to compile and run as a non-secure application with Cortex-M Security Extensions enabled. Therefore, it automatically includes Trusted Firmware-M that prepares the required peripherals and secure services to be available for the application.

Multiprotocol extension requirements

If you enable the Multiprotocol Bluetooth LE extension, make sure you have a phone with the nRF Toolbox application installed or an additional development kit programmed with Bluetooth: Central UART sample.

Note

The testing instructions refer to nRF Toolbox, but similar applications can be used as well, for example nRF Connect for Mobile.

Overview

This sample demonstrates how to access resources available on a Thread server node. After the Thread network is established, the client node can control the state of LED 4 on server nodes. It can turn on the LED either on every server node in the network with a multicast message, or on a single specific server node that is paired with the client node.

The following CoAP resources are accessed on the server side:

• /light - Used to control LED 4.

• /provisioning - Used to perform provisioning.

This sample uses Zephyr CoAP API for communication, which is the preferred API to use for new CoAP applications. For example usage of the native Thread CoAP API, see the Thread: CoAP Server sample.

Multiprotocol Bluetooth LE extension

This optional extension demonstrates the OpenThread stack and SoftDevice Controller working concurrently. It uses the Nordic UART Service (NUS) library to control the LED states over Bluetooth® LE in a Thread network. For more information about the multiprotocol feature, see Multiprotocol support.

User interface

The following LED and buttons of the client development kit are used by this sample:

LED 1:

On when the OpenThread connection is established.

Button 1:

Send a unicast LIGHT_TOGGLE message to the /light resource on a paired device. If no device is paired with the specific client node, pressing the button has no effect.

Button 2:

Send a multicast LIGHT_ON or LIGHT_OFF message (alternatively) to the /light resource. Sending this multicast message instead of LIGHT_TOGGLE allows to synchronize the state of the LEDs on several server nodes.

Button 4:

Send a multicast pairing request to the /provisioning resource.

Minimal Thread Device assignments

When the device is working as Minimal Thread Device (MTD), the following LED and Button assignments are also available:

LED 3:

The mode the device is working in:

• On when in the Minimal End Device (MED) mode.

• Off when in the Sleepy End Device (SED) mode.

Button 3:

Toggle the power consumption between SED and MED.

For more information, see Device type options in the Thread user guide.

Multiprotocol Bluetooth LE extension assignments

LED 2:

On when Bluetooth LE connection is established.

UART command assignments:

The following command assignments are configured and used in nRF Toolbox when Testing multiprotocol Bluetooth LE extension:

• u - Send a unicast CoAP message over Thread (the same operation as Button 1).

• m - Send a multicast CoAP message over Thread (the same operation as Button 2).

• p - Send a pairing request as CoAP message over Thread (the same operation as Button 4).

Configuration

See Configuring and building an application for information about how to permanently or temporarily change the configuration.

Snippets

The sample provides predefined Snippets for typical use cases, and to activate sample extensions. You can find the snippets in the snippets directory of the sample.

Specify the corresponding snippet names in the SNIPPET option when building with CMake, or as a -S argument when using west. For more information about using snippets, see Using Snippets in the Zephyr documentation.

The following snippets are available:

• debug - Enables debugging the Thread sample by enabling __ASSERT() statements globally.

• mtd - Enables the Minimal Thread Device variant.

• logging - Enables logging using RTT. For additional options, refer to RTT logging.

• multiprotocol_ble - Enables the Multiprotocol Bluetooth LE extension.

FEM support

You can add support for the nRF21540 front-end module to this sample by using one of the following options, depending on your hardware:

• Build the sample for one board that contains the nRF21540 FEM, such as nrf21540dk_nrf52840.

• Manually create a devicetree overlay file that describes how FEM is connected to the nRF5 SoC in your device. See Set devicetree overlays for different ways of adding the overlay file.

• Provide nRF21540 FEM capabilities by using a shield, for example the nRF21540 EK shield that is available in the nRF Connect SDK. In this case, build the project for a board connected to the shield you are using with an appropriate variable included in the build command, for example SHIELD=nrf21540ek. This variable instructs the build system to append the appropriate devicetree overlay file.

  nRF Connect for VS CodeCommand line

  To build the sample in the nRF Connect for VS Code IDE for an nRF52840 DK with the nRF21540 EK attached, add the shield variable in the build configuration’s Extra CMake arguments and rebuild the build configuration. For example: -DSHIELD=nrf21540ek.

  See nRF Connect for VS Code extension pack documentation for more information.

  See Programming nRF21540 EK for information about how to program when you are using a board with a network core, for example nRF5340 DK.

Each of these options adds the description of the nRF21540 FEM to the devicetree. See Working with RF front-end modules for more information about FEM in the nRF Connect SDK.

To add support for other front-end modules, add the respective devicetree file entries to the board devicetree file or the devicetree overlay file.

Building and running

Make sure to enable the OpenThread stack before building and testing this sample. See Thread for more information.

This sample can be found under samples/openthread/coap_client in the nRF Connect SDK folder structure.

When built as firmware image for the _ns build target, the sample has Cortex-M Security Extensions (CMSE) enabled and separates the firmware between Non-Secure Processing Environment (NSPE) and Secure Processing Environment (SPE). Because of this, it automatically includes the Trusted Firmware-M (TF-M). To read more about CMSE, see Processing environments.

To build the sample with Visual Studio Code, follow the steps listed on the How to build an application page in the nRF Connect for VS Code extension documentation. See Configuring and building an application for other building scenarios, Programming an application for programming steps, and Testing and optimization for general information about testing and debugging in the nRF Connect SDK.

Testing

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

1. Program at least one development kit with Thread: CoAP Server and reset it.

2. Turn on the CoAP Client and at least one CoAP Server. They will create the Thread network.

   Note

   It may take up to 15 seconds for nodes to establish the network. When the sample application is ready, the LED 1 starts blinking.

3. Press Button 2 on a client node to control LED 4 on all server nodes.

4. Pair a client with a server by completing the following steps:

   1. Press Button 4 on a server node to enable pairing.

   2. Press Button 4 on a client node to pair it with the server node in the pairing mode.

5. Press Button 1 on the client node to control the LED 4 on the paired server node.

Testing Minimal Thread Device

After building the MTD variant of this sample and programming it, the device starts in the SED mode with LED 3 off. This means that the radio is disabled when idle and the serial console is not working to decrease the power consumption. You can switch to the MED mode at any moment during the standard testing procedure.

To toggle MED, press Button 3 on the client node. LED 3 turns on to indicate the switch to the MED mode. At this point, the radio is enabled when it is idle and the serial console is operating.

Pressing Button 3 again will switch the mode back to SED. Switching between SED and MED modes does not affect the standard testing procedure, but terminal logs are not available in the SED mode.

Testing multiprotocol Bluetooth LE extension

To test the multiprotocol Bluetooth LE extension, you can use nRF Toolbox or the Bluetooth: Central UART sample. The steps below assume nRF Toolbox as the Bluetooth tester.

First, you need to set up nRF Toolbox as follows:

1. Tap UART to open the UART application in nRF Toolbox.

   

   UART application in nRF Toolbox

2. Tap the EDIT button in the top right corner of the application to configure the UART commands. The button configuration window appears.

3. Create the active application buttons by completing the following steps:

   1. Bind the top left button to the u command, with EOL set to LF and an icon of your choice. For this testing procedure, the > icon is used.

   2. Bind the top middle button to the m command, with EOL set to LF and an icon of your choice. For this testing procedure, the play button icon is used.

   3. Bind the top right button to the p command, with EOL set to LF and an icon of your choice. For this testing procedure, the settings gear icon is used.

      

      Configuring buttons in the UART application of nRF Toolbox

4. Tap the DONE button in the top right corner of the application.

5. Tap CONNECT and select the NUS_CoAP_client device from the list to connect to the device.

   

   The UART application of nRF Toolbox after establishing the connection

   Note

   Observe that LED 2 on your CoAP Multiprotocol Client node lights up, which indicates that the Bluetooth connection is established.

When you have set up nRF Toolbox, complete the following steps after the standard Testing procedure:

1. In nRF Toolbox, tap the middle button to control LED 4 on all CoAP server nodes.

2. To pair a client with a server, complete the following steps:

   1. Press Button 4 on a server node to enable pairing.

   2. In nRF Toolbox, tap the right button to pair the two nodes.

3. In nRF Toolbox, tap the left button to control LED 4 on the paired server node.

Sample output

You can observe the sample logging output with a terminal emulator that supports VT100/ANSI escape characters (for example, nRF Connect Serial Terminal). See Testing and optimization for the required settings and steps.

Dependencies

This sample uses the following nRF Connect SDK libraries:

• DK Buttons and LEDs

• CoAP utils

In addition, it uses the following Zephyr libraries:

• CoAP

  • include/net/coap.h

• Logging:

  • include/logging/log.h

• Kernel Services:

  • include/kernel.h

The following dependencies are added by the optional multiprotocol Bluetooth LE extension:

• SoftDevice Controller

• Nordic UART Service (NUS)

• Zephyr’s Bluetooth APIs:

  • include/bluetooth/bluetooth.h

  • include/bluetooth/gatt.h

  • include/bluetooth/hci.h

  • include/bluetooth/uuid.h

In addition, it uses the following secure firmware component:

• Trusted Firmware-M