HOW to dynamically Change READ VALUES ?

[Larkin]

Hi !

I added " Read Characteristic" in NUS.

How can I get different values every time I click "read again"?For example, read the value of a varying ADC from here.

How do I dynamically send an ADC value from here in NRF52832? Which API  function should I call?

Thanks very much!

[cbd]

Your easiest way is to make have your NRF52832 update the characteristic value with your ADC data on a regular basis (say on a timer). There is no synchronisation between the read action on the phone app and the update of the data in the characteristic.

If the phone app is set to allow notification events on the characteristic then you can set the notify bit when adding your characteristic definition (on the NRF52832) and trigger your app to automatically read the characteristic value by updating the characteristic with new ADC data and triggering a notification event on the NRF52832.

Example of notification from some project code of mine:

static uint32_t lds_ResponseCharAdd(ble_lds_t * p_lds, const ble_lds_init_t * p_lds_init)
{
    if (NULL == p_lds)
    {
        return NRF_ERROR_INTERNAL;
    }
    ble_add_char_params_t add_char_params;


    memset(&add_char_params, 0, sizeof(add_char_params));
    add_char_params.uuid                     = LDS_UUID_RESPONSE_CHAR;
    add_char_params.uuid_type                = p_lds->uuid_type;
    add_char_params.max_len                  = sizeof(lds_drive_data_t);
    add_char_params.init_len                 = sizeof(lds_drive_data_t);
    add_char_params.is_var_len               = true;
    add_char_params.char_props.notify        = 1;
    add_char_params.char_props.read          = 1;

    add_char_params.read_access  = SEC_OPEN;
    add_char_params.write_access = SEC_OPEN;
    add_char_params.cccd_write_access= SEC_OPEN;

    return characteristic_add(p_lds->service_handle, &add_char_params, &p_lds->lds_char_result_handles);

}

then when you want to update your ADC value you set the ble_gatts_hvx_params_t data with your data and update the characteristic using sd_ble_gatts_hvx and then sd_ble_gatts_value_set

e.g.

 /* set-up parameter data for BLE characteristic update notification */
    uint16_t len = data.dataLength + index; // sizeof(m_lds_result_data);
    ble_gatts_hvx_params_t params;

    memset(&params, 0, sizeof(params));
    params.type = BLE_GATT_HVX_NOTIFICATION;
    params.p_len = &len;

    /* update and notify for the characteristic */
    params.handle = m_LiveDriveService.lds_char_result_handles.value_handle;
    params.p_data = m_scratch_buffer;

    err_code = sd_ble_gatts_hvx(m_LiveDriveService.conn_handle, &params);
    if (NRF_SUCCESS != err_code)
    { /* notifications may not be enabled, attempt to update data */
        ble_gatts_value_t valueData;
        valueData.len = len;
        valueData.offset = 0;
        valueData.p_value = m_scratch_buffer;
        NRF_LOG_HEXDUMP_DEBUG(m_scratch_buffer, len);
        err_code = sd_ble_gatts_value_set(m_LiveDriveService.conn_handle,
                                          m_LiveDriveService.lds_char_result_handles.value_handle,
                                          &valueData);
        if (NRF_SUCCESS != err_code)
        {
            return err_code;
        }
    }