# Adafruit Feather 32u4 LoRa - long transmission time after deep sleep

**URL:** <https://www.thethingsnetwork.org/forum/t/adafruit-feather-32u4-lora-long-transmission-time-after-deep-sleep/11678>\
**Category:** End Devices (Nodes)\
**Created:** [January 10, 2018, 9:55pm UTC](https://www.thethingsnetwork.org/forum/t/adafruit-feather-32u4-lora-long-transmission-time-after-deep-sleep/11678 "2018-01-10T21:55:15Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![aschroeder](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/aschroeder/32/7857_2.png) [@aschroeder](https://www.thethingsnetwork.org/forum/u/aschroeder)\
**Post date:** [January 11, 2018, 12:09am UTC](https://www.thethingsnetwork.org/forum/t/adafruit-feather-32u4-lora-long-transmission-time-after-deep-sleep/11678/13 "2018-01-11T00:09:08Z")

</div>

Couldn’t resist 🙂

After reading the linked infos I added

`extern volatile unsigned long timer0_overflow_count;`

to my sketch and after the deep sleep I inserted

`timer0_overflow_count += 3E6;`

Thats it! timer0\_overflow\_count comes from wiring.c in the arduino core and is used for micros().  
Adding at least 3E6 microseconds did the job. Could be adjusted depending on the real sleep time.

Sounds so easy - did I miss something? Maybe there will be some trouble when micros rollover.

With this modification my node now needs less than three seconds for wake up, doing some measuring, sending data and going to deep sleep again.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/adafruit-feather-32u4-lora-long-transmission-time-after-deep-sleep/11678)._
