Format of data sent from central in Current Time Service.

RE: Format of data sent from central in Current Time Service.

paul — Tue, 09 Mar 2021 20:35:22 GMT

Glad to know I'm not the only one. Thanks for the reply. I'll continue to use the example as you suggest.

RE: Format of data sent from central in Current Time Service.

tesc — Tue, 09 Mar 2021 20:19:41 GMT

Hi,

I am afraid I did not figure out where to find those definitions, but you could always use our Current Time Application example as reference, regarding what are the fields and how it is encoded.

Regards,
Terje

RE: Format of data sent from central in Current Time Service.

paul — Tue, 02 Mar 2021 17:50:44 GMT

Hi Terje,

Apologies for reviving this thread, but I have the same question about the Current Time Service, and the format of the characteristic data.

Going to the link you mentioned, one finds a document called CTS_SPEC_V1.1.0. This document does not define the actual content of the characteristics. Do you know where the characteristic bytes are actually defined now?

thanks,

Paul

RE: Format of data sent from central in Current Time Service.

tesc — Wed, 17 Jun 2020 10:40:02 GMT

Hi,

The values are printed to log using the function current_time_print() in main.c. The values are provided from the Current Time Service client event, and the parsing itself is implemented in ble_cts.c.c.

You can store the values in the application as you wish, yes. For instance store them to variables instead of printing them to log.

Data formats are specified from the Bluetooth SIG, see e.g. the Current Time Service specification which you can obtain from https://www.bluetooth.com/specifications/gatt/

Regards,
Terje