[Nordic 8001] Conflict between requestData and lib_aci_close_remote_pipe

RE: [Nordic 8001] Conflict between requestData and lib_aci_close_remote_pipe

Nadgob — Mon, 21 Sep 2015 13:23:35 GMT

Thank you for your answer! This limitation does not affect me so much, I just wanted to know if I didn't miss something.

RE: [Nordic 8001] Conflict between requestData and lib_aci_close_remote_pipe

run_ar — Mon, 21 Sep 2015 13:15:05 GMT

You are right, this not clear from the nRF8001 PS. Unfortunately the read request is still pending (assumption, since you are sending the commands back to back). So the write request cannot be sent. This is because these are sequential request-response protocols, so the client is not allowed to send another request to the server until a respond has been received. I guess you could call this a design limitation on the nRF8001 as we could possibly have buffered the command, and sent it when the previous procedure is finished, but unfortunately we don't. I'm sorry for the inconvenience.

RE: [Nordic 8001] Conflict between requestData and lib_aci_close_remote_pipe

Nadgob — Mon, 21 Sep 2015 12:26:20 GMT

No. They are not on the same remote characteristics. It is not clear from the datasheet that I should wait for the request procedure to finish or I did not find the paragraph.

RE: [Nordic 8001] Conflict between requestData and lib_aci_close_remote_pipe

run_ar — Mon, 21 Sep 2015 12:22:28 GMT

Are these two operations done on the same remote characteristics? Regardless, you should wait until the request data procedure is finished (that is you should have gotten a response from the peer).