Bluetooth: Central HIDS

The Central HIDS sample demonstrates how to use the GATT Human Interface Device (HID) Service Client to interact with a HIDS server. Basically, the sample simulates a computer that connects to a mouse or a keyboard.

Overview

The sample scans available devices, searching for a HIDS server. If any HIDS server is found, the sample connects to it and discovers all characteristics.

If any input reports are detected, the sample subscribes to them to receive notifications. If any boot reports are detected, the behavior depends on if they are boot mouse reports or boot keyboard reports:

  • If a boot mouse report is detected, the sample subscribes to it.

  • If a boot keyboard report is detected, the sample subscribes to its input report, and the sample functionality of changing the CAPSLOCK LED is enabled (Button 1 and 3).

Requirements

User interface

Button 1:

Toggle the CAPSLOCK LED on the connected keyboard using Write without response. This function is available only if the connected keyboard is set to work in Boot Protocol Mode.

Button 2:

Switch between Boot Protocol Mode and Report Protocol Mode. This function is available only if the connected peer supports the Protocol Mode Characteristic.

Button 3:

Toggle the CAPSLOCK LED on the connected keyboard using Write with response. This function is available only if the connected HID has boot keyboard reports. It always writes CAPSLOCK information to the boot report, even if Report Protocol Mode is selected.

Building and Running

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

See Building and programming a sample application for information about how to build and program the application.

Testing

After programming the sample to your board, you can test it either by connecting to another board that is running the Bluetooth: Peripheral HIDS keyboard sample, or by using nRF Connect for Desktop that emulates a HIDS server.

Testing with another board

  1. Connect to the board that runs this sample with a terminal emulator (for example, PuTTY). See How to connect with PuTTY for the required settings.

  2. Reset the board.

  3. Program the other board with the Bluetooth: Peripheral HIDS keyboard sample and reset it.

  4. Wait until the HIDS keyboard is detected by the central. All detected descriptors are listed. In the terminal window, check for information similar to the following:

    HIDS is ready to work
    Subscribe to report id: 1
    Subscribe to boot keyboard report
    
  5. Press Button 1 and Button 2 one after another on the board that runs the keyboard sample and observe the notification values in the terminal window. See Bluetooth: Peripheral HIDS keyboard for the expected values:

    Notification, id: 1, size: 8, data: 0x0 0x0 0xb 0x0 0x0 0x0 0x0 0x0
    Notification, id: 1, size: 8, data: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
    
  6. Press Button 2 on the board that runs the Central HIDS sample and observe that the protocol mode is updated into boot mode:

    Setting protocol mode: BOOT
    
  7. Press Button 1 and Button 2 one after another on the board that runs the keyboard sample and observe the notification of the boot report values:

    Notification, keyboard boot, size: 8, data: 0x0 0x0 0xf 0x0 0x0 0x0 0x0 0x0
    Notification, keyboard boot, size: 8, data: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
    
  8. Press Button 1 and Button 3 one after another on the Central HIDS board and observe that LED 1 on the keyboard board changes its state. The following information is also displayed in the terminal window.

    If Button 1 was pressed:

    Caps lock send (val: 0x2)
    

    If Button 3 was pressed:

    Caps lock send using write with response (val: 0x2)
    Capslock write result: 0
    Received data (size: 1, data[0]: 0x2)
    

Testing with nRF Connect for Desktop

  1. Connect to the board that runs this sample with a terminal emulator (for example, PuTTY). See How to connect with PuTTY for the required settings.

  2. Reset the board.

  3. Start nRF Connect for Desktop and select the connected dongle that is used for communication.

  4. Go to the Server setup tab. Click the dongle configuration and select Load setup. Load the hids_keyboard.ncs file that is located under samples/bluetooth/central_hids in the nRF Connect SDK folder structure.

  5. Click Apply to device.

  6. Go to the Connection Map tab. Click the dongle configuration and select Advertising setup.

    The current version of nRF Connect cannot store the advertising setup, so it must be configured manually. See the following image for the required target configuration:

    Advertising setup for HIDS keyboard simulator

    Advertising setup for HIDS keyboard simulator

    Complete the following steps to configure the advertising setup:

    1. Delete the default Complete local name from Advertising data.

    2. Add a Custom AD type with AD type value set to 19 and Value set to 03c1. This is the GAP Appearance advertising data.

    3. Add a Custom AD type with AD type value set to 01 and Value set to 06. This is the AD data with “General Discoverable” and “BR/EDR not supported” flags set.

    4. Add a UUID 16 bit complete list with two comma-separated values: 1812 and 180F. These are the values for HIDS and BAS.

    5. Add a Complete local name of your choice to the Scan response data.

    6. Click Apply and Close.

  7. In the Adapter settings, choose Start advertising.

  8. Wait until the board that runs the Central HIDS sample connects. All detected descriptors are listed. Check for information similar to the following:

    HIDS is ready to work
    Subscribe in report id: 1
    Subscribe in boot keyboard report
    
  9. Explore the first record inside Human Interface Device (the one with six values). Change any of the values and note that the board logs the change.

  10. Press Button 2 on the board and observe that the Protocol Mode value changes from 01 to 00.

  11. Press Button 1 and Button 3 one after another and observe that the Boot Keyboard Output Report value toggles between 00 and 02.

Dependencies

This sample uses the following nRF Connect SDK libraries:

In addition, it uses the following Zephyr libraries:

  • include/sys/byteorder.h

  • include/zephyr/types.h

  • lib/libc/minimal/include/errno.h

  • include/sys/printk.h

  • Bluetooth:

    • include/bluetooth/bluetooth.h

    • include/bluetooth/gatt.h

    • include/bluetooth/hci.h

    • include/bluetooth/conn.h

    • include/bluetooth/uuid.h