https://devzone.nordicsemi.com/f/nordic-q-a/29648/sdk-14-0-power-consumptionHi We are using sdk version 12.2.0 and trying to change it to sdk 14.0.0. However, when I measured the power while converting the code, ppk confirmed that the sdk 14.0.0 version consumes much more power than the existing sdk 12.2.0 version. I woulden-USTelligent Community 13Tue, 23 Jan 2018 10:29:15 GMThttps://devzone.nordicsemi.com/thread/117746?ContentTypeID=1Tue, 23 Jan 2018 10:29:15 GMT137ad170-7792-4731-bb38-c0d22fbe4515:236fbab5-aa78-4739-805b-df6514952a55hongpal<p>Thank you. I will go to the company tomorrow and I will try.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/117745?ContentTypeID=1Tue, 23 Jan 2018 10:12:30 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7baa0bd2-31c1-4c05-87ac-a4ec612d5f73MartinBL<p>Hi,</p> <p>I see the same thing and it is related to this: <a href="https://devzone.nordicsemi.com/question/163689/nrf_log-uart-draws-300ua/">nRF_LOG UART draws ~300uA</a></p> <p>The CSCS example uses the Loger module with UART as backend. @Stian &#39;s workaround explained in the link above should do the trick.</p> <p>Before workaround (average 1.45mA): <img src="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/sdk1420.PNG" alt="adf" /></p> <p>Notice that there seems to be a base current of ~500uA. This is because the high frequency clock is left running by the UART driver unless you implement the workaround.</p> <p>After workaround (average 742uA):</p> <p><img src="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/sdk1420-after-fix.PNG" alt="asdf" /></p><div style="clear:both;"></div>