RE: Problem with sending data from central to peripheral

Kenneth — Mon, 02 Aug 2021 16:19:02 GMT

And you can write to them from the nRF Connect app? They are writeable?

Kenneth

RE: Problem with sending data from central to peripheral

stopbar — Thu, 29 Jul 2021 13:38:14 GMT

Ok so handle 0x0003 is asigned to Device Name in Generic Access service. My custom characteristics are as follow: 0x000D, 0x000F, 0x0011, 0x0013, 0x0015.

RE: Problem with sending data from central to peripheral

Kenneth — Thu, 29 Jul 2021 13:27:01 GMT

You need to "hover" over the different characteristics to find which is handle 0x0003, for instance for a random BLE peripheral I could find:

The service changed characteristic (handle 0x0003) is indicate only, and is not writeable.

Kenneth

RE: Problem with sending data from central to peripheral

stopbar — Thu, 29 Jul 2021 13:00:10 GMT

characteristics creating:

uint32_t ble_config_init(ble_config_t *p_config, ble_config_init_t const *p_config_init)
{
    ret_code_t err_code;
    ble_uuid_t ble_uuid;
    ble_uuid128_t config_base_uuid = BLE_UUID_CONFIG_SERVICE_BASE_UUID;
    ble_add_char_params_t add_char_params;

    VERIFY_PARAM_NOT_NULL(p_config);
    VERIFY_PARAM_NOT_NULL(p_config_init);

    // Initialize the service structure.
    p_config->data_handler = p_config_init->data_handler;

    /**@snippet [Adding proprietary Service to the SoftDevice] */
    // Add a custom base UUID.
    err_code = sd_ble_uuid_vs_add(&config_base_uuid, &p_config->uuid_type);
    VERIFY_SUCCESS(err_code);

    ble_uuid.type = p_config->uuid_type;
    ble_uuid.uuid = BLE_UUID_CONFIG_SERVICE;
   

    // Add the service.
    err_code = sd_ble_gatts_service_add(BLE_GATTS_SRVC_TYPE_PRIMARY,
        &ble_uuid,
        &p_config->service_handle);
    /**@snippet [Adding proprietary Service to the SoftDevice] */
    VERIFY_SUCCESS(err_code);

    // Add the RX Characteristic.
    memset(&add_char_params, 0, sizeof(add_char_params));
    add_char_params.uuid = BLE_UUID_CONFIG_ID_RX_CHARACTERISTIC;
    add_char_params.uuid_type = p_config->uuid_type;
    add_char_params.max_len = BLE_CONFIG_MAX_RX_ID_CHAR_LEN;
    add_char_params.init_len = sizeof(uint8_t);
    add_char_params.is_var_len = true;
    add_char_params.char_props.write = 1;
    add_char_params.char_props.write_wo_resp = 1;
    add_char_params.char_props.read = 1;

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

    err_code = characteristic_add(p_config->service_handle, &add_char_params, &p_config->rx_handlesID);
    if (err_code != NRF_SUCCESS)
    {
        return err_code;
    }

    // Add the RX Characteristic.
    memset(&add_char_params, 0, sizeof(add_char_params));
    add_char_params.uuid = BLE_UUID_CONFIG_MEASURMENT_INTERVAL_CHARACTERISTIC;
    add_char_params.uuid_type = p_config->uuid_type;
    add_char_params.max_len = BLE_CONFIG_MAX_RX_MEASURMENT_INTERVA_CHAR_LEN;
    add_char_params.init_len = sizeof(uint8_t);
    add_char_params.is_var_len = true;
    add_char_params.char_props.write = 1;
    add_char_params.char_props.write_wo_resp = 1;
    add_char_params.char_props.read = 1;
  
    add_char_params.read_access = SEC_OPEN;
    add_char_params.write_access = SEC_OPEN;

    err_code = characteristic_add(p_config->service_handle, &add_char_params, &p_config->rx_handlesMeasurment_interval);
    if (err_code != NRF_SUCCESS)
    {
        return err_code;
    }
    // Add the RX Characteristic.
    memset(&add_char_params, 0, sizeof(add_char_params));
    add_char_params.uuid = BLE_UUID_CONFIG_ADVERTISING_INTERVAL_CHARACTERISTIC;
    add_char_params.uuid_type = p_config->uuid_type;
    add_char_params.max_len = BLE_CONFIG_MAX_RX_ADVERTISING_INTERVA_CHAR_LEN;
    add_char_params.init_len = sizeof(uint16_t);
    add_char_params.is_var_len = true;
    add_char_params.char_props.write = 1;
    add_char_params.char_props.write_wo_resp = 1;
    add_char_params.char_props.read = 1;

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

    err_code = characteristic_add(p_config->service_handle, &add_char_params, &p_config->rx_handlesAdvertising_interval);
    if (err_code != NRF_SUCCESS)
    {
        return err_code;
    }

    // Add the RX Characteristic.
    memset(&add_char_params, 0, sizeof(add_char_params));
    add_char_params.uuid = BLE_UUID_CONFIG_LOW_ALARM_CHARACTERISTIC;
    add_char_params.uuid_type = p_config->uuid_type;
    add_char_params.max_len = BLE_CONFIG_MAX_RX_LOW_ALARM_CHAR_LEN;
    add_char_params.init_len = sizeof(uint8_t);
    add_char_params.is_var_len = true;
    add_char_params.char_props.write = 1;
    add_char_params.char_props.write_wo_resp = 1;
    add_char_params.char_props.read = 1;

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

    err_code = characteristic_add(p_config->service_handle, &add_char_params, &p_config->rx_handlesLow_alarm);
    if (err_code != NRF_SUCCESS)
    {
        return err_code;
    }

    memset(&add_char_params, 0, sizeof(add_char_params));
    add_char_params.uuid = BLE_UUID_CONFIG_HIGH_ALARM_CHARACTERISTIC;
    add_char_params.uuid_type = p_config->uuid_type;
    add_char_params.max_len = BLE_CONFIG_MAX_RX_HIGH_ALARM_CHAR_LEN;
    add_char_params.init_len = sizeof(uint8_t);
    add_char_params.is_var_len = true;
    add_char_params.char_props.write = 1;
    add_char_params.char_props.write_wo_resp = 1;
    add_char_params.char_props.read = 1;

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

    err_code = characteristic_add(p_config->service_handle, &add_char_params, &p_config->rx_handlesHigh_alarm);
    return err_code;

    // Add the RX Characteristic.
}

RE: Problem with sending data from central to peripheral

Kenneth — Thu, 29 Jul 2021 12:41:00 GMT

Can you connect using the nRF Connect for desktop : Bluetooth Low Energy app, then we can see which entry in the peer GATT table is handle 0x0003, this may be helpful in understanding what is occuring.

Kenneth

RE: Problem with sending data from central to peripheral

stopbar — Wed, 28 Jul 2021 19:25:14 GMT

Discovery seems fine to me. All the discovered handles matches handles assigned on peripheral. I think there is something wrong with sending or receiving, because even if i hardcode the handle on sending function it doesn"t work. Except this strange situation with 0x0003 value which i mentioned.

RE: Problem with sending data from central to peripheral

Darkenkade — Wed, 28 Jul 2021 19:14:02 GMT

Hard to say without seeing more of the service/discovery code. Are you assigning all the handles properly after you perform the discovery on central?