https://devzone.nordicsemi.com/f/nordic-q-a/18033/gpiote-in_event-currentHello, I am currently using the GPIOTE Driver (nrf_drv_gpiote) to detect external interrupts from a sensor on a custom board using the nRF51822 with the S130 v2.0.0 SoftDevice and SDK 11. I currently have the interrupts setup to use the GPIOTE IN_EVENTen-USTelligent Community 13Wed, 07 Dec 2016 15:49:06 GMThttps://devzone.nordicsemi.com/thread/69505?ContentTypeID=1Wed, 07 Dec 2016 15:49:06 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e8db5d66-75c4-4d1c-b044-b47059e9b277Cory Mast<p>Thank you for your help Hung Bui, I added the <code>nrf_drv_gpiote_in_event_disable(PIN_IN)</code> to a scheduled event and I can now see the power drop before and after the event is executed by the scheduler.</p> <p>Thank you very much for your help!</p> <p>-Cory</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/69504?ContentTypeID=1Tue, 29 Nov 2016 10:02:08 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e4725e89-bfc4-4046-85b6-db648ad8269bHung Bui<p>Hi Cory,</p> <p>There is a chance that you were still in debug mode when you test. You would need to make sure you do a power reset after programming to get out of the debug mode, before you do any measurement.</p> <p>I just did a quick test here with the pin_change_int example in the SDK. I added __WFE() in the main loop, and then added <code>nrf_drv_gpiote_in_event_disable(PIN_IN)</code> in in_pin_handler() after that I can see the current consumption dropped after I pressed the button.</p><div style="clear:both;"></div>