https://devzone.nordicsemi.com/f/nordic-q-a/10688/why-does-pwm-consume-so-much-powerAccording to the nrf52 product specifications, the PWM peripheral consumes 200 uA running at 16MHz. But a TIMER in combination with PPI an GPIOTE consumes 30.1uA max. Why the big difference?en-USTelligent Community 13Thu, 10 Dec 2015 11:51:25 GMThttps://devzone.nordicsemi.com/thread/39907?ContentTypeID=1Thu, 10 Dec 2015 11:51:25 GMT137ad170-7792-4731-bb38-c0d22fbe4515:abf8fb82-10d5-4f7d-bc42-5a1c88ad6b60Ole Bauck<p>No, not that I know of. The current PWM driver in the SDK does not use the PWM peripheral, but TIMER+GPIOTE+PPI, so you may save some power using that one.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/39906?ContentTypeID=1Wed, 09 Dec 2015 07:58:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:64b3aade-b8c2-44d9-b3be-7c5f2d0ea639Martijn<p>ok, I will wait for the final Product Specification. Is there a way to disable the DMA feature and just use a fixed duty cycle? I know the HFCK is running, but that is for both solutions.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/39905?ContentTypeID=1Tue, 08 Dec 2015 15:34:56 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a81a3124-9e62-4d9c-82ce-9942e8ebd437Ole Bauck<p>The PWM peripheral have more features than using TIMER, PPI and GPIOTE. One of these features is DMA to automatically update the PWM. Therefore the PWM will consume more current. In addition, the Product Specification is an objective Product Specification and the current draw may not be the same as real measured values.</p> <p>For both peripherals, the high frequency clock (HFCLK) will also be running, so there will be some additional current draw.</p><div style="clear:both;"></div>