https://devzone.nordicsemi.com/f/nordic-q-a/7161/odd-ble-notification-problem-windows-8-1So I have my nRF51822 updating the characteristic value and sending notifications once every time I receive a radio notification. uint8_t readings[20] = { 0, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18 }; void bleRadioNotificationHandleren-USTelligent Community 13Thu, 02 Jul 2015 11:43:19 GMThttps://devzone.nordicsemi.com/thread/25309?ContentTypeID=1Thu, 02 Jul 2015 11:43:19 GMT137ad170-7792-4731-bb38-c0d22fbe4515:dbfb44ab-289e-4f94-855f-ffae82cab905ImQ009<p>After reading the Windows BLE API headers that haven&#39;t been documented on MSDN I found out I was just using it wrong.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/25308?ContentTypeID=1Fri, 22 May 2015 12:02:03 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d22d0ab7-3310-41e4-a5cd-5dfd781bcc26Stefan Birnir Sverrisson<p>Hi</p> <p>You should try to set the max and min connection interval to a slightly different value in order to give the central device (win 8.1) a little choice on which value to set for the link. Otherwise it might not change the connection interval at all. See <a href="https://devzone.nordicsemi.com/question/12545/update-connection-parameter-programmatically/">this thread</a> how the connection parameter negotiation works. Also see <a href="https://devzone.nordicsemi.com/question/2898/knowing-the-connection-interval/">this thread</a> on how to identify the actual connection interval on the link.</p> <p>I am not sure what is happening on win 8.1 side. Probably the best way to find out is to sniff the on air packages with e.g. the <a href="https://www.nordicsemi.com/eng/nordic/Products/nRF51822/nRF-Sniffer/26386">nRF sniffer</a>. What happens when you try to transmit only a single packet? Try to change the parameters mentioned <a href="https://devzone.nordicsemi.com/question/28442/nrf51-dk-connection-event-packet-length/">here</a> to see what happens.</p><div style="clear:both;"></div>