Maximum value to be input to otLinkSetPollPeriod function as parameter

RE: Maximum value to be input to otLinkSetPollPeriod function as parameter

Jørgen Holmefjord — Fri, 11 Mar 2022 16:38:34 GMT

I'm pretty sure you need to set the longer Child timeout before setting the Poll period in your application to be able to set the longer poll period correctly. In your screenshot you are calling otThreadSetChildTimeout() after otLinkSetPollPeriod().

RE: Maximum value to be input to otLinkSetPollPeriod function as parameter

Abhijith.Desai — Wed, 02 Mar 2022 09:14:30 GMT

ea88129601832ebc05dc06b68fe39420 could you try with this sniffer key.

Sorry for not providing it earlier..

RE: Maximum value to be input to otLinkSetPollPeriod function as parameter

Jørgen Holmefjord — Thu, 24 Feb 2022 17:27:55 GMT

I'm not able to read the sniffer trace, as the packets are encrypted. I tried adding the masterkey from your log, but it did not seem to work. Do you have another masterkey?

RE: Maximum value to be input to otLinkSetPollPeriod function as parameter

Abhijith.Desai — Thu, 24 Feb 2022 12:57:14 GMT

Hi,

Yes i am using 300s as child timeout value. but i tried to increase and still it seems poll period is clipped to 188s..

and in all the examples with SDK is see the poll period and child timeout value is very less (1000ms or less)devzone.nordicsemi.com/.../sniff-for-188s.pcapng devzone.nordicsemi.com/.../Debug-log.txt

RE: Maximum value to be input to otLinkSetPollPeriod function as parameter

Jørgen Holmefjord — Wed, 23 Feb 2022 19:18:21 GMT

What is the value of your child timeout?

I tested the CLI example, and I'm not able to set the poll period above 236000 ms with the default child timeout (240s). If I increase the child timeout, I can set longer poll periods.

This makes sense, as the child would time out before polling the parent on every wakeup.

RE: Maximum value to be input to otLinkSetPollPeriod function as parameter

Abhijith.Desai — Mon, 21 Feb 2022 11:34:51 GMT

Hi.

Additionally, i used a get function otLinkGetPollPeriod(instance) where it returns the set opll period value.. and i just printed that value before going to sleep every time.

It seems that this return function:

During joining returns some default value 236000

Once joining is completed and poll period is executed is see it returns the value we have set(it doesnt set to 188s here).

This makes clear that OT function has nothing to do with the set poll period value it works perfectly.

Issue maybe something else i guess.. please give some clues to check further..

During joining

Once joining is completed

Best Regards

Abhijith Desai

RE: Maximum value to be input to otLinkSetPollPeriod function as parameter

Abhijith.Desai — Mon, 21 Feb 2022 10:26:45 GMT

Hi,

Thanks for your reply on this..

Even i dont see any limitations listed in the documentation related to poll value.

I tried to do the above tests with RF wakeup (printed as wakeup in eosm) and device wakeupp (Printed as wakeup in CSA) and along with that i ran sniffer where i could see that when ever i see the RF wakeup printed at the same time i see some packets getting exchanged(the one in white lines in sniffer window)

From that it is clear that, the poll period itsef is set to 188s even if it is set to 200 or any value above that.

Is there anyway we could see what is the exact poll period that is set inside the OT stack with some sort of library return function.

Best Regards

Abhijith Desai

RE: Maximum value to be input to otLinkSetPollPeriod function as parameter

Jørgen Holmefjord — Tue, 08 Feb 2022 16:30:21 GMT

Hi,

I can't see any limitations mentioned in the documentation, and I would expect longer periods to be supported (OpenThread specifically mentions longest poll period cap would be ~18.6 hours). Have you verified with a sniffer if the poll period is actually set to 188s, or if it is set to the requested value?

How do you check the poll period? Note that the chip may wakeup more frequent, without actually sending packets on the radio, for instance to handle overflow event in RTC peripheral (which handles the wakeup events).

Best regards,
Jørgen