# Low power operation

**URL:** <https://forums.digi.com/t/low-power-operation/13906>\
**Category:** XBee - DigiMesh\
**Tags:** pin-sleep, xbee-pro-900hp, spi\
**Created:** [November 11, 2014, 11:21am UTC](https://forums.digi.com/t/low-power-operation/13906 "2014-11-11T11:21:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![reynaldomic](https://avatars.discourse-cdn.com/v4/letter/r/a698b9/32.png) [@reynaldomic](https://forums.digi.com/u/reynaldomic)\
**Post date:** [November 11, 2014, 11:21am UTC](https://forums.digi.com/t/low-power-operation/13906/1 "2014-11-11T11:21:13Z")

</div>

Seems asserting high SLEEP\_REQUEST pin doesn’t sleep the module if SPI lines are enabled.

It does work when using UART only, but not with SPI ( verified by measuring current draw with mm device)

is this the normal behaviour?

Documentation says one can drive sleep and transmission with SSEL only if SLEEP\_REQUEST disabled, but I actually need to have separate line to sleep the module.

---

<div class="post-metadata">

**Author:** ![mvut](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/mvut/32/31_2.png) [@mvut](https://forums.digi.com/u/mvut)\
**Post date:** [November 11, 2014, 2:28pm UTC](https://forums.digi.com/t/low-power-operation/13906/2 "2014-11-11T14:28:45Z")

</div>

Which XBee module and firmware version are you working with?

---

<div class="post-metadata">

**Author:** ![reynaldomic](https://avatars.discourse-cdn.com/v4/letter/r/a698b9/32.png) [@reynaldomic](https://forums.digi.com/u/reynaldomic)\
**Post date:** [November 11, 2014, 2:47pm UTC](https://forums.digi.com/t/low-power-operation/13906/3 "2014-11-11T14:47:45Z")

</div>

XBP9B-DMST-002 revB  
firmware: 806A (200 kbps)

there are two firmware updates, but release notes don’t say anything about it.

---

<div class="post-metadata">

**Author:** ![mvut](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/mvut/32/31_2.png) [@mvut](https://forums.digi.com/u/mvut)\
**Post date:** [November 11, 2014, 2:47pm UTC](https://forums.digi.com/t/low-power-operation/13906/4 "2014-11-11T14:47:37Z")

</div>

Try upgrading to version 8071.

---

<div class="post-metadata">

**Author:** ![mvut](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/mvut/32/31_2.png) [@mvut](https://forums.digi.com/u/mvut)\
**Post date:** [November 24, 2014, 10:41am UTC](https://forums.digi.com/t/low-power-operation/13906/5 "2014-11-24T10:41:09Z")

</div>

Try deasserting the slave select pin.

---

<div class="post-metadata">

**Author:** ![helzbo](https://avatars.discourse-cdn.com/v4/letter/h/e56c9b/32.png) [@helzbo](https://forums.digi.com/u/helzbo)\
**Post date:** [March 5, 2018, 11:43am UTC](https://forums.digi.com/t/low-power-operation/13906/6 "2018-03-05T11:43:04Z")

</div>

I am experiencing the same problem on XBee 868LP 80K with firmware 8074.

I am using SPI, and have tried to use sleep request AND slave select (by disabling sleep request) as sleep drivers. Indeed this seems to work only for UART and not for SPI. Once SPI is started, the current draw jumps up about 20mA and doesn’t come down again even when the sleep pin is driven high.

I also notice that when the UART pins are disabled from the get-go, the current draw has this 20mA offset from startup, presumably since it has immediately started up SPI because of the lack of UART.

Is there anything I can try to resolve this?

Thanks,  
Helena
