Sending log data over BLE through custom UUID Service

RE: Sending log data over BLE through custom UUID Service

ovrebekk — Wed, 26 May 2021 13:46:47 GMT

In that case I would probably just copy the ble_nus implementation, and rename it to something else (ble_log_service for instance).

As long as you make sure to rename all the non static functions and structs, and ensure that your log service uses a different UUID, it doesn't matter that you have two essentially identical services running side by side.

Alternatively you could simply add a new characteristic to your existing service, but it is probably more logical to separate the log functionality in a separate service.

Best regards
Torbjørn

RE: Sending log data over BLE through custom UUID Service

coyodha — Tue, 25 May 2021 23:12:52 GMT

Hi Torbjorn,

I planned to have DFU, Nordic NUS and Custom Log Transfer data services. So NUS is for regular data transfer channel and the custom service for a log data transfer (potentially huge amount of data) channel. Maybe similar like DFU Service implementation.

I am not sure whether it's a redundant thing to create my custom service for this?

RE: Sending log data over BLE through custom UUID Service

ovrebekk — Tue, 25 May 2021 14:21:36 GMT

Any reason you couldn't just use the ble_app_uart example directly, rather than copying this functionality into something else?

This example is made for applications where you want to send proprietary (user defined) data of varying sizes over BLE.

If you plan to go to production with this implementation you can simply change the 128-bit service UUID in order to not represent your device as a Nordic NUS device.

Best regards
Torbjørn