Hi,
I want to directly enable notify without discovering the service handle, but it didn't work(return NRF_ERROR_BUSY).
Because it takes time to discover the service, and I need to communicate as soon as possible after connecting
Hi,
I want to directly enable notify without discovering the service handle, but it didn't work(return NRF_ERROR_BUSY).
Because it takes time to discover the service, and I need to communicate as soon as possible after connecting
Hi,
NRF_ERROR_BUSY indicates that another write request procedure is ongoing and that you need to wait for it to complete first (completion signaled through BLE_GATTC_EVT_WRITE_RSP). So I think it's timing related and not that you're using a hardcoded attribute handle.
Optional: with SDK 16 you can use the BLE GATT Queue module to enqueue the write request.
API reference: sd_ble_gattc_write and the MSC: GATTC Characteristic or Descriptor Value Write
Hi,
NRF_ERROR_BUSY indicates that another write request procedure is ongoing and that you need to wait for it to complete first (completion signaled through BLE_GATTC_EVT_WRITE_RSP). So I think it's timing related and not that you're using a hardcoded attribute handle.
Optional: with SDK 16 you can use the BLE GATT Queue module to enqueue the write request.
API reference: sd_ble_gattc_write and the MSC: GATTC Characteristic or Descriptor Value Write
thx Vidor Berg, thx for your reply