https://devzone.nordicsemi.com/f/nordic-q-a/9280/nrf51822-api-sequenceLet me ask you a communication sequence between nRF51822 and peripherals.We assume 5 peripherals. In a sample program for multilink, original sequence is that 5 times repetition of API request / receive reply. Dear Sir We would like to change theen-USTelligent Community 13Fri, 18 Sep 2015 03:44:37 GMThttps://devzone.nordicsemi.com/thread/34244?ContentTypeID=1Fri, 18 Sep 2015 03:44:37 GMT137ad170-7792-4731-bb38-c0d22fbe4515:824fe4da-825b-4aad-9458-d13c2d1712dfT.shib<p>Hello, Hang Buoi san Thank you for your feedback. Very appreciated. Your below comment made clear my question. &quot;you don&#39;t have to wait for response from each of them before calling other request.&quot; I have to consider source code again.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/34243?ContentTypeID=1Thu, 17 Sep 2015 15:45:12 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f3460825-9a36-422e-a518-e0b193cce925Hung Bui<p>Hi T.shib,</p> <p>With BLE there is no native way to sync between peripherals.</p> <p>What we have now is that the peripheral stack will try to response in the next connection event after it receives the request unless the characteristic has authorization requirement.</p> <p>You mentioned that &quot;original sequence is that 5 times repetition of API request / receive reply&quot; I could you point me to that code ?</p> <p>I don&#39;t see any reason you can&#39;t call a write/read request for all 5 peripheral you don&#39;t have to wait for response from each of them before calling other request.</p><div style="clear:both;"></div>