HID customer application

RE: HID customer application

CY — Thu, 28 Mar 2019 02:44:06 GMT

Hi Hakon,

Sorry for the late response.

It did work.

I appreciate your great support.

BR,

Wedy

RE: HID customer application

Håkon Alseth — Wed, 13 Mar 2019 08:42:43 GMT

Hi,

Its hard to say what can be the issue without seeing a sniffer trace and/or having the full project to test with.

How are you sending this data from the firmware side?

To send a command, I would recommend that you create a function instead of using "send_keys()" in the untouched ble_app_hids_keyboard, similar to this one:

https://github.com/Rallare/nrf51_ble_app_hids_kbd_consumercontrol/blob/SDK15/main.c#L1243

Kind regards,

Håkon

RE: HID customer application

Wedy Hsiao — Tue, 12 Mar 2019 00:55:38 GMT

Hi Hakon,

Somehow I could not set up the sniffer, but I did try to use the keyboard viewer again. And It has record the event for not expectation action like below:

Some time it will show the command like below: D, C

According to the result, I would like to know whether there is any set for the HID application in the initial project from SDK.

I am afraid there is some unknown setting for the HID sample, since I cannot find the root cause in my program.

I appreciate your great support.

Thanks.

BR,

Wedy

RE: HID customer application

Håkon Alseth — Mon, 28 Jan 2019 13:54:50 GMT

Hi Wedy,

Thanks for the explanation. I think a sniffer trace should show more information here. I suspect that there's some keys that will be missed if the window for the keyboard viewer is out-of-focus.

Kind regards,

Håkon

RE: HID customer application

CY — Mon, 28 Jan 2019 04:19:30 GMT

Hi Hakon,

To answer the first question, as you see the video you can see that the "file folder" and the "outlook" will be opened in spite of there just commanded the Key "LeftWindow" showed in the software, but the command was send as WIN+F20 (130) / WIN+F19 (129) / WIN+F18 (128). When I did the second time to trigger the event it becomes normal.

I will try to used sniffer to trace later, I need some time to be familiar with the tool.

Thanks.

Wedy

RE: HID customer application

Håkon Alseth — Fri, 25 Jan 2019 13:50:36 GMT

Hi Wedy,

Which command are you referring to? Is it the "130" one that isn't supposed to be sent? Or is it one of the programs opening that is unwanted?

Could you perform a sniffer trace to see what is actually going over the bluetooth link? You can use the nRF sniffer to perform this (remember to re-pair again so that it is able to follow the encryption process).

Kind regards,

Håkon

RE: HID customer application

CY — Fri, 25 Jan 2019 03:39:34 GMT

Hi Hakon,

It is OK. Thank you for your suggestion.

Actually, there is one more thing I would like to ask that I just noticed yesterday.

www.dropbox.com/.../Record_2019_01_25_11_24_05_186.mp4

As you see in the video, whenever I just do the first operation of each event after connecting there will always show something else. After I trigger the each event for the first time, it won't happened.

Do you have any idea with this?

Frankly speaking, event I did not use the combined key, it will show something else for the first time trigger as well.

Kind regards,

Wedy

RE: HID customer application

Håkon Alseth — Thu, 24 Jan 2019 09:59:14 GMT

I am sorry, but I cannot answer this. I unfortunately do not know. You could try contacting microsoft via their development forums to ask about this specific feature.

Kind regards,

Håkon

RE: HID customer application

CY — Thu, 24 Jan 2019 09:33:27 GMT

Hi Hakon,

Thank you for your reply.

I will try it.

BTW, I would like to let you know the information below:

The computer I used to test was ThinkPad Win10 1803, which I met the FnLock problem. When I switch back to the FnLock it worked properly in both condition. Thus I just did the unlock again then it worked. However, I used surface pen to test, there was no issue like this even it is the first time to link.

Do you have any opinion with this?

Best regards,

Wedy

RE: HID customer application

Håkon Alseth — Thu, 24 Jan 2019 08:50:54 GMT

Hi,

I have not seen this behavior before, but it seems like other people have run into this as well.

There's a thread here on arduino that I found:

http://forum.arduino.cc/index.php?topic=324554.0

I am not sure why, but it seems that the usage for the specific command is offset. In arduino's code base (keyboard.h), its F18 is defined as 0xF5 (0x6d + 0x88):

https://github.com/arduino-libraries/Keyboard/blob/master/src/Keyboard.h#L78

Could you try this and see how that works? You'll need to expand the usage max and logical max in the usb descriptor again to try this.

Kind regards,

Håkon

RE: HID customer application

CY — Thu, 24 Jan 2019 02:10:56 GMT

Hi Hakon,

Sure.

static uint8_t                     report_map_data[] =
    {
        0x05, 0x01,       // Usage Page (Generic Desktop)
        0x09, 0x06,       // Usage (Keyboard)
        0xA1, 0x01,       // Collection (Application)
        0x05, 0x07,       // Usage Page (Key Codes)
        0x19, 0xe0,       // Usage Minimum (224)
        0x29, 0xe7,       // Usage Maximum (231)
        0x15, 0x00,       // Logical Minimum (0)
        0x25, 0x01,       // Logical Maximum (1)
        0x75, 0x01,       // Report Size (1)
        0x95, 0x08,       // Report Count (8)
        0x81, 0x02,       // Input (Data, Variable, Absolute)

        0x95, 0x01,       // Report Count (1)
        0x75, 0x08,       // Report Size (8)
        0x81, 0x01,       // Input (Constant) reserved byte(1)

        0x95, 0x05,       // Report Count (5)
        0x75, 0x01,       // Report Size (1)
        0x05, 0x08,       // Usage Page (Page# for LEDs)
        0x19, 0x01,       // Usage Minimum (1)
        0x29, 0x05,       // Usage Maximum (5)
        0x91, 0x02,       // Output (Data, Variable, Absolute), Led report
        0x95, 0x01,       // Report Count (1)
        0x75, 0x03,       // Report Size (3)
        0x91, 0x01,       // Output (Data, Variable, Absolute), Led report padding

        0x95, 0x06,       // Report Count (6)
        0x75, 0x08,       // Report Size (8)
        0x15, 0x00,       // Logical Minimum (0)
        
        //0x25, 0x65,       // Logical Maximum (101)
        //Wedy test to change
        0x25, 0x6F,
        
        0x05, 0x07,       // Usage Page (Key codes)
        0x19, 0x00,       // Usage Minimum (0)
        
        //0x29, 0x65,       // Usage Maximum (101)
        //Wedy test to change
        0x29, 0x6F,
        
        0x81, 0x00,       // Input (Data, Array) Key array(6 bytes)

        0x09, 0x05,       // Usage (Vendor Defined)
        0x15, 0x00,       // Logical Minimum (0)
        0x26, 0xFF, 0x00, // Logical Maximum (255)
        0x75, 0x08,       // Report Size (8 bit)
        0x95, 0x02,       // Report Count (2)
        0xB1, 0x02,       // Feature (Data, Variable, Absolute)

        0xC0              // End Collection (Application)
    };

BTW, I just found out the reason why I can not send the F18 (105) description.

Because of the keyboard on the laptop that FnLock.

I just can do the WIN+F18 Function now, like below:

Here comes the question:

How can I ensure to disable the FnLock whenever I use my device without setting the keyboard.

Thank you for spend your time to deal with this matter.

Sincerely,

Wedy

RE: HID customer application

Håkon Alseth — Wed, 23 Jan 2019 11:00:05 GMT

Could you share your current descriptor?

Kind regards,

Håkon

RE: HID customer application

CY — Tue, 22 Jan 2019 08:56:27 GMT

Hi Hakon,

Yes, I did change the USB descriptor that you mentioned before.

The picture shows the result I tried:

It still shows the response of Left Windows only.

Best Regards,

Wedy

RE: HID customer application

Håkon Alseth — Tue, 22 Jan 2019 08:30:34 GMT

Hi Wedy,

Happy new year to you as well!

When switching over to SDK 15, did you alter the USB descriptor in any way?

It is important that you extend the Logical Maximum and Usage Maximum to reflect the data you're sending, shown here in lines 666 and 669:

https://github.com/Rallare/nrf51_ble_app_hids_kbd_consumercontrol/blob/SDK15/main.c#L666

If you are sending 0x6d (109 dec), your usage and logical maximum must be equal or larger.

Could you verify if this is set in the descriptor?

Kind regards,

Håkon

RE: HID customer application

CY — Tue, 22 Jan 2019 06:46:47 GMT

Hi Hakon,

Happy new year~

Since a while I have tried to program the code, it still doesn't work properly.

The main function I would like to develop is like Windows Pen.

https://docs.microsoft.com/en-us/windows-hardware/design/component-guidelines/windows-pen-designs

Actually, I just test with surface pen and get some information by the tool "Keyboard Message" :

The method I tried is like below:

static uint8_t PRESS_HOLD[8] = {0,0,0x6D,0,0,0,0,0}; //Win+F18

static uint8_t CLEAR_CLICK[8] = {0,0,0,0,0,0,0,0}; //Null

static void bsp_event_handler(bsp_event_t event)
{
    uint32_t         err_code;
    static uint8_t * p_key = 0;
    static uint8_t   size  = 0;

    switch (event)
    {
        case BSP_EVENT_SLEEP:
            sleep_mode_enter();
            break;

        case BSP_EVENT_DISCONNECT:
            err_code = sd_ble_gap_disconnect(m_conn_handle,
                                             BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);
            if (err_code != NRF_ERROR_INVALID_STATE)
            {
                APP_ERROR_CHECK(err_code);
            }
            break;

        case BSP_EVENT_WHITELIST_OFF:
            if (m_conn_handle == BLE_CONN_HANDLE_INVALID)
            {
                err_code = ble_advertising_restart_without_whitelist(&m_advertising);
                if (err_code != NRF_ERROR_INVALID_STATE)
                {
                    APP_ERROR_CHECK(err_code);
                }
            }
            break;
        
        case BSP_EVENT_KEY_1:
          
            if (m_conn_handle != BLE_CONN_HANDLE_INVALID)
            {
              press_hold();
            }
            break;

        default:
            break;
    }
}

static void press_hold (void)
{
    uint32_t         err_code;
    static uint8_t * p_key = 0;
    static uint8_t   size  = 0;
    keys_send(8, p_key);
    p_key=PRESS_HOLD;
    keys_send(8, p_key);
    p_key=CLEAR_CLICK;
}

static uint32_t send_key_scan_press_release(ble_hids_t * p_hids,
                                            uint8_t    * p_key_pattern,
                                            uint16_t     pattern_len,
                                            uint16_t     pattern_offset,
                                            uint16_t   * p_actual_len)
{
    ret_code_t err_code;
    uint16_t offset;
    uint16_t data_len;
    uint8_t  data[INPUT_REPORT_KEYS_MAX_LEN];

    // HID Report Descriptor enumerates an array of size 6, the pattern hence shall not be any
    // longer than this.
    STATIC_ASSERT((INPUT_REPORT_KEYS_MAX_LEN - 2) == 6);

    ASSERT(pattern_len <= (INPUT_REPORT_KEYS_MAX_LEN - 2));

    offset   = pattern_offset;
    data_len = pattern_len;

    do
    {
        // Reset the data buffer.
        memset(data, 0, sizeof(data));

        // Copy the scan code.
        memcpy(data + SCAN_CODE_POS + offset, p_key_pattern + offset, data_len - offset);

        if (bsp_button_is_pressed(WINDOW_BUTTON_ID))
        {
            data[MODIFIER_KEY_POS] |= WINDOW_KEY_CODE;
        }

        if (!m_in_boot_mode)
        {
            err_code = ble_hids_inp_rep_send(p_hids,
                                             INPUT_REPORT_KEYS_INDEX,
                                             INPUT_REPORT_KEYS_MAX_LEN,
                                             data,
                                             m_conn_handle);
        }
        else
        {
            err_code = ble_hids_boot_kb_inp_rep_send(p_hids,
                                                     INPUT_REPORT_KEYS_MAX_LEN,
                                                     data,
                                                     m_conn_handle);
        }

        if (err_code != NRF_SUCCESS)
        {
            break;
        }

        offset++;
    }
    while (offset <= data_len);

    *p_actual_len = offset;

    return err_code;
}

It was not worked properly.

Do you have any suggestion with this topic?

If I would like to control the button event, should I still need to use app_button as the reference?

Is the below protocol I tried is correct?

i. “Win” + “F18” (raw data: 08 00 6D 00 00 00 00 00)
ii. Release “F18” (raw data: 08 00 00 00 00 00 00 00)
iii. Release “Win” (raw data: 00 00 00 00 00 00 00 00)

BTW, I just change the SDK from V11 to V15.2 in order to get the swift pair function.

RE: HID customer application

Håkon Alseth — Wed, 02 Jan 2019 09:05:40 GMT

Hi Wedy,

I am very sorry for the late reply.

These are hard-coded bit mapped commands, where the first bit is directly mapped to "Play".

Here's the enum:

typedef enum
{
    RELEASE_KEY                     = 0x00,
    CONSUMER_CTRL_PLAY              = 0x01,
    CONSUMER_CTRL_ALCCC             = 0x02,
    CONSUMER_CTRL_SCAN_NEXT_TRACK   = 0x04,
    CONSUMER_CTRL_SCAN_PREV_TRACK   = 0x08,
    CONSUMER_CTRL_VOL_DW            = 0x10,
    CONSUMER_CTRL_VOL_UP            = 0x20,
    CONSUMER_CTRL_AC_FORWARD        = 0x40,
    CONSUMER_CTRL_AC_BACK           = 0x80,    
} consumer_control_t;

Which is directly derived from the descriptor:

        0xA1, 0x01,                     // Collection (Application)
        0x85, 0x02,                     //     Report Id (2)
        0x15, 0x00,                     //     Logical minimum (0)
        0x25, 0x01,                     //     Logical maximum (1)
        0x75, 0x01,                     //     Report Size (1)
        0x95, 0x01,                     //     Report Count (1)

        0x09, 0xCD,                     //     Usage (Play/Pause)
        0x81, 0x02,                     //     Input (Data,Value,Relative,Bit Field)
        0x0A, 0x83, 0x01,               //     Usage (AL Consumer Control Configuration)
        0x81, 0x02,                     //     Input (Data,Value,Relative,Bit Field)
        0x09, 0xB5,                     //     Usage (Scan Next Track)
        0x81, 0x02,                     //     Input (Data,Value,Relative,Bit Field)
        0x09, 0xB6,                     //     Usage (Scan Previous Track)
        0x81, 0x02,                     //     Input (Data,Value,Relative,Bit Field)

        0x09, 0xEA,                     //     Usage (Volume Down)
        0x81, 0x02,                     //     Input (Data,Value,Relative,Bit Field)
        0x09, 0xE9,                     //     Usage (Volume Up)
        0x81, 0x02,                     //     Input (Data,Value,Relative,Bit Field)
        0x0A, 0x25, 0x02,               //     Usage (AC Forward)
        0x81, 0x02,                     //     Input (Data,Value,Relative,Bit Field)
        0x0A, 0x24, 0x02,               //     Usage (AC Back)
        0x81, 0x02,                     //     Input (Data,Value,Relative,Bit Field)
        0xC0,                           // End Collection

By changing the first command 0xCD (Play/Pause) to anything else, the enum corresponding to bit 0 (CONSUMER_CTRL_PLAY) will also change behavior.

When specifying a ReportID, you can choose any unused number between 1 and 255 (0 is reserved).

Kind regards,

Håkon

RE: HID customer application

CY — Tue, 18 Dec 2018 08:39:58 GMT

Hi Hakan,

Sorry for disturbing.

As your explanation of the report, I could understand in "left windows key" case.

But there comes another question.

It is the original part of the consumer control sample code.

The Logical max/min is 0/1, but there is 0xCD to 0xE9, however, there also show the command as consumer_control_t. How it can work?

Moreover, I would like to know the number of report ID is specific for consumer or we can identified by our-self?

Thanks,

Wedy

RE: HID customer application

CY — Mon, 17 Dec 2018 09:18:06 GMT

Hi,

I will try to figure it out.

At this moment, I would like to know it will influence the consumer control?

/**@brief Function for handling button events.
 *
 * @param[in]   pin_no   The pin number of the button pressed.
 */
static void button_event_handler(uint8_t pin_no, uint8_t button_action)
{
    if (button_action == APP_BUTTON_PUSH)
    {
        switch (pin_no)
        {
            case KEY_PRESS_BUTTON_PIN_NO:
            {
                APP_ERROR_CHECK(hid_kbd_send_string());
                break;
            }
            case VOLDOWN_BUTTON:
                APP_ERROR_CHECK(consumer_control_send(CONSUMER_CTRL_VOL_DW));
                break;
            case VOLUP_BUTTON:
                APP_ERROR_CHECK(consumer_control_send(CONSUMER_CTRL_VOL_UP));
                break;
            //12/14 Wedy add for functional key
           /* case FUNCTION_BUTTON:
                APP_ERROR_CHECK(function_control_send(FUNCTION_F01));
                break;*/
            default:
                APP_ERROR_HANDLER(pin_no);
                break;
        }
    }
    else if (button_action == APP_BUTTON_RELEASE)
    {
        switch (pin_no)
        {
            case VOLDOWN_BUTTON:
            /* Fall-through */
            case VOLUP_BUTTON:
                APP_ERROR_CHECK(consumer_control_send(RELEASE_KEY)); 
                break;
            case KEY_PRESS_BUTTON_PIN_NO:    
                APP_ERROR_CHECK(hid_kbd_send_release());
                break;
            //12/14 Wedy add for functional key
           /* case FUNCTION_BUTTON:
                APP_ERROR_CHECK(function_control_send(LIFT_KEY)); 
                break;*/
            default:
                APP_ERROR_HANDLER(pin_no);
                break;
        }
    }
}

Even I block this part the consumer control cannot work?

RE: HID customer application

Håkon Alseth — Mon, 17 Dec 2018 09:07:45 GMT

Hi,

A USB descriptor has limits, where in the case of the keyboard it has a usage min. set to 0, and a maximum to 101. See the fields LOGICAL_MINIMUM and MAXIMUM, and USAGE_MINIMUM and MAXIMUM.

The "Left Windows Key" has a usage of 0xE3, which is 227 decimal, and that is defined in the first byte of the keyboard USB descriptor (which has a range of 224 - 231), meaning that if you set bit 3 (0x08), this button shall be triggered.

In order to use F18 to F20 (Usage 0x6D to 0x6F), you need to expand the above mentioned usage min/max and logical min/max in report id 1, or add a new report id which includes these.

Kind regards,

Håkon

RE: HID customer application

CY — Mon, 17 Dec 2018 08:53:09 GMT

Hi Hakon,

Actually, I just could not test the code in present status because when I add the BUTTON_FUNCTION and the report id 3, all of the functions are not worked properly. It is awkward, and I still try to find out the reason.

What is " report-id 3 (0x3A command atleast) in the generic keyboard endpoint." really means in the code? And if I use the F18-F20 in the report id 1 is that possible I can add the modifier WIN?

 //12/14 Wedy add for functional key
        0x05, 0x01,         // Usage Page (Generic Desktop)
        0x09, 0x06,         // Usage (Keyboard)
        0xa1, 0x01,         // Collection: (Application)
	    0x85, 0x03,         // Report ID(3)  
        0x05, 0x07,         // Usage Page (Key Codes)
        0x09, 0x3A,         // USAGE(F01 Key)
        0x09, 0x6D,         // USAGE(F18 Key)
	    0x09, 0x6E,         // USAGE(F19 Key)
	    0x09, 0x6F,         // USAGE(F20 Key)
	    0x09, 0xe3,         // USAGE(Left Windows Key)
	    0x15, 0x00,         // LOGICAL_MINIMUM(0)
	    0x25, 0x01,         // LOGICAL_MAXIMUM(1)
	    0x75, 0x01,         // REPORT_SIZE(1)
	    0x95, 0x03,         // REPORT_COUNT(3)
	    0x81, 0x02,         // INPUT (Data, Var, Abs)
	    0x95, 0x05,         // REPORT_COUNT(5)
	    0x81, 0x03,         // INPUT(Cnst, Var, Abs)
        0xc0                //  End Collection ->41byte

How to call F1 and WIN from report map at the same time? (WIN+F1)

RE: HID customer application

Håkon Alseth — Mon, 17 Dec 2018 08:39:33 GMT

Hi Wedy,

When this last worked, what was the command that you sent at that point?

You should be able to send the information in report-id 3 (0x3A command atleast) in the generic keyboard endpoint.

F18 to F20 commands are outside of the logical and usage maximum (101) set in report id 1.

Kind regards,

Håkon

RE: HID customer application

CY — Fri, 14 Dec 2018 09:16:02 GMT

Hi Hakon,

OK, I will try to modified from the your suggestion.

Actually I was trying to use the app_button to get the same performance like last time (WIN+F1).

Below are the way I pattern the structure from the example you provide. Honestly, I have no idea how to use the structure like these

#define OUTPUT_REPORT_INDEX              0                                              /**< Index of Output Report. */
#define OUTPUT_REPORT_MAX_LEN            1                                              /**< Maximum length of Output Report. */
#define INPUT_REPORT_KEYS_INDEX          0                                              /**< Index of Input Report. */
#define INPUT_CCONTROL_KEYS_INDEX		 1
#define OUTPUT_REPORT_BIT_MASK_CAPS_LOCK 0x02                                           /**< CAPS LOCK bit in Output Report (based on 'LED Page (0x08)' of the Universal Serial Bus HID Usage Tables). */
#define INPUT_REP_REF_ID                 1                                              /**< Id of reference to Keyboard Input Report. */
#define INPUT_CC_REP_REF_ID				 2
#define OUTPUT_REP_REF_ID                0                                              /**< Id of reference to Keyboard Output Report. */
//12/14 Wedy add for functional button
#define INPUT_FUNCTION_KEY_INDEX         2
#define INPUT_FU_REP_REF_ID              3

#define MAX_BUFFER_ENTRIES               5                                              /**< Number of elements that can be enqueued */

#define BASE_USB_HID_SPEC_VERSION        0x0101                                         /**< Version number of base USB HID Specification implemented by this application. */

#define INPUT_REPORT_KEYS_MAX_LEN        8                                              /**< Maximum length of the Input Report characteristic. */
#define INPUT_CC_REPORT_KEYS_MAX_LEN	 1
//12/14 Wedy add for functional key
#define INPUT_FU_REPORT_KEYS_MAX_LEN	 1

I have know idea why the typedef enum can indicate the relative function in the usage report

//12/14 Wedy add to test the functional key
typedef enum
{
    LIFT_KEY                        = 0x00,
    FUNCTION_F01                    = 0x01,
    FUNCTION_F18                    = 0x02,
    FUNCTION_F19                    = 0x04,
    FUNCTION_F20                    = 0x08,
    LEFT_WINDOW_KEY                 = 0x10,    
} function_control_t;

typedef enum
{
    RELEASE_KEY                     = 0x00,
    CONSUMER_CTRL_PLAY              = 0x01,
    CONSUMER_CTRL_ALCCC             = 0x02,
    CONSUMER_CTRL_SCAN_NEXT_TRACK   = 0x04,
    CONSUMER_CTRL_SCAN_PREV_TRACK   = 0x08,
    CONSUMER_CTRL_VOL_DW            = 0x10,
    CONSUMER_CTRL_VOL_UP            = 0x20,
    CONSUMER_CTRL_AC_FORWARD        = 0x40,
    CONSUMER_CTRL_AC_BACK           = 0x80,    
} consumer_control_t;

I hope I can use the same method to get achievement.

static uint8_t report_map_data[] =
    {
        0x05, 0x01,                 // Usage Page (Generic Desktop)
        0x09, 0x06,                 // Usage (Keyboard)
        0xA1, 0x01,                 // Collection (Application)
		0x85, 0x01,                     //     Report Id (1)
        0x05, 0x07,                 //     Usage Page (Key Codes)
        0x19, 0xe0,                 //     Usage Minimum (224)
        0x29, 0xe7,                 //     Usage Maximum (231)
        0x15, 0x00,                 //     Logical Minimum (0)
        0x25, 0x01,                 //     Logical Maximum (1)
        0x75, 0x01,                 //     Report Size (1)
        0x95, 0x08,                 //     Report Count (8)
        0x81, 0x02,                 //     Input (Data, Variable, Absolute)

        0x95, 0x01,                 //     Report Count (1)
        0x75, 0x08,                 //     Report Size (8)
        0x81, 0x01,                 //     Input (Constant) reserved byte(1)

        0x95, 0x05,                 //     Report Count (5)
        0x75, 0x01,                 //     Report Size (1)
        0x05, 0x08,                 //     Usage Page (Page# for LEDs)
        0x19, 0x01,                 //     Usage Minimum (1)
        0x29, 0x05,                 //     Usage Maximum (5)
        0x91, 0x02,                 //     Output (Data, Variable, Absolute), Led report
        0x95, 0x01,                 //     Report Count (1)
        0x75, 0x03,                 //     Report Size (3)
        0x91, 0x01,                 //     Output (Data, Variable, Absolute), Led report padding

        0x95, 0x06,                 //     Report Count (6)
        0x75, 0x08,                 //     Report Size (8)
        0x15, 0x00,                 //     Logical Minimum (0)
        0x25, 0x65,                 //     Logical Maximum (101)
        0x05, 0x07,                 //     Usage Page (Key codes)
        0x19, 0x00,                 //     Usage Minimum (0)
        0x29, 0x65,                 //     Usage Maximum (101)
        0x81, 0x00,                 //     Input (Data, Array) Key array(6 bytes)

        0x09, 0x05,                 //     Usage (Vendor Defined)
        0x15, 0x00,                 //     Logical Minimum (0)
        0x26, 0xFF, 0x00,           //     Logical Maximum (255)
        0x75, 0x08,                 //     Report Count (2)
        0x95, 0x02,                 //     Report Size (8 bit)
        0xB1, 0x02,                 //     Feature (Data, Variable, Absolute)
        0xC0,                       // End Collection (Application)
		
        // Report ID 2: Advanced buttons
        0x05, 0x0C,                     // Usage Page (Consumer)
        0x09, 0x01,                     // Usage (Consumer Control)
        0xA1, 0x01,                     // Collection (Application)
        0x85, 0x02,                     //     Report Id (2)
        0x15, 0x00,                     //     Logical minimum (0)
        0x25, 0x01,                     //     Logical maximum (1)
        0x75, 0x01,                     //     Report Size (1)
        0x95, 0x01,                     //     Report Count (1)

        0x09, 0xCD,                     //     Usage (Play/Pause)
        0x81, 0x02,                     //     Input (Data,Value,Relative,Bit Field)
        0x0A, 0x83, 0x01,               //     Usage (AL Consumer Control Configuration)
        0x81, 0x02,                     //     Input (Data,Value,Relative,Bit Field)
        0x09, 0xB5,                     //     Usage (Scan Next Track)
        0x81, 0x02,                     //     Input (Data,Value,Relative,Bit Field)
        0x09, 0xB6,                     //     Usage (Scan Previous Track)
        0x81, 0x02,                     //     Input (Data,Value,Relative,Bit Field)

        0x09, 0xEA,                     //     Usage (Volume Down)
        0x81, 0x02,                     //     Input (Data,Value,Relative,Bit Field)
        0x09, 0xE9,                     //     Usage (Volume Up)
        0x81, 0x02,                     //     Input (Data,Value,Relative,Bit Field)
        0x0A, 0x25, 0x02,               //     Usage (AC Forward)
        0x81, 0x02,                     //     Input (Data,Value,Relative,Bit Field)
        0x0A, 0x24, 0x02,               //     Usage (AC Back)
        0x81, 0x02,                     //     Input (Data,Value,Relative,Bit Field)
        0xC0,                           // End Collection

        //12/14 Wedy add for functional key
        0x05, 0x01,         // Usage Page (Generic Desktop)
        0x09, 0x06,         // Usage (Keyboard)
        0xa1, 0x01,         // Collection: (Application)
	    0x85, 0x03,         // Report ID(3)  
        0x05, 0x07,         // Usage Page (Key Codes)
        0x09, 0x3A,         // USAGE(F01 Key)
        0x09, 0x6D,         // USAGE(F18 Key)
	    0x09, 0x6E,         // USAGE(F19 Key)
	    0x09, 0x6F,         // USAGE(F20 Key)
	    0x09, 0xe3,         // USAGE(Left Windows Key)
	    0x15, 0x00,         // LOGICAL_MINIMUM(0)
	    0x25, 0x01,         // LOGICAL_MAXIMUM(1)
	    0x75, 0x01,         // REPORT_SIZE(1)
	    0x95, 0x03,         // REPORT_COUNT(3)
	    0x81, 0x02,         // INPUT (Data, Var, Abs)
	    0x95, 0x05,         // REPORT_COUNT(5)
	    0x81, 0x03,         // INPUT(Cnst, Var, Abs)
        0xc0                //  End Collection ->41byte
		};
		    // Initialize HID Service - keyboard descriptor input and output report
    p_input_report                      = &input_report_array[INPUT_REPORT_KEYS_INDEX];
    p_input_report->max_len             = INPUT_REPORT_KEYS_MAX_LEN;
    p_input_report->rep_ref.report_id   = INPUT_REP_REF_ID;
    p_input_report->rep_ref.report_type = BLE_HIDS_REP_TYPE_INPUT;

    BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM(&p_input_report->security_mode.cccd_write_perm);
    BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM(&p_input_report->security_mode.read_perm);
    BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM(&p_input_report->security_mode.write_perm);	
    p_output_report                      = &output_report_array[OUTPUT_REPORT_INDEX];
    p_output_report->max_len             = OUTPUT_REPORT_MAX_LEN;
    p_output_report->rep_ref.report_id   = OUTPUT_REP_REF_ID;
    p_output_report->rep_ref.report_type = BLE_HIDS_REP_TYPE_OUTPUT;

	// 	Initialize HID Service - ConsumerControl
	
    // Initialize HID Service
    p_input_report                      = &input_report_array[INPUT_CCONTROL_KEYS_INDEX];
    p_input_report->max_len             = INPUT_CC_REPORT_KEYS_MAX_LEN;
    p_input_report->rep_ref.report_id   = INPUT_CC_REP_REF_ID;
    p_input_report->rep_ref.report_type = BLE_HIDS_REP_TYPE_INPUT;

    BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM(&p_input_report->security_mode.cccd_write_perm);
    BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM(&p_input_report->security_mode.read_perm);
    BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM(&p_input_report->security_mode.write_perm);	

    //12/14 Wedy add for functional key
    p_input_report                      = &input_report_array[INPUT_FUNCTION_KEY_INDEX];
    p_input_report->max_len             = INPUT_FU_REPORT_KEYS_MAX_LEN;
    p_input_report->rep_ref.report_id   = INPUT_FU_REP_REF_ID;
    p_input_report->rep_ref.report_type = BLE_HIDS_REP_TYPE_INPUT;
    BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM(&p_input_report->security_mode.cccd_write_perm);
    BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM(&p_input_report->security_mode.read_perm);
    BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM(&p_input_report->security_mode.write_perm);

As you can see, I just add the report, and try to call the function, but it doesn't work.

Did I get any misunderstanding?

//12/14 Wedy add for functional key
/**@brief Function for sending function control data
 */
static uint32_t function_control_send(function_control_t cmd)
{
    return ble_hids_inp_rep_send(&m_hids, INPUT_FUNCTION_KEY_INDEX, INPUT_FU_REPORT_KEYS_MAX_LEN, (uint8_t*)&cmd);
}

/**@brief Function for sending consumer control data
 */
static uint32_t consumer_control_send(consumer_control_t cmd)
{
    return ble_hids_inp_rep_send(&m_hids, INPUT_CCONTROL_KEYS_INDEX, INPUT_CC_REPORT_KEYS_MAX_LEN, (uint8_t*)&cmd);
}

static uint32_t hid_kbd_send_string(void)
{
    uint8_t temp_buf[INPUT_REPORT_KEYS_MAX_LEN] = {0x00, 0x00, 0xb, 0xc, 0x2c, 0x0, 0x0, 0x0};   
    return ble_hids_inp_rep_send(&m_hids, INPUT_REPORT_KEYS_INDEX, INPUT_REPORT_KEYS_MAX_LEN, (uint8_t*)temp_buf);
}

static uint32_t hid_kbd_send_release(void)
{
    uint8_t temp_buf[INPUT_REPORT_KEYS_MAX_LEN] = {0, 0, 0, 0, 0, 0, 0, 0};   
    return ble_hids_inp_rep_send(&m_hids, INPUT_REPORT_KEYS_INDEX, INPUT_REPORT_KEYS_MAX_LEN, (uint8_t*)temp_buf);
}

/**@brief Function for handling button events.
 *
 * @param[in]   pin_no   The pin number of the button pressed.
 */
static void button_event_handler(uint8_t pin_no, uint8_t button_action)
{
    if (button_action == APP_BUTTON_PUSH)
    {
        switch (pin_no)
        {
            case KEY_PRESS_BUTTON_PIN_NO:
            {
                APP_ERROR_CHECK(hid_kbd_send_string());
                break;
            }
            case VOLDOWN_BUTTON:
                APP_ERROR_CHECK(consumer_control_send(CONSUMER_CTRL_VOL_DW));
                break;
            case VOLUP_BUTTON:
                APP_ERROR_CHECK(consumer_control_send(CONSUMER_CTRL_VOL_UP));
                break;
            //12/14 Wedy add for functional key
            case FUNCTION_BUTTON:
                APP_ERROR_CHECK(function_control_send(FUNCTION_F01));
                break;
            default:
                APP_ERROR_HANDLER(pin_no);
                break;
        }
    }
    else if (button_action == APP_BUTTON_RELEASE)
    {
        switch (pin_no)
        {
            case VOLDOWN_BUTTON:
            /* Fall-through */
            case VOLUP_BUTTON:
                APP_ERROR_CHECK(consumer_control_send(RELEASE_KEY)); 
                break;
            case KEY_PRESS_BUTTON_PIN_NO:    
                APP_ERROR_CHECK(hid_kbd_send_release());
                break;
            //12/14 Wedy add for functional key
            case FUNCTION_BUTTON:
                APP_ERROR_CHECK(function_control_send(LIFT_KEY)); 
                break;
            default:
                APP_ERROR_HANDLER(pin_no);
                break;
        }
    }
}

I am sorry for bothering you many times.

I really appreciate your support.

BTW, when I add the code into the project, the functions of consumer are also failed and the button are out of the response.

Sincerely,

Wedy

RE: HID customer application

Håkon Alseth — Fri, 14 Dec 2018 08:54:41 GMT

Hi Wedy,

The button handling in BSP is a wrapper around app_button. There's no need to have both in the same application.

The events "BSP_EVENT_DISCONNECT", "BSP_EVENT_WHITELIST_OFF", and "BSP_EVENT_SLEEP" are specific buttons that places the device into each of these modes. The actual functions called is shown in main.c::bsp_event_handler() in the SDK example. You can copy these into your own button handling if you'd like.

Scheduler vs. no scheduler is up to you. If your application requires data to be handled in several contexts (interrupt and main), one uses a scheduler to always run functions/operations in main context.

Kind regards,

Håkon

RE: HID customer application

CY — Fri, 14 Dec 2018 01:44:11 GMT

Hi Hakon,

Thank you for the reply.

I just try to run the sample code you applied and it is worked.

However, I just found that there is no setting for the BSP_EVENT control (sleep, disconnect, whitelist off).

And I also found they use the different header for timer (app_timer vs. app_timer_appsh, app_scheduler)

According to this, I would like to know is it possible to keep the both feature in the same project? Or where can I found the relative of bsp_enevt control in the sample code you provided?

Thanks,

Wedy

RE: HID customer application

Håkon Alseth — Thu, 13 Dec 2018 11:10:59 GMT

This one uses app_button (checkout the branch SDK11):

https://github.com/Rallare/nrf51_ble_app_hids_kbd_consumercontrol/tree/SDK11

Kind regards,

Håkon