Searching for a UUID when trying to connect to a peripheral

[developer]

I am trying to connect to a peripheral device advertising f0000000-0114-4000-B000-000000000000 as the UUID. The peripheral adds it to the stack via sd_ble_uuid_vs_add after making it a ble_uuid128_t value. On the central device I want to hard code it so that it finds this peripheral device but am getting an error when I try to see if the service matches this UUID. I am not sure syntactically how to write out this {0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xB0, 0x00, 0x40, 0x14, 0x01, 0x00, 0x00, 0x00, 0xF0} on the central.

Thanks

[Joakim Jakobsen]

Hi developer! I'm not quite sure if I understand you correctly, are you wondering about how to implement the UUID the central should look for? Are you using any examples from one of the Nordic SDK's? I would suggest that you take a look at how it is done in the ble_app_hrs_c example.

[developer]

Yes I am using the Heart Rate Service example however my device has a vendor base UUID and I am not sure how to have the central device search for the base UUID.

[Joakim Jakobsen]

What version of the Nordic SDK are you using? Have you confirmed that the peripheral is advertising the custom 128-bit UUID you want? I'm sorry, as you are using 128-bit UUID you might want to take a look at the ble_app_uart_c example instead, which is handling a 128-bit UUID.

[developer]

I am using the Nordic SDK 13. Yes I am able to connect to the peripheral via nRFConnect and can see what the UUID is. I think the central cannot discover the service of the peripheral because I get all the way to "Service UUID not found" in ble_db_discovery when I run the program

[Joakim Jakobsen]

Did you take a look at the ble_app_uart_c example? That covers what you are trying to do.