# Change Timermillis() period on downlink for STM32L0

**URL:** <https://www.thethingsnetwork.org/forum/t/change-timermillis-period-on-downlink-for-stm32l0/34897>\
**Category:** End Devices (Nodes)\
**Created:** [February 28, 2020, 1:29am UTC](https://www.thethingsnetwork.org/forum/t/change-timermillis-period-on-downlink-for-stm32l0/34897 "2020-02-28T01:29:57Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![coastalplain](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/coastalplain/32/46415_2.png) [@coastalplain](https://www.thethingsnetwork.org/forum/u/coastalplain)\
**Post date:** [February 28, 2020, 12:23pm UTC](https://www.thethingsnetwork.org/forum/t/change-timermillis-period-on-downlink-for-stm32l0/34897/5 "2020-02-28T12:23:22Z")

</div>

Great points; and thank you for the clarification on `delay` _vs_. ` period`. I will want to think through (again) the various needs and values that should be restricted or limited. Say, set a delay of 600s to let the realization sink in after sending a downlink with a 60000m (field trip) _vs._ 60000ms delay. Of course, I could predetermine the maximum value and simply validate, or simply make each port a separate configuration, and have one port where I can set the values. And to reduce downlink size, if I used the [bitmap](https://www.thethingsnetwork.org/forum/t/how-to-use-bitmap-in-lora-serialization-library/33424) or other single byte, that would also be helpful to the network. Thank you.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/change-timermillis-period-on-downlink-for-stm32l0/34897)._