https://devzone.nordicsemi.com/f/nordic-q-a/5852/pwm-in-nrf51822Hi, I am using nRF51822 to generate two channels PWM to control motors. Softdevice is V5.2.1. But I found the the Blue tooth connection sometimes dead if the PWM frequency is high. I set the frequency to 300Hz it ran well, but when I set the PWM frequencyen-USTelligent Community 13Fri, 06 Mar 2015 10:31:34 GMThttps://devzone.nordicsemi.com/thread/20429?ContentTypeID=1Fri, 06 Mar 2015 10:31:34 GMT137ad170-7792-4731-bb38-c0d22fbe4515:010fff43-19cf-481d-97a9-111066d58a44Stefan Birnir Sverrisson<p>Hi</p> <p>Softdevice 5.2.1 is rather old softdevice. Is it because you have older nRF51 hardware that you are using the 5.2.1 softdevice. If you are using the latest <a href="https://github.com/NordicSemiconductor/nrf51-pwm-library">PWM library</a>, then it is developed with SDK 7 which runs with softdevice 7.1, see the <a href="https://www.nordicsemi.com/eng/nordic/Products/nRF51822/ATTN-51/41917">nRF51 compatibility matrix</a>.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/20428?ContentTypeID=1Wed, 04 Mar 2015 12:04:22 GMT137ad170-7792-4731-bb38-c0d22fbe4515:794953ed-b7c3-4b16-826e-800e43a13262Annim<p>Hi,</p> <p>PWM is not affecting you Bluetooth connection at all. It is the power_manage() api call which pulls the device for a sleep and from this the BUTTON or say WAKEUP_BUTTON should be configured.</p> <p>If you want to not to loose the BLE connection and PWM activity also goes on, then i shall say remove the power_manage() call from the end of main context loop and place it where you find it suitable to save energy.</p> <p>Apart from this, be careful about the timers you are using to get PWM running as softdevice will occupy the timer0. So drive the PWm on other left timers with priority 3 which is the leat app priority.</p><div style="clear:both;"></div>