nRF5 SDK v15.0.0
Experimental: Object Transfer Service client Example
This example requires one of the following SoftDevices: S132, S140

Important: Before you run this example, make sure to program the SoftDevice.

The Object Transfer Service (OTS) client application is a central role example that implements an Object Transfer Service (OTS) client.

When the application device connects to a peer, they establish L2CAP channel reserved for OTS.

Upon connection, the OTS Feature characteristic (0x2ABD) is also read. A typical output from the read looks like this on the UART:

Supported features on the connected Server:
    Read OP Code Supported.
    Append Additional Data to Objects Supported.
    Truncation of Objects Supported.
    Patching of Objects Supported.
    Abort OP Code Supported.

The OTS client will request to write an object. The request is done by writing to the Object Action Control Point (0x2AC5) over GATT. If the write is accepted by the server, the data will be transfered over the L2CAP channel established earlier. An event is triggered on the server side application when the write is complete.

The "object" in this example is simply the numbers from 0 to 255, repeated for the length of the object.


You can find the source code and the project file of the example in the following folder: <InstallFolder>\examples\ble_central\experimental\ble_app_ots_c

Button assignments: BSP BLE Button Assignments

The application uses the following UART settings:


Two boards are needed to perform this test:

Documentation feedback | Developer Zone | Subscribe | Updated