# Packet Forwarder: Who sets "powe" in JSON downstream txpk packet?

**URL:** <https://www.thethingsnetwork.org/forum/t/packet-forwarder-who-sets-powe-in-json-downstream-txpk-packet/34481>\
**Category:** Gateways\
**Created:** [February 17, 2020, 2:06pm UTC](https://www.thethingsnetwork.org/forum/t/packet-forwarder-who-sets-powe-in-json-downstream-txpk-packet/34481 "2020-02-17T14:06:10Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![TonySmith](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/tonysmith/32/46334_2.png) [@TonySmith](https://www.thethingsnetwork.org/forum/u/TonySmith)\
**Post date:** [March 5, 2020, 8:36am UTC](https://www.thethingsnetwork.org/forum/t/packet-forwarder-who-sets-powe-in-json-downstream-txpk-packet/34481/27 "2020-03-05T08:36:23Z")

</div>

Came across a relevant quote in another post by @htdvisser

> _Every device has the same transmit duty cycle, gateways are no exception. The TTN backend is compliant with these regulations, so in Europe we stay under the 1% duty cycle for g and g1 and under 10% for g3 . By default, **gateways transmit with maximum allowed TX power (14 for EU-868)**._

See original at [Fair Use Policy explained - #7 by jakl5749](https://www.thethingsnetwork.org/forum/t/limitations-data-rate-packet-size-30-seconds-uplink-and-10-messages-downlink-per-day-fair-access-policy-guidelines/1300/7)

So wonder if this approach has changed or something has slipped through in the updates to the TTN server.

@kersing, I also went back and reread the LoraWan Regional parameters and agree, they seem to be written from a Node’s perspective.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/packet-forwarder-who-sets-powe-in-json-downstream-txpk-packet/34481)._