• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 87 subscribers
  • Views 530 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 258934
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
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

When the app_button and app_timer2 of sdk15.3 work together, the buttons cannot be triggered at the same time

Deang

I developed on sdk16.0 and found that app_button has abnormal power consumption,

so I replaced it with app_button of sdk15.3, but found that no key events were reported when multiple keys were triggered at the same time. 

Then I tracked down the reason, the debounce timer did not generate a timeout event, and there was no app_button event.

I replaced the app_timer2 with legacy version. At this time, pressing multiple buttons at the same time works well.

What should I do to ensure that app_button can be pressed simultaneously with multiple buttons and the power consumption is normal on sdk16.0?

  • 0

    Hi,

    You don't mention how the current changed or exactly how much the abnormal current consumption is versus expected. Anyways, I suspect that the higher current consumption is due to the logger module. See this thread.

    regards

    Jared

  • 0 in reply to Jared

    Hi Jared,

    Thank you for your reply. Here has been explained here why the app_button of sdk16.0 causes high power consumption.

    Does Nordic have plans to optimize the app button library? If the power consumption of the app_button library is not optimized, I think few people will use it.

  • +1 in reply to Deang

    Hi,

    I understand, but as Vidar already replied in the thread, the increased current is not really a bug but rather a result of using the library in a way that it wasn't optimized for. I would just recommend doing what you've already done by using the previous version from an earlier SDK. I will pass your feedback onwards to the developers though.

    Thank you. 

    regards

    Jared 

Related
Terms of service