Characteristic Write followed by inline read (eg write command, read Ack/Nak response)https://devzone.nordicsemi.com/f/nordic-q-a/43415/characteristic-write-followed-by-inline-read-eg-write-command-read-ack-nak-responseHi I am back on the firmware end of my project after several months doing the PC and Xamarin ends in C#... Trying to remember my C...! My device has 3 MCU&#39;s incl the Nordic as well as a mobile App (via BLE) and a PC (via USB). EG I have BLE, USBen-USTelligent Community 13Thu, 07 Feb 2019 14:55:52 GMTRE: Characteristic Write followed by inline read (eg write command, read Ack/Nak response)https://devzone.nordicsemi.com/thread/169961?ContentTypeID=1Thu, 07 Feb 2019 14:55:52 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3293891a-5fe3-4c54-9e70-b8ae046fa0ebEdvin<p>Hello Nigel,</p> <p>I am not sure whether I actually understand your question. Is this a matter of latency, or just cleaning up the code?</p> <p></p> <p>Regardless, it seems a bit messy turning on and off notifications all the time. I don&#39;t understand the need to do this, but maybe that is the part of the question that I don&#39;t understand. What are your ACK/NACK and datawaiting flags used for?</p> <p></p> <p>Is it possible to skip the ACK/NACK in the BLE part of your application, and just send the header and payload in one message? This will reduce the latency. Then check the header and decide whether or not to pass the payload on to one of the other peripherals?</p> <p></p> <p>Best regards,</p> <p>Edvin</p><div style="clear:both;"></div>