Discovering BLE server and characteristic is Nordic Central mode

[chandan]

Hello, I have custom BLE service and characteristic as below image.

I wanted to discover them in ble central mode. I have modified ble_hrc_c.c to validate but central not able to discover. Can anyone suggest? Also attaching code.

[Sigurd]

Hi,

have custom BLE service and characteristic

I wanted to discover them in ble central mode. I have modified ble_hrc_c.c to validate but central not able to discover.

 Since you are using a custom service/characteristic, I recommend taking a look at the central examples that also uses custom/vendor specific service/characteristic, e.g. the ble_app_uart_c and ble_app_blinky_c

[chandan]

Yes, I checked, But I am unable to make it work. I pasted my code too. I am not able to find mistakes in my code. 

[Sigurd]

E.g. the type you passed to ble_db_discovery_evt_register() is wrong, it should be BLE_UUID_TYPE_VENDOR_BEGIN. Again, since you are using a custom service/characteristic, I recommend taking a look at the central examples that also uses custom/vendor specific service/characteristic, e.g. the ble_app_uart_c and ble_app_blinky_c. 

[chandan]

I have updated but still not working. Looking into the ble_app_uart_c and ble_app_blinky_c  tooo

[Sigurd]

Did you implement the BLE Peripheral as well?

Do you have a requirement for different base UUIDs in your project?

What is usually recommended is to use a 128-bit vendor specific UUID which will look something like this "4A98xxxx-1CC4-E7C1-C757-F1267DD021E8" as a “base UUID”. The four x’s represent a field where you will insert your own 16-bit IDs for your custom services and characteristics and use them just like a predefined UUID. You will have different customs UUID for each service and characteristic but only one "base UUID".

[chandan]

I know that but  BLE Peripheral is already implemented and in production. So we can't change it