Skip to content
  • Blog
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Community Forum

  1. Home
  2. Categories
  3. ULPNode
  4. ULPNode Low Power - How to calculate reserve capacitor capacity?

ULPNode Low Power - How to calculate reserve capacitor capacity?

Scheduled Pinned Locked Moved ULPNode
1 Posts 1 Posters 1.5k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    mj
    wrote on last edited by mj
    #1

    Hello,
    after building my first version od DC/DC booster as described here I have testes few capacitors 33uF, 45uF and at last 1000uF (electrolytic, low ESR) - it needs about 60ms to get fully charged.
    Test circuit with white LED 20mA lightup + fading. Time I got between recharging is about 1m30s.

    My question is: Is there any equation to calculate optimal capacity/charge time, to achieve best power efficiency?

    Correct me if I'm wrong in my approach to find size of reserve capacitor with charge time equal to time I need to take all measurements, send data with RF module and receive ACK and go to sleep.
    So not to draw power from booster only to run uC (atmega328p) while capacitor is already charged?

    Right now I have made self running power circuit ( BATT -> MCP1640 -> NCP302 + IRF7410PbF) where time is regulated by capacitor attached to pin 5 (CD) of ncp302, so system is autonomous.

    In context of regulating time before measurements I think it's a must to do it on uC site, because I don't see reason to change capacitors for every time change.

    So:

    • wake up uC
    • increase counter
    • go to sleep
    • every X times wake up all devices take measurement
    • reset counter
    • go to sleep
      is the best and only approach.

    This X should be given to node form Gateway during first start or config.

    Any comment about capacity and wake approach?

    1 Reply Last reply

    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

    With your input, this post could be even better 💗

    Register Login
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    0

    Online

    5.8k

    Users

    565

    Topics

    5.3k

    Posts

    Top Topics

    Popular Tags

    teleinfo
    25 topics
    arduino
    19 topics
    remora
    16 topics
    esp8266
    10 topics
    arduipi
    10 topics
    raspberry
    8 topics
    wifinfo
    7 topics
    broadcast
    7 topics
    Copyright © 2022 Charles-Henri Hallard | Return to blog page | Powered by NodeBB
    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Blog
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups