Why no ble_hts_c in ble_services?

[Manish]

Hello,

I want to implement BLE central for Health Thermometer Service using nRF51822 with S130 SD

I used the example ble_app_hrs_c as a reference, but I don't see an equivalent of ble_hrs_c.h for hts.

What am I missing? Should I just read the data as generic GATT client?

[Jørgen Holmefjord]

Hi,

There is no Health Thermometer Service central application in the SDK, therefore there is not any source/header files for this either. You will have to implement your own central for HTS. This should be quite similar to the other central applications, so you should be able to get some ideas from the other files.

Best regards,

Jørgen

[Manish]

Thanks for the clarification!

Just curious, on what basis are some centrals present and the other absent in the SDK? Based on practically how common they are?

[Jørgen Holmefjord]

All examples in the SDK are created to show common use-cases and popular applications that many users desire. Most BLE service clients will be similar, so creating a single example for each service will be redundant. As you typically have to modify the example to fit your application anyway, it should not be more work changing to the correct services. We are happy to help with any problems you should encounter during your development process, just remember to search for previous answers first!

[Manish]

Just to clarify, I wasn't looking for an example of HTS central, I was looking the implementation in the SDK (infocenter.nordicsemi.com/index.jsp

I am little confused though (probably because all BLE I know if based only on nRF SDKs) - in S130 SDS v2.0 Table 15 which lists 'supported profiles and services' mentions that the SD supports "Health Thermometer" and that it doesn't provide "Internet Protocol Support". Since HTS central is not part of the SDK's BLE Services module but it can be implemented by user, does this mean that IP support can't be implemented by user at all until the SD supports it?

[Jørgen Holmefjord]

I understand, but all service implementations in the SDK is used in the examples.

Internet Protocol Support Profile (IPSP) requires L2CAP Connection Oriented Channels, which is not currently supported by our softdevices. If you want IP support, you can take a look at nRF5 IoT SDK. This includes a modified softdevice that support L2CAP CoC and IPSP. Note that this softdevice is only for prototyping purposes. We are working hard on getting ready a production grade softdevice, with support for connection oriented channels.