• State Verified Answer
  • Replies 4 replies
  • Subscribers 67 subscribers
  • Views 2249 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 104353
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

active current TWI

Matthias

Hello,

i am measuring the current on my nrf51822 board. While sending messages over I2C i have a current about 4.4 mA.

This should be correct? The CPU, 1v2, hfclk and i2c are using during the send/receive?

Greets Matthias

Parents
  • 0

    From the description of what you have running, then yes, you should see a current consumption around what you measure. If you need to lower it then perhaps you can shut down the MCU for longer periods or at least put into power down during transmissions.

  • 0 in reply to Asbjørn

    Which code example and from what SDK and Softdevice are you using? In the recent SDK it's called sd_app_evt_wait(), but should be same behavior. Since you are using softdevice, yes, the softdevice will handle this on it's own. When you run sd_app_evt_wait() the MCU will power down if possible (no interrupts), but as you are doing the TWI, I guess this could occur fairly often/quick. Do you get a success back from your wait_for_event()? Are you able to monitor the current consumption with an oscilloscope to see if there MCU actually powers down?

Reply
  • 0 in reply to Asbjørn

    Which code example and from what SDK and Softdevice are you using? In the recent SDK it's called sd_app_evt_wait(), but should be same behavior. Since you are using softdevice, yes, the softdevice will handle this on it's own. When you run sd_app_evt_wait() the MCU will power down if possible (no interrupts), but as you are doing the TWI, I guess this could occur fairly often/quick. Do you get a success back from your wait_for_event()? Are you able to monitor the current consumption with an oscilloscope to see if there MCU actually powers down?

Children
No Data
Related