0
\$\begingroup\$

Background

Right now I have a circuit consisting of a Adafruit Huzzah Feather (ESP8266 board), an ADXL345 accelerometer, and an ATTiny85 (bare chip). The circuit is powered by a lipo battery plugged in to the huzzah with the ADXL345 and ATTINy being powered by the VBat pin (so they are always powered).

The INT1 (Interrupt 1) pin of the ADXL345 is connected to ATTiny85 and set to fire on ACTIVITY. The Tiny wakes on the rising interrupt and turns on the ENABLE pin of the Huzzah (enabling the onboard 3V3 regulator and starting the ESP8266). When the ESP8266 starts, it clears the interrupt from the ADXL345 (the two are connected via I2C) updates an ePaper display connected via SPI. The Huzzah tells Tiny it is done and ready to shutdown by changing the state on a GPIO pin. Tiny senses this, pulls the ENABLE pin low and then puts itself to sleep. circuit The LED flashes for 50ms every 2s just so I know if the Tiny is awake or sleeping.

Problem

The problem I am having is that when the Huzzah is disabled and the Tiny is sleeping, the power consumption is still around 900 uA. Moving the ammeter around, I found that about half of that is current flowing between the sleeping Tiny and disabled huzzah. The ADXL345 in measurement mode should only consume 23uA.

In the interest of simplifying things, I'd like to replace the Tiny with something simpler and even lower powered. The three things I've found by googling are:

Seems like the relay would only consume power while switching but may be overkill (I had difficulty finding a small one since I don't need 10A switching). The watchdog feature of the TPL5111 chip would be a nice-to-have thing in case the ESP locks up but not required.

Can someone with some EE experience weigh in and help this ME figure out the best way to control power via the enable pin given the above information? I'm also open to other suggestions too.

\$\endgroup\$
  • 1
    \$\begingroup\$ Welcome to EE.SE. There's a schematic tool built into the editor. It's easy to use and would replace several paragraphs of text and make the schema much clearer. If you already have a schematic you can post that but please turn off the grid if making a screenshot. \$\endgroup\$ – Transistor Nov 13 '17 at 20:44
  • \$\begingroup\$ Thanks, I'll take a look. Wasn't at my home PC, I'll work something up and edit the post \$\endgroup\$ – MattD Nov 14 '17 at 2:06
  • \$\begingroup\$ Are you using pull up resistors? When you're "asleep", do you pull the GPIO pin high or low? \$\endgroup\$ – awjlogan Nov 14 '17 at 7:34
  • 1
    \$\begingroup\$ @MattD: You've added a wiring diagram instead of a schematic. It's very pretty but tells us nothing about what it's for or how it's supposed to work. You seem to be adding a lot of data in the comments. If it's relevant to the question it should probably be in the question but the question is rather long already. I think your best bet is to summarise the question at the top with a schematic of the essential parts. It's rather unusual not to have an answer after two days and it suggests that nobody can understand it. \$\endgroup\$ – Transistor Nov 15 '17 at 22:05
  • 1
    \$\begingroup\$ The built-in schematic app on the editor toolbar has a custom component that allows you to add as many pins to it as required. You can name the device and each pin. \$\endgroup\$ – Transistor Nov 16 '17 at 13:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.