SAADC on SDK12.3

RE: SAADC on SDK12.3

Jørgen Holmefjord — Wed, 14 Jun 2017 07:47:16 GMT

The power management module should provide more functionality than the sleep functions, but you should still be able to put the device in sleep mode by calling sd_app_evt_wait()/__WFE() directly.

RE: SAADC on SDK12.3

Dave_couling — Tue, 13 Jun 2017 18:42:21 GMT

Thats what I figured regarding the low power setting. I recently added the nrf_pwr_mgmt.h module to my project. Added nrf_pwr_mgmt_run(); to the loop in my BLE thread (i used FreeRTOS). This seems to have brought down the power consumption. I'm coming from SDK 11, where only app_sched_execute(); & sd_app_evt_wait(); were required to put the system to low power sleep. Curious as to why this was changed and why its not implemented by default.

RE: SAADC on SDK12.3

Jørgen Holmefjord — Tue, 13 Jun 2017 06:32:02 GMT

Hi,

When using the low power mode of the SAADC driver in SDK > v12.0.0, it will automatically uninit the peripheral between sampling. Unless you want to disable the interface completely, you should not have to call nrf_drv_saadc_uninit() manually.

~3-4 mA sounds too high to come from the SAADC peripheral alone. You will have the EasyDMA current of ~1.5mA and ~700uA extra when sampling, so depending on your sample rate and method of triggering sampling, you should end up at less than 3mA. Are you putting the device in sleep mode whenever possible? Do you power cycle the device after flashing, to make sure it is not in debug mode?

I recently updated this GitHub example to SDK 13, could you have a look at it and compare it to your application? Could you also upload your entire code for debugging?

Best regards,

Jørgen