Using a custom 16 bit service

RE: Using a custom 16 bit service

asmita_patil — Sat, 06 Jul 2019 11:40:48 GMT

can you please share code...that would be helpful..thank you

RE: Using a custom 16 bit service

Roger Clark — Mon, 07 Aug 2017 11:18:15 GMT

Thanks

I'll printf the values and post them

RE: Using a custom 16 bit service

endnode — Mon, 07 Aug 2017 10:49:40 GMT

OK, little bit of highlight syntax and the values you put into function call params would help, cannot say anything to this;)

RE: Using a custom 16 bit service

Roger Clark — Mon, 07 Aug 2017 08:05:29 GMT

In rx_char_add

sd_ble_gatts_characteristic_add(p_c16s->service_handle, &char_md, &attr_char_value, &p_c16s->rx_handles);

returns code 7, which I think is NRF_ERROR_INVALID_PARAM

I've actually decided to just use a 128 bit UUID and not bother trying to implement the temperature 16 bit service that I'd initially intended to do.

But I suppose its best if I do get a solution to this in case I ever need to make another 16 bit service.

RE: Using a custom 16 bit service

endnode — Mon, 07 Aug 2017 07:12:25 GMT

Hi Roger, what is exactly the line failing with error code?

RE: Using a custom 16 bit service

Roger Clark — Mon, 07 Aug 2017 04:47:46 GMT

Guys

I've been trying to do the same thing as r00li

Except if I remove sd_ble_uuid_vs_then the calls to sd_ble_gatts_service_add in my 16 bit service init cause the application to hang

I've tracked the problem down to when it adds the UART RX characteristic

as its returning NRF_ERROR_INVALID_PARAM

But if I leave the sd_ble_uuid_vs_add in place, it seems to work OK.

Why does sd_ble_uuid_vs_add need to be removed ?

RE: Using a custom 16 bit service

r00li — Sun, 16 Jul 2017 21:23:08 GMT

Oh wow. That was easy. Removed the sd_ble_uuid_vs_add calls, set the UUID type to BLE_UUID_TYPE_BLE and that was it. Of course I forgot to set the type for advertising so it still didn't work, but after I fixed that it started working like a charm. Thank you!

RE: Using a custom 16 bit service

endnode — Sun, 16 Jul 2017 19:51:53 GMT

If you want to add 16-bit UUID it means the base is well known BT SIG 128-bit UUID defined in their specification. All UUIDs in Nordic stacks (Soft Device) are made of two parts: 128-bit base and 16-bit "actual" UUID. The only base which is by default present in the stack is (logically) the BT SIG one. So if you really want to use 16-bit UUID then you should use BLE_UUID_TYPE_BLE as base. Don't add anything through sd_ble_uuid_vs_add function then.