This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

why my nrf51822-board current in sd_app_evt_wait() is up to 9uA?

  1. In sd_power_system_off(),the nrf51822-board current is 2uA;And I think the current in sd_app_evt_wait() will be ~4uA(Is it correct)?

  2. In sd_app_evt_wait(), the code is same as to in sd_power_system_off(). And I sure I close uart and there is no orther peripherals except 3 GPIO(Pin22,Pin24,Pin25) for in and 3 GPIO(Pin15,Pin21,Pin29) for out;

  3. There is no 32k crystal oscillator in my board.

  4. My IC is nrf51822_xxac. My soft-device is V2.0.1, my SDK is 12.1.0;

  5. Before sd_app_evt_wait(), My code is:

    timers_init();

    ble_stack_init();

    gap_params_init();

    services_init();

    advertising_init();

    conn_params_init();

    sd_ble_gap_adv_stop();

I have read nRF51 series current consumption guide and 《S130_SDS_v2.0.pdf》 and 《nRF51822_PS_v3.3.pdf》。But I still don't konw Where does the excess current consume。

  • Hi,

    1. Is this a custom board?
    2. Have you tried to run the same code on an nRF51 development kit?
    3. Do you see this if you run an unmodified example from our SDK?
  • Thank you!

    1. It is a custom board;
    2. I have no "nRF51 development kit";
    3. I must modified example code first then run it in my custom board;
    4. I try to porting "app_pwr_profiling" example to my custom board , the current only 2uA . It seems my full-code app has some problems, although I don't resolve it.
    1. Do you have more devices? Is it possible for you to try a different one? If you saw a difference between two devices it could e.g. be due to poor soldering and small short circuits.
    2. Can you try the unmodified ble_app_hrs example in our SDK? If you see a lower current consumption then, we know it is most likely something going on in your code and not a HW issue.
    3. Do you have sensors, etc. on your device? Are they part of your current measurements?
  • I have solve this problem with orther device. Thank you!

Related