# Notecard deepsleep or mosfet cutoff

**URL:** <https://discuss.blues.com/t/notecard-deepsleep-or-mosfet-cutoff/1940>\
**Category:** Notecard API\
**Created:** [February 8, 2024, 4:52pm UTC](https://discuss.blues.com/t/notecard-deepsleep-or-mosfet-cutoff/1940 "2024-02-08T16:52:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ouaibeer](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/ouaibeer/32/418_2.png) [@ouaibeer](https://discuss.blues.com/u/ouaibeer)\
**Post date:** [February 8, 2024, 4:52pm UTC](https://discuss.blues.com/t/notecard-deepsleep-or-mosfet-cutoff/1940/1 "2024-02-08T16:52:57Z")

</div>

Hello,  
I use the notecard on my datalogger to send my data every X measurements, for example I measure every 15 minutes and I send the data every 6 or 12h. In order to save current, I have a mosfet that cuts the current to the sensors and another that cuts the current to the notecard. So when my ESP32 (TinyPico) goes into deepsleep, everything is cut off and most of the time when it take measurment the Notecard is off. An external RTC (DS3231) then switches my ESP32 back on with a precise time step. So I’m not using the Notecard’s deepsleep function. What are the advantages of using the deepsleep function rather than cutting the power completely?  
Thank you for your advices,  
Eric

---

<div class="post-metadata">

**Author:** ![zfields](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/zfields/32/29_2.png) [@zfields](https://discuss.blues.com/u/zfields)\
**Post date:** [February 8, 2024, 5:10pm UTC](https://discuss.blues.com/t/notecard-deepsleep-or-mosfet-cutoff/1940/2 "2024-02-08T17:10:27Z")

</div>

The Notecard does not need to be put into “deep sleep”, per se. Depending on the model, when it is inactive, it will automatically drop down to only consuming around 8-20uA.

For this reason, the Notecard is designed to remained powered at all times. If you cut the power, then you risk losing queued Notes, and this is an unsupported path.

You may find interesting that the Notecard has an `ATTN` (attention) pin that is designed to respond to several events, including a timer. The host can request the Notecard set the ATTN pin for `x` seconds. When you tie the ATTN pin to the EN of the host (or use it to drive a MOSFET), then it works as a sleep function for your sensing electronics while the Notecard idles at 8-20uA (less than the discharge rate of a typical LiPo battery).

Best,  
Zak

Here is a similar Q&A you might find helpful:

> [@Arduino Low power (with deep sleep) sample code for Notecard](https://discuss.blues.com/t/arduino-low-power-with-deep-sleep-sample-code-for-notecard/192/9):
>
> Sorry for the delayed response, but I have worked through several iterations to be sure to provide the best possible advice. If you’re looking to build a low-power solution, I would suggest using the Notecarrier-AL, which we’ve purpose-built for this use case, and which runs in our Airnote. Using the Notecarrier-AL gives you FULL CONTROL of the circuitry running between the Notecard and the host MCU, which allows you to tailor the power solution to your project. Then from your sketch, you will…