Create BLE characteristic with notifications active on queued write service

RE: Create BLE characteristic with notifications active on queued write service

bjorn-spockeli — Fri, 17 Aug 2018 09:05:12 GMT

The only property I see in the attached code from August 2nd is

add_char_params.char_props.write = true;

However; I do got the same result and you need to add an additional line setting the cccd write access, i.e.

add_char_params.char_props.notify= true;
add_char_params.char_props.read = true;
add_char_params.cccd_write_access= true;

Best regards

Bjørn

RE: Create BLE characteristic with notifications active on queued write service

naf18 — Fri, 17 Aug 2018 08:24:29 GMT

Hi Bjørn,

If you take a look at my code at the beginning of this thread, that's exactly what I have done, however, after that change the function characteristic_add() returned NRF_INVALID_PARAM. Could I be forgetting something?

Thanks

Nuno Ferreira

RE: Create BLE characteristic with notifications active on queued write service

bjorn-spockeli — Fri, 17 Aug 2018 08:14:33 GMT

Hi Nuno.

I took a look at the characteristic_add() function that is used in the nrf_ble_qwrs_init() function. The characteristic_add() function is a utility function that sets a lot of the parameters automatically, as opposed to setting them manually as I do in my tutorial. If you want the QWRS characteristic to have Read and Notify properties in addition to Write, then I think you simply need to add

add_char_params.char_props.notify= true;
add_char_params.char_props.read = true;

when the ble_add_char_params_t struct is populated. The characteristic_add() function will examine the properties and then set the appropriate permissions for the notification property, i.e.

memset(&char_md, 0, sizeof(ble_gatts_char_md_t));
if ((p_char_props->char_props.notify == 1)||(p_char_props->char_props.indicate == 1))
{

    memset(&cccd_md, 0, sizeof(cccd_md));
    set_security_req(p_char_props->cccd_write_access, &cccd_md.write_perm);
    BLE_GAP_CONN_SEC_MODE_SET_OPEN(&cccd_md.read_perm);

    cccd_md.vloc       = BLE_GATTS_VLOC_STACK;

    char_md.p_cccd_md  = &cccd_md;
}

RE: Create BLE characteristic with notifications active on queued write service

naf18 — Thu, 16 Aug 2018 15:20:13 GMT

Hi Bjørn,

I will repeat the tests and send you a log of the nRF connect.

However, I don't understand yet why I can't add a characteristic with those permissions using my code. in your first comment you told "I think that you're missing the pointer to the ble_gatts_attr_md_t cccd_md struct in the charachteristic metadata( char_md).". Where did I forgot the pointer? What do I need to change to put it working?

Thanks

RE: Create BLE characteristic with notifications active on queued write service

bjorn-spockeli — Thu, 16 Aug 2018 09:38:00 GMT

Could you be a bit more specific than "when I tried to read something it failed and I was again unable to use that characteristic"? Did you get en error message with an error code when you tried to write to it in nRF connect?

RE: Create BLE characteristic with notifications active on queued write service

naf18 — Tue, 14 Aug 2018 14:34:04 GMT

Hi Bjørn,

Thanks for your answer. I was trying that example and I was able to create a characteristic with reading and notifications permissions. It appeared at nordic nrf connect application, but when I tried to read something it failed and I was again unable to use that characteristic.

Thanks

Nuno Ferreira

RE: Create BLE characteristic with notifications active on queued write service

bjorn-spockeli — Thu, 09 Aug 2018 13:21:57 GMT

Hi Nuno,

I apologize for the late reply.

I suggest that you take a look at custom_value_char_add() in ble_cus.c in the GitHub repo link below.

https://github.com/bjornspockeli/custom_ble_service_example/blob/master/ble_cus.c

It adds a characteristic that has write/read/notification properties.

Bjørn

RE: Create BLE characteristic with notifications active on queued write service

naf18 — Thu, 02 Aug 2018 16:40:02 GMT

Hi bjorn-spockeli,

thanks for your answer.

Below you can check the functions I'm running to configure this service:

retval_t initQWRSService()
{
    uint32_t          err_code = 0;
    nrf_ble_qwr_init_t  qwr_init;
    nrf_ble_qwrs_init_t qwrs_init;

    // Initialize Queued Write Module
    qwr_init.mem_buffer.len   = MEM_BUFF_SIZE;
    qwr_init.mem_buffer.p_mem = umdc_qwrs_service.m_buffer;
    qwr_init.error_handler    = NULL;
    qwr_init.callback         = queuedWriteHandlerWrapper;

    err_code += nrf_ble_qwr_init(&umdc_qwrs_service.m_qwr, &qwr_init);

    //initialize the Queued Writes Example Service
    memset(&qwrs_init, 0, sizeof(qwrs_init));

    qwrs_init.evt_handler   = queuedWriteServiceEvtHandlerWrapper;
    qwrs_init.error_handler = NULL;
    qwrs_init.p_qwr_ctx     = &umdc_qwrs_service.m_qwr;

    err_code += nrfBleQWRSInit(&qwrs_init, &umdc_qwrs_service.m_qwrs);

    if (0 == err_code) {
        return SUCCESS;
    }

    return ERROR;
}


retval_t nrfBleQWRSInit(nrf_ble_qwrs_init_t *p_qwrs_init, nrf_ble_qwrs_t *p_qwrs)
{
    ret_code_t    err_code = 0;
    ble_uuid_t    ble_uuid;

    // Initialize service structure.
    p_qwrs->evt_handler   = p_qwrs_init->evt_handler;
    p_qwrs->error_handler = p_qwrs_init->error_handler;
    p_qwrs->conn_handle   = BLE_CONN_HANDLE_INVALID;

    // Add service.
    ble_uuid128_t base_uuid = QWRS_BASE_UUID;
    err_code += sd_ble_uuid_vs_add(&base_uuid, &p_qwrs->uuid_type);

    ble_uuid.type = p_qwrs->uuid_type;
    ble_uuid.uuid = BLE_UUID_QWRS_SERVICE;

    err_code += sd_ble_gatts_service_add(BLE_GATTS_SRVC_TYPE_PRIMARY,
                                        &ble_uuid,
                                        &p_qwrs->service_handle);

    //Add Long characteristic
    ble_add_char_params_t add_char_params;

    memset(&add_char_params, 0, sizeof(add_char_params));
    add_char_params.uuid               = BLE_UUID_QWRS_LONG_CHARACTERISTIC;
    add_char_params.max_len            = BLE_QWRS_MAX_LONG_CHAR_LEN;
    add_char_params.init_len           = 0;
    add_char_params.char_props.write   = true;
    add_char_params.write_access       = SEC_OPEN;
    add_char_params.is_defered_write   = true;

    err_code += characteristic_add(p_qwrs->service_handle,
                                  &add_char_params,
                                  &p_qwrs->long_charact_handles);

    if (p_qwrs_init->p_qwr_ctx != NULL)
    {
        err_code += nrf_ble_qwr_attr_register(p_qwrs_init->p_qwr_ctx,
                                             p_qwrs->long_charact_handles.value_handle);
    }

    if (0 == err_code) {
        return SUCCESS;
    }

    return ERROR;
}

The next step I need is to add a characteristic with read and notifications properties active. Can you tell what I need to do?

Thanks

Nuno Ferreira

RE: Create BLE characteristic with notifications active on queued write service

bjorn-spockeli — Thu, 02 Aug 2018 15:39:00 GMT

HI Naf18,

could you post the entire .c file where you're adding the characteristics? I think that you're missing the pointer to the ble_gatts_attr_md_t cccd_md struct in the charachteristic metadata( char_md).

Best regards

Bjørn