https://devzone.nordicsemi.com/f/nordic-q-a/25707/why-does-central-scan-2x-longer-when-receiving-advertisementsusing nRf52832 with S132 in central mode Scan-Interval= 3000 ms Scan-Window= 25 ms Monitoring the current consumption I see a 25ms wide pulse, as expected. No advertiser is nearby, so no signal is received. But as soon as an advertiser signalen-USTelligent Community 13Tue, 10 Oct 2017 08:23:45 GMThttps://devzone.nordicsemi.com/thread/101276?ContentTypeID=1Tue, 10 Oct 2017 08:23:45 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c219d282-fa06-44bd-935a-bbb012b39d59JB21<p>Petter, I measured again, and now the current pulse is 25ms wide, as expected. What was wrong the last time, I don&#39;t know. I worked on other parts of the code, perhaps new re-compilations made it happen? At least I&#39;m glad that it now works as expected. Thank you for your effort.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/101275?ContentTypeID=1Mon, 09 Oct 2017 13:33:27 GMT137ad170-7792-4731-bb38-c0d22fbe4515:941570d1-0ec6-4a32-92be-889853cf54c9Petter Myhre<p>So you didn&#39;t see a 25ms wide pulse earlier? But 40? How are you measuring this? Could you edit your question and include a capture? There should be some radio startup and post-processing, as you can see <a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.sds/dita/softdevices/s130/ble_power_profiles/scanning_event.html?cp=2_3_0_0_17_2">here</a>, but 15 ms sounds like a lot.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/101274?ContentTypeID=1Fri, 06 Oct 2017 12:54:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:510d1f45-02e7-4e7d-8dfe-3e40bcd979e5JB21<p>Just realized that I fooled myself.</p> <p>During debugging I used a LED flash during each rcv&#39;ed advertisement, and forgot removing that part of code. Now that &quot;problem&quot; is gone.</p> <p>But measuring more carefully, the curent pulse width is 40ms wide, not the expected 25ms.</p> <p>Any idea why?</p><div style="clear:both;"></div>