https://devzone.nordicsemi.com/f/nordic-q-a/4715/strange-behavior-of-certain-central-peripheral-combinationHi everyone, I have some strange behavior with a central peripheral combination. My central subscribes notification on the peripheral. This has a limited TX-Buffer for just one notification to prevent buffering old sensor data. The sensor data are readen-USTelligent Community 13Fri, 12 Dec 2014 08:46:24 GMThttps://devzone.nordicsemi.com/thread/16696?ContentTypeID=1Fri, 12 Dec 2014 08:46:24 GMT137ad170-7792-4731-bb38-c0d22fbe4515:685fdf7e-01c7-4abd-938f-7c6521dc8006Asbj&#248;rn<p>Do you take any actions based on the radio notifications?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/16695?ContentTypeID=1Thu, 11 Dec 2014 08:08:09 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5e798de9-e084-46ed-a946-b33ba2d551b4Simon Ferres<p>Hi, My original code is based on the multilink example from SDK 5.2.0, because I already developed some multilink applications. But this one is just a single link central. So I shortened my own application again. I use S120 version 1.0.1 All serial communication is disabled. “app_timer” module with a 5ms repeated timer is in use. Central and peripheral are initialized with intern RC LFCLK. The central scans, connects, discovers and then subscribes for notification. The same procedure worked well for many times in other applications (multilink). But there my peripherals always used 800us radio notification distance.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/16694?ContentTypeID=1Thu, 11 Dec 2014 07:40:25 GMT137ad170-7792-4731-bb38-c0d22fbe4515:830adf32-fe46-4cfc-b8c3-177985c249d5Asbj&#248;rn<p>Which code example for the S120 are you basing this on? Have you enabled anything else in the code example that what was already there? Timers? SPI? I2C? What&#39;s the connection interval between the peripheral and central?</p><div style="clear:both;"></div>