Unable to update parent polling period of Sleepy End Device above 1000 ms

[nikhilkomalan]

Hello Developers,

Currently i have a product developed using Nordic nRF5 SDK for Thread v4.2. My project is developed on mqttsn sleepy publisher example. I am looking to change the parent polling period above 5 seconds, but the parent polling period is not getting updated above 1 sec (1000 ms) which leads to high power consumption.

I have enabled CLI too and tried to change the polling period using poll period command still i am unable to update its value above 1000 ms. I have attached logs from terminal setting parent poll period for your reference.

Can you please tell what could be the issue here, what could be the reason why my parent poll period is not updating.

CuteCom Logs:

[16:21:23:685] > pollperiod 100

[16:21:26:495] Done

[16:21:26:495] > pollperiod

[16:21:28:517] 100

[16:21:28:517] Done

[16:21:28:517] > pollperiod 500

[16:21:38:972] Done

[16:21:38:972] > pollperiod

[16:21:41:557] 500

[16:21:41:557] Done

[16:21:41:557] > pollperiod 800

[16:21:48:436] Done

[16:21:48:436] > pollperiod

[16:21:50:863] 800

[16:21:50:863] Done

[16:21:50:863] > pollperiod 900

[16:21:57:060] Done

[16:21:57:060] > pollperiod

[16:21:59:023] 900

[16:21:59:023] Done

[16:21:59:023] > pollperiod 950

[16:22:04:764] Done

[16:22:04:764] > pollperiod

[16:22:06:485] 1000

[16:22:06:485] Done

[16:22:06:485] > pollperiod 1500

[16:22:14:552] Done

[16:22:14:552] > pollperiod

[16:22:18:224] 1000

[16:22:18:224] Done

[16:22:18:224] > 

As you can see when i set pollperiod to 1500 ms it still gives me 1000 ms poll period.

[jwhui]

I believe the poll period is bounded by the Child Timeout. You can check the Child Timeout value using the childtimeout CLI.

[nikhilkomalan]

Okay thanks for info.
Child timeout was set to 5. After updating it to 30 i was able to set desired polling period.