NUS UART Service - Getting confirmation after writing to the gatt queue?

RE: NUS UART Service - Getting confirmation after writing to the gatt queue?

Amanda Hsieh — Mon, 02 Dec 2019 11:10:20 GMT

Hi,

The idea behind the indication is that has to be confirmed by the application, the SoftDevice won't do it for you.

To do so you have to call the sd_ble_gattc_hv_confirm(..) function, after receiving the BLE_GATTC_EVT_HVX event.

The main purpose of indications is to allow the application to confirm the packet only after it has fully processed the data, and completed any operations associated with it.
If quick and efficient data transfer is more important I would recommend using notifications instead, you still have a link layer ACK to avoid packet loss/corruption.

-Amanda H.

RE: NUS UART Service - Getting confirmation after writing to the gatt queue?

Ros — Sat, 30 Nov 2019 02:41:23 GMT

Hi,

Sorry for the confusion, the question was how to implement an indication instead of sending notification (I mean after server writing or updating its own characteristic). Where would I receive an "indication confirm event" in the peripheral (server) ?

RE: NUS UART Service - Getting confirmation after writing to the gatt queue?

Amanda Hsieh — Fri, 29 Nov 2019 08:51:27 GMT

Hi,

[quote user=""]In server side, after writing to the gatt characteristic (ble_nus_c_string_send), how can confirm that the other device read the data?[/quote]

Not sure I understand the question correctly or not. Please correct me if I am wrong.

The Server cannot write to the Client. When the client sends a write request to the server, the server would send Confirmation.

Please see the following figure for data transfer:

[quote user=""]I am not sure the example uses indication or notification.[/quote]

It uses notifications. Please see Nordic UART Service Client.

-Amanda H.