RE: Events/result codes when notifications fail

obbe — Fri, 05 Jul 2019 08:34:12 GMT

Just the answer I needed. Thanks!

RE: Events/result codes when notifications fail

ovrebekk — Thu, 04 Jul 2019 12:38:20 GMT

The link layer sends notifications as commands rather than requests, which means that they don't have an explicit timeout, and no timeout event will be generated.

The only way a notification can be lost is if you have a link loss, which is what is happening in your case, triggering the disconnected event.

While you don't get any events on a missing notification, you will get an event when one or more notifications are ACK'ed by the client. In this case the BLE_EVT_TX_COMPLETE will be sent, informing you that a certain number of notifications were successfully sent.

If you send a notification and see that this event never occurs then it means the notification still hasn't been ACK'ed by the client, and is pending in the SoftDevice buffers. If this happens over several connection intervals it is typically a sign that the link is poor.

Best regards
Torbjørn