Error in "is_UUID_present"

RE: Error in "is_UUID_present"

MartinBL — Fri, 20 May 2016 07:31:11 GMT

An answer to this is given here.

RE: Error in "is_UUID_present"

Francesca — Wed, 04 May 2016 08:47:04 GMT

Thank you very much!!Now it's working...but can you tell me another thing please?after connecting the two boards, I would like to use the db discovery module to find the service and enable notification and now I have checked that after connecting the function ble_db_discovery_start return NRF_SUCCESS but the function db_disc_handler is never called...

RE: Error in "is_UUID_present"

MartinBL — Wed, 04 May 2016 07:40:25 GMT

New edit above.

RE: Error in "is_UUID_present"

Francesca — Tue, 03 May 2016 16:07:32 GMT

I have uploaded my projects : the ble_app_uart_c is for the nrf51 that is my central (sdk11), my peripheral is a smart beacon kit that sends his temperature. When I say that it doesn't work I mean that I still get the error from is_uuid_present, NRF_ERROR_NOT_FOUND

RE: Error in "is_UUID_present"

MartinBL — Tue, 03 May 2016 14:25:19 GMT

Why didn't it work? Can you upload your code?

RE: Error in "is_UUID_present"

Francesca — Tue, 03 May 2016 14:20:06 GMT

I loaded the code but I had to include our_service.h otherwise it doesn't work.But my beacon and my nrf51 still don't connect to each other

RE: Error in "is_UUID_present"

MartinBL — Tue, 03 May 2016 13:17:16 GMT

See my edit 1 and 2 above.

RE: Error in "is_UUID_present"

Francesca — Tue, 03 May 2016 12:34:44 GMT

I have done like this:

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 = BLE_UUID_OUR_BASE_UUID;
        
    VERIFY_PARAM_NOT_NULL(p_ble_nus_c);
    VERIFY_PARAM_NOT_NULL(p_ble_nus_c_init);
    
    err_code = sd_ble_uuid_vs_add(&nus_base_uuid, &p_ble_nus_c->uuid_type);
    VERIFY_SUCCESS(err_code);
    
    uart_uuid.type = p_ble_nus_c->uuid_type;
    uart_uuid.uuid = BLE_UUID_OUR_SERVICE_UUID;

and now I have no error from sd_ble_uuid_vs_add but I stil have NRF_ERROR_NOT_FOUND from is_uuid_present

RE: Error in "is_UUID_present"

MartinBL — Tue, 03 May 2016 12:16:16 GMT

Try this:

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 = {0x23, 0xD1, 0x13, 0xEF, 0x5F, 0x78, 0x23, 0x15, 0xDE, 0xEF, 0x12, 0x12, 0x00, 0x00, 0x00, 0x00}; // <-- Put your 128-bit base UUID;
        
    VERIFY_PARAM_NOT_NULL(p_ble_nus_c);
    VERIFY_PARAM_NOT_NULL(p_ble_nus_c_init);
    
    err_code = sd_ble_uuid_vs_add(&nus_base_uuid, &p_ble_nus_c->uuid_type);
    VERIFY_SUCCESS(err_code);
    
    uart_uuid.type = p_ble_nus_c->uuid_type;
    uart_uuid.uuid = 0xABCD; // <-- Put your 16-bit service UUID here

RE: Error in "is_UUID_present"

Francesca — Tue, 03 May 2016 12:06:53 GMT

If I paste those lines in ble_nus_c_init I obtain the error NRF_ERROR_NO_MEM from the function sd_ble_uuid_vs_add

RE: Error in "is_UUID_present"

Francesca — Tue, 03 May 2016 11:30:01 GMT

Yes my base code is the ble_app_uart_c. Do you mean that I have to paste the declaration of my service UUID inside ble_nus_c_init?

ble_uuid_t        service_uuid;
    ble_uuid128_t     base_uuid = BLE_UUID_OUR_BASE_UUID;
    service_uuid.uuid = BLE_UUID_OUR_SERVICE_UUID;
err_code = sd_ble_uuid_vs_add(&base_uuid, &service_uuid.type);
    APP_ERROR_CHECK(err_code);

RE: Error in "is_UUID_present"

MartinBL — Tue, 03 May 2016 10:29:43 GMT

Hi,

I think the problem is on the central side. Since you are using is_uuid_present() I assume that you base your code on the ble_app_uart_c example? You need to add your beacon base UUID with its 16-bit service UUID to the table of UUIDs in ble_nus_c_init() located in ble_nus_c.c. The method is almost identical to the method used in the tutorial.

EDIT 1: Modify ble_nus_c_init() to look like this:

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 = BLE_UUID_OUR_BASE_UUID; // NORDIC: Use our base UUID instead
        
    VERIFY_PARAM_NOT_NULL(p_ble_nus_c);
    VERIFY_PARAM_NOT_NULL(p_ble_nus_c_init);
    
    err_code = sd_ble_uuid_vs_add(&nus_base_uuid, &p_ble_nus_c->uuid_type);
    VERIFY_SUCCESS(err_code);
    
    uart_uuid.type = p_ble_nus_c->uuid_type;
    uart_uuid.uuid = BLE_UUID_OUR_SERVICE; // NORDIC: Use our service UUID instead
    
    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_rx_handle = BLE_GATT_HANDLE_INVALID;
    p_ble_nus_c->handles.nus_tx_handle = BLE_GATT_HANDLE_INVALID;
    
    return ble_db_discovery_evt_register(&uart_uuid);
}

You also need to modify the static const ble_uuid_t m_nus_uuid variable located almost at the top of main.c:

static const ble_uuid_t m_nus_uuid = 
{
    .uuid = BLE_UUID_OUR_SERVICE,
    .type = BLE_UUID_TYPE_VENDOR_BEGIN
};

EDIT 2: Modified ble_app_uart_c example that works with finished service tutorial code: 77683-ble_app_uart_c

EDIT 3: Example is for SDK 11. Search for "// NORDIC" to see what I have modified.

EDIT 4: I have looked at your code and I think I have found the issue. After I compiled and ran your beacon code I could see that you are not advertising the the correct vendor specific UUID. You have actually placed the DFU UUID in your scan response, not the BLE_UUID_OUR_BASE_UUID. The root cause is found in advertising_init() and services_init() in the Beacon project. In services_init() you initiate three services; dfu, bcs, and our service. All three services add a 128-bit UUID to the table of UUIDs in the BLE stack, and BLE_UUID_OUR_BASE_UUID is the third UUID to be added to the table. So the solution is simply to change this line in advertising_init():

ble_uuid_t m_adv_uuids[]= {BLE_UUID_OUR_SERVICE,BLE_UUID_TYPE_VENDOR_BEGIN};

to this:

ble_uuid_t m_adv_uuids[]= {BLE_UUID_OUR_SERVICE,BLE_UUID_TYPE_VENDOR_BEGIN + 2};

then you will put the third 128-bit UUID into your scan response packet. That was the only change I had to make to get your code working (after altering the ble_nus_c.c file as above of course).

RE: Error in "is_UUID_present"

Francesca — Tue, 03 May 2016 09:49:21 GMT

Sorry if I continue on posting, but there's a possibility that something is wrong with is_uuid_present ? Because I create the service as in the tutorial, I can see the UUID from the mobile phone but I can't establish a connection using the UUID because is_uuid_present gives me error

RE: Error in "is_UUID_present"

Francesca — Mon, 02 May 2016 14:10:59 GMT

I see from the Android App an 128bit UUID, I have followed this tutorial to create it devzone.nordicsemi.com/.../ I have a question: if I would like to write in the code directly the UUID that I see in the app, which kind of variable should I use?and how to exactly write it inside the code?

RE: Error in "is_UUID_present"

Susheel Nuguru — Mon, 02 May 2016 13:28:21 GMT

The only thing I can think of is that your BLE_UUID_OUR_SERVICE_UUID is not the BLE_GAP_AD_TYPE_128BIT_SERVICE_UUID_MORE_AVAILABLE or BLE_GAP_AD_TYPE_128BIT_SERVICE_UUID_COMPLETE type. Can you sniff your advertisement packets to see if it is transmitting as 128BIT UUID AD_Type?