Disable TX notifications

[Simon]

Hello,

the peripheral (nRF52) bonds to a central (Android nRF Connect), central enables TX notifications, and the peripheral sends over 80 bytes by NUS.

If the central does not disable TX notifications and lets disconnect occur, and because the devices were bonded, TX notification on the central will already be enabled on the next connection. If the peripheral tries another ble_nus_data_send() a NRF_ERROR_INVALID_STATE is returned. (Not looking to have the peripheral send data automatically on subsequent connections).

Is the standard procedure to have the central disable TX notifications before disconnecting, or for the peripheral upon reaching BLE_GATTS_HVN_TX_COMPLETE to some way disable TX notifications, or some way let the central know that there is no more?

thank-you,

[Simonr]

Hi

No, not that I'm aware of at least. If you always transmit the same amount of data from the peripheral, I guess you could make the central disable notifications once you have received X amount of data, but this won't do if the peripheral doesn't send the same amount of during every connection.

Best regards,

Simon

[Simon]

I added an additional send() to the trailing notification to only have 0xFFFFFFFF to signal the central that its ok to disable TX notification. Maybe central is ok with this.

thank-you,