When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

NORDIC_SUR — Thu, 11 Apr 2019 13:52:40 GMT

I can get service UUID,but I can't get 128 bit char UUID

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Holmes — Thu, 11 Apr 2019 08:54:15 GMT

Used some other methods，I get the handle directly.

By the uuid , I can't discovery the service.

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

NORDIC_SUR — Wed, 03 Apr 2019 03:43:11 GMT

Hi,Holmes

did you find how to solve this problem?I have the same question as you.

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Holmes — Fri, 29 Mar 2019 07:17:39 GMT

I have tried,but still can't discovery

Are there any ble_central examples like the nRF Connect APP? No specific services , it can read and write data to any service and characteristic?

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Andy — Thu, 28 Mar 2019 11:12:08 GMT

Can you try changing this:

//ble_uuid128_t   service_base_uuid = HXJ_BASE_UUID_FEE9;
ble_uuid128_t   service_base_uuid = HXJ_BASE_UUID;

I don't think it should make a difference but who knows. I can't see anything else weird with your code.

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Holmes — Thu, 28 Mar 2019 11:00:59 GMT

Yes,I can discovery 0x1800(the p_evt->params.discovered_db.char_count is 5 and char uuid is 0x2axx),and the service which marked blue I can discovery too.So I think my discovery module is work.

But the red mark I can't discovery.

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Andy — Thu, 28 Mar 2019 10:39:24 GMT

Can you try to discover the Generic Access Service?

BLE_UUID_BLE_ASSIGN(serviceFEE9, 0x1800);
APP_ERROR_CHECK(ble_db_discovery_evt_register(&serviceFEE9));

You should at least be able to discover that one. Just to check that the discovery module at least works.

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Holmes — Thu, 28 Mar 2019 10:05:29 GMT

This does not matter , beacuse I already know that the problem is on init function.

What I want to know now is why I can receive data by nRF Connect APP , but when I add the same UUID to 52832 , I can't discovery it.

Please refer to my reply above.

Thanks

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Andy — Thu, 28 Mar 2019 08:39:33 GMT

0x11 isn't invalid data, it's busy. That probably means that the discovery procedure had already started or something like that. You will have to check which function exactly is returning that error.

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Holmes — Thu, 28 Mar 2019 02:37:11 GMT

When I register both 0xfee8 and 0xfee9 at the same time by ble_db_discovery_evt_register() function. The value of p_evt->evt_type is 0x01.p_evt->params.err_code is 0x0011 (NRF_ERROR_INVALID_DATA) What does this error mean?

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Holmes — Wed, 27 Mar 2019 08:37:21 GMT

I found I can't insert the code success, let me try again:

        case BLE_GAP_EVT_CONNECTED:
        {
            ble_gap_evt_adv_report_t const * p_adv_report = &p_gap_evt->params.adv_report;
            
            err_code = ble_nus_c_handles_assign(&m_ble_nus_c[p_gap_evt->conn_handle], p_ble_evt->evt.gap_evt.conn_handle, NULL);
            APP_ERROR_CHECK(err_code);

            // start discovery of services. The NUS Client waits for a discovery result
            err_code = ble_db_discovery_start(&m_db_disc[p_gap_evt->conn_handle], p_ble_evt->evt.gap_evt.conn_handle);
            APP_ERROR_CHECK(err_code);
        }
            break;

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Holmes — Wed, 27 Mar 2019 08:26:09 GMT

The 0xfee9 service UUID is the only service I want to discovery. I had discovery other services successful.

This is the code I used to discovery in my central application , this is in the ble_evt_handler() function:

        case BLE_GAP_EVT_CONNECTED:
        {
            ble_gap_evt_adv_report_t const * p_adv_report = &p_gap_evt->params.adv_report;
            
            err_code = ble_nus_c_handles_assign(&m_ble_nus_c[p_gap_evt->conn_handle], p_ble_evt->evt.gap_evt.conn_handle, NULL);
            APP_ERROR_CHECK(err_code);

            // start discovery of services. The NUS Client waits for a discovery result
            err_code = ble_db_discovery_start(&m_db_disc[p_gap_evt->conn_handle], p_ble_evt->evt.gap_evt.conn_handle);
            APP_ERROR_CHECK(err_code);
        }
            break;
I am making changes based on ble_app_uart_c project.

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Andy — Wed, 27 Mar 2019 07:39:45 GMT

That´s not what I´m asking. I´m asking if you're also trying to discover other services in your central application. And how are you starting the discovery in your central application?

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Holmes — Wed, 27 Mar 2019 02:36:17 GMT

There are many service in the BLE peripheral device. The BLE peripheral UUID I can get from nRF Connect APP, see the picture below please.

The blue mark (fee8) is the UUID I can discovery . The red mark (fee9) is the UUID I want to discovery , but failed.The way I used to discovery the two uuid(fee8 and fee9) is the same(Like the init function above).

In the nRF Connect APP ,when I click the yellow mark, I can receive the data I want.

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Andy — Mon, 25 Mar 2019 09:04:47 GMT

If you don't get 0x01 you're not getting any errors. 0x02 means that the service was not found. The error code is in a union, so what you're seeing is actually the UUID in params.discovered_db, not the err_code.

Is that the only service you're trying to discover? Have you successfully discovered other services before? How are you starting the discovery?

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Holmes — Mon, 25 Mar 2019 08:48:24 GMT

I am not sure under what circumstances 0x01 will appear.This seems to be related to different UUID I set.

I tested it a few times, but 0x01 did not appear.May be that my parameter error occurred during the test.

When I get 0x02, the p_evt->params.err_code looks like uuid.type<<8|16bit uuid.

What I want to know is why I can read the 128bit characteristi UUID by nRF Connect APP but I can't discover it by the function ble_db_discovery_start().Even though I have added the 128bit uuid to the list.

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Andy — Fri, 22 Mar 2019 06:49:32 GMT

If you get 0x01 as the event type that indicates that you're getting a SoftDevice error somewhere. What's the error code you get? You can check it in p_evt->params.err_code

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Holmes — Fri, 22 Mar 2019 02:43:31 GMT

Hi Andy

Thank you for your reply.

I had modify my init function as you say , but still failed.

This is my init code:

#define HXJ_BASE_UUID                   {{0xfb,0x34,0x9b,0x5f,0x80,0x00,0x00,0x80,0x00,0x10,0x00,0x00,0x00,0x00,0x00,0x00}}
#define HXJ_BASE_UUID_FEE9              {{0xfb,0x34,0x9b,0x5f,0x80,0x00,0x00,0x80,0x00,0x10,0x00,0x00,0xe9,0xfe,0x00,0x00}}
#define HXJ_BASE_UUID_CHAR_RX           {{0x00,0x96,0x12,0x16,0x54,0x92,0x75,0xb5,0xa2,0x45,0xfd,0xab,0x39,0xc4,0x4b,0xd4}}
#define HXJ_BASE_UUID_CHAR_TX           {{0x01,0x96,0x12,0x16,0x54,0x92,0x75,0xb5,0xa2,0x45,0xfd,0xab,0x39,0xc4,0x4b,0xd4}}

uint32_t ble_nus_c_init(ble_nus_c_t * p_ble_nus_c, ble_nus_c_init_t * p_ble_nus_c_init)
{
    uint32_t      err_code;
    ble_uuid_t    uart_uuid;
    ble_uuid128_t nus_base_uuid =HXJ_BASE_UUID;//NUS_BASE_UUID;
    
    ble_uuid128_t   service_base_uuid = HXJ_BASE_UUID_FEE9;
    ble_uuid128_t   characteristicRX_base_uuid = HXJ_BASE_UUID_CHAR_RX;
    ble_uuid128_t   characteristicTX_base_uuid = HXJ_BASE_UUID_CHAR_TX;
    
    VERIFY_PARAM_NOT_NULL(p_ble_nus_c);
    VERIFY_PARAM_NOT_NULL(p_ble_nus_c_init);
    p_ble_nus_c->conn_handle           = BLE_CONN_HANDLE_INVALID;
    p_ble_nus_c->evt_handler           = p_ble_nus_c_init->evt_handler;
    p_ble_nus_c->handles.nus_tx_handle = BLE_GATT_HANDLE_INVALID;
    p_ble_nus_c->handles.nus_rx_handle = BLE_GATT_HANDLE_INVALID;

    APP_ERROR_CHECK(sd_ble_uuid_vs_add(&service_base_uuid, &serviceFEE9.type));
    APP_ERROR_CHECK(sd_ble_uuid_vs_add(&characteristicRX_base_uuid, &charRX.type));
    APP_ERROR_CHECK(sd_ble_uuid_vs_add(&characteristicTX_base_uuid, &charTX.type));
    
    serviceFEE9.uuid=0xfee9;
    charRX.uuid=0x0;
    charTX.uuid=0x0;
    
    APP_ERROR_CHECK(ble_db_discovery_evt_register(&serviceFEE9));
    
    return err_code;
}

All of the four 128bit UUID ,I can get it by nRF Connect APP. Red mark is UUID.

I tried a lot of values for serviceFEE9.uuid、charRX.uuid and charTX.uuid in the init function。But in the ble_nus_c_on_db_disc_evt() , the value of p_evt->evt_type has not been BLE_DB_DISCOVERY_COMPLETE.(often 0x01、0x02、0x010A)

But in the nRF Connect APP , I can receive data when I click the blue mark.

Look forward to your reply

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Andy — Thu, 21 Mar 2019 10:02:37 GMT

Also, the ble_uuid_t variables should be global to that file (i.e. your_service and your_characteristic), so that you have access to those variables in the db_evt_handler as well.

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Andy — Thu, 21 Mar 2019 09:57:57 GMT

This is what you need, modify it as you see fit:

In your init function:

ble_uuid128_t   your_service_base_uuid = YOUR_SERVICE_BASE_UUID;
ble_uuid128_t   your_characteristic_base_uuid = YOUR_CHARACTERISTIC_BASE_UUID;
APP_ERROR_CHECK(sd_ble_uuid_vs_add(&your_service_base_uuid, &your_service.type));
APP_ERROR_CHECK(sd_ble_uuid_vs_add(&your_characteristic_base_uuid, &your_characteristic.type));

your_service.uuid = BLE_UUID_YOUR_SERVICE;
your_characteristic.uuid = BLE_UUID_YOUR_CHARACTERISTIC;

APP_ERROR_CHECK(ble_db_discovery_evt_register(&your_service));

In your db_evt_handler:

if (p_evt->evt_type == BLE_DB_DISCOVERY_COMPLETE) {
	if ((p_evt->params.discovered_db.srv_uuid.uuid == your_service.uuid) &&
		(p_evt->params.discovered_db.srv_uuid.type == your_service.type)) {
		for (uint8_t i = 0; i < p_evt->params.discovered_db.char_count; i++) {
			if (p_evt->params.discovered_db.charateristics[i].characteristic.uuid.type == your_characteristic.type) {
				if (p_evt->params.discovered_db.charateristics[i].characteristic.uuid.uuid == your_characteristic.uuid) {
					cccd_handle  = p_evt->params.discovered_db.charateristics[i].cccd_handle;
					value_handle = p_evt->params.discovered_db.charateristics[i].characteristic.handle_value;
				}
			}
		}
	}
}

That should work. If it doesn't, my bet is that your calls to ble_db_discovery_evt_register are returning errors. Check the return codes of those functions to verify that they are returning NRF_SUCCESS.

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Holmes — Thu, 21 Mar 2019 06:16:47 GMT

Hi Simonr

The parameters p_uuid is 16bit UUID , but the characteristic I want to read is 128bit UUID . And it is totally different from the Primary Service UUID.

How do I use sd_ble_gattc_char_value_by_uuid_read() function? Can you give me a example?

This is my code , but I can read no data.

void getCHAR(int handle)
{
    ble_gattc_handle_range_t handle_range;
    ret_code_t            err_code;
    ble_uuid_t         uuid;
    uuid.uuid=0xc439;               
    uuid.type=2;
    
    handle_range.start_handle=1;
    handle_range.end_handle=50;
    err_code=sd_ble_gattc_char_value_by_uuid_read(handle,&uuid,&handle_range);
    APP_ERROR_CHECK(err_code);
}

In the ble_evt_handler()

case BLE_GAP_EVT_CONNECTED:
{
    ble_gap_evt_adv_report_t const * p_adv_report = &p_gap_evt->params.adv_report;
    NRF_LOG_INFO("Connected to target");

    getCHAR(p_ble_evt->evt.gap_evt.conn_handle);
}
break;

case BLE_GATTC_EVT_CHAR_VAL_BY_UUID_READ_RSP:
{
    int i=0;
    uint8_t data[20][100];
    static int cnt=0;
    
    memset(data,0,sizeof(data));
    
    for(i=0;i<p_ble_evt->evt.gattc_evt.params.char_val_by_uuid_read_rsp.count;i++)
    {
        memcpy(data[i],p_ble_evt->evt.gattc_evt.params.char_val_by_uuid_read_rsp.handle_value,p_ble_evt->evt.gattc_evt.params.char_val_by_uuid_read_rsp.value_len);
    }                 
}
break;

Look forward to your reply

Thanks

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Simonr — Wed, 20 Mar 2019 13:38:11 GMT

Could you try the sd_ble_gattc_char_value_by_uuid_read function? If you are not able to get this working, please send a snippet of your code, to show me how exactly you are reading the UUID.

Best regards,

Simon

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Holmes — Wed, 20 Mar 2019 10:21:30 GMT

I can find the 128bit characteristic UUID by sd_ble_gattc_attr_info_discover()

But I can not find the 128bit characteristic UUID by the function ble_db_discovery_start(). Although I had add the 128bit characteristic uuid by sd_ble_uuid_vs_add() and ble_db_discovery_evt_register(). But in the function of ble_nus_c_on_db_disc_evt() the p_evt->evt_type is 0x01 or 0x02 or 0x010A but it is not 0x00 ,and p_evt->params.discovered_db.char_count still 0.

Look forward to your help

Thanks

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Simonr — Wed, 20 Mar 2019 09:44:21 GMT

So what you want is the UUID found by sd_ble_gattc_attr_info_discover()?

If you add the ble_cus.c file, and the necessary header files from the aforementioned example to your project you should be able to add UUIDs by calling the ble_cus_init function in your main file.

Best regards,

Simon

RE: When 128bit characteristic UUID is different form 128bit service UUID，how to discovery it?

Holmes — Wed, 20 Mar 2019 06:14:39 GMT

Hi Simonr

To use function sd_ble_gattc_attr_info_discover() I can get the same 128bit-UUID as the Android app.

But when I add this UUID to list by function sd_ble_uuid_vs_add() , I can't get BLE_DB_DISCOVERY_COMPLETE result.

You can see the code at the top of the problem.

Look forward to your reply

Thanks