# duty cycle counter 868 Pro not working like it should?

**URL:** <https://forums.digi.com/t/duty-cycle-counter-868-pro-not-working-like-it-should/14461>\
**Category:** XBee - 802.15.4\
**Tags:** xbee-868-pro, counter, cycle, duty, xbee\
**Created:** [March 3, 2015, 1:14pm UTC](https://forums.digi.com/t/duty-cycle-counter-868-pro-not-working-like-it-should/14461 "2015-03-03T13:14:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![korstiaan](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@korstiaan](https://forums.digi.com/u/korstiaan)\
**Post date:** [March 3, 2015, 1:14pm UTC](https://forums.digi.com/t/duty-cycle-counter-868-pro-not-working-like-it-should/14461/1 "2015-03-03T13:14:22Z")

</div>

Hi,

I understand that these modules are limited by a 10% duty cycle. But I don’t understand why the duty cycle increments automatically WITHOUT sending anything? My controller (connected on the coordinator) ONLY loops the local AT command “DC” and there I see that the duty cycle counter increases. Why? My end device is only connected with a power supply and also sends nothing. Is there a kind of overhead between the 2 that causes the duty cycle counter to increment without sending anything?  
Then, if I power off the end device the increase of the DC counter also stops? BUT, also, when it stops (after the power off of the end device) the counter does NOT decrements but stays forever at the last value? This is not normal also.  
What is going on?  
How to avoid these problems (increments without sending anything and not decrementing when there are no end devices)?  
There are no IO detection changes configured.

Korstiaan

---

<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:** [March 3, 2015, 1:56pm UTC](https://forums.digi.com/t/duty-cycle-counter-868-pro-not-working-like-it-should/14461/2 "2015-03-03T13:56:22Z")

</div>

Korstiaan,

Are you receiving data from your End device?

---

<div class="post-metadata">

**Author:** ![korstiaan](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@korstiaan](https://forums.digi.com/u/korstiaan)\
**Post date:** [March 3, 2015, 4:08pm UTC](https://forums.digi.com/t/duty-cycle-counter-868-pro-not-working-like-it-should/14461/3 "2015-03-03T16:08:49Z")

</div>

Hi,

Now, that’s the point: I don’t send anything. There is even nothing connected on the end device. Also, there is nothing coming out of the coordinator. Only the answers of my DC command.

---

<div class="post-metadata">

**Author:** ![korstiaan](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@korstiaan](https://forums.digi.com/u/korstiaan)\
**Post date:** [March 4, 2015, 11:55am UTC](https://forums.digi.com/t/duty-cycle-counter-868-pro-not-working-like-it-should/14461/4 "2015-03-04T11:55:58Z")

</div>

Hi,

I found my problem: Changed from Coordinator/End device to 2x Standard Node.  
The performance (speed) is also much better now!  
10% rule stays but duty cycle is not incrementing if I don’t send anything.