CC2652P: How to use API to customize pollrate for ZED devices

mingwei yang

Part Number: CC2652P
Other Parts Discussed in Thread: SYSCONFIG, Z-STACK

I use SDK to develop cc2652p zed device.

I find that it is effective to change pollrate using API in this way. However, after running for a period of time (when the device sends dataRequest at a long interval), the power consumption of the device has not been reduced. Under normal conditions, the power consumption of the device is about 5ua. It is observed that after the device sends dataRequest based on long interval, the power consumption cannot return to the normal level, which is about 3 ~ 4mA.

I use the API to customize pollrate. The source code is as follows:

zstack_sysConfigWriteReq_t req;

memset(&req, 0, sizeof(zstack_sysConfigWriteReq_t));

req.has_disablePollRate = TRUE;
Zstackapi_sysConfigWriteReq(appServiceTaskId, &req);

req.has_disablePollRate = FALSE;
req.has_pollRate = TRUE;
req.pollRateType = POLL_RATE_TYPE_DEFAULT;
req.pollRate = 500; //pollCtrl->shortInterval:0.5s,longInterval:1620s
Zstackapi_sysConfigWriteReq(appServiceTaskId, &req);

Due to product requirements, the pollrate needs to be changed during the operation of the equipment (the short interval of datarequest is 0.5 seconds and the long interval is 27 minutes).

I think the power consumption of the device may be related to calling API to set pollrate. I want to know the correct method of using API to customize pollrate. Is there any sample code?

Thank you~

over 3 years ago

0 YiKai Chen over 3 years ago

Guru 735695 points

If you suspect changing polling rate causes this issue, you can use sniffer to check real polling rate when you see current consumption about 3 ~ 4mA.

0 mingwei yang over 3 years ago in reply to YiKai Chen

Prodigy 110 points

Yes, when the power consumption is always 3~4mA, I can see from the sniffer packet capture that the device sent a dataRequest at that time.

The long interval is 27 minutes. Every time I reach 27 minutes, I observe the power consumption of the device. There is a 50% chance that this problem will occur.

0 YiKai Chen over 3 years ago in reply to mingwei yang

Guru 735695 points

How long will your device consumes 3~4mA every 27 minutes?

0 mingwei yang over 3 years ago in reply to YiKai Chen

Prodigy 110 points

When this happens, it is always kept at 3 ~ 4mA.

It is possible that the next datarequest after 27 minutes will return to normal, or it may return to normal when powerconfig or other cluster attribute are reported during this period.

0 Ryan Brown1 over 3 years ago in reply to mingwei yang

TI__Guru**** 220737 points

Hi mingwei,

This issuehas been observed before. Please review this relevant E2E thread and the Z-Stack Release Notes Known Issues. Poll periods equal to or greater than 540000 ms will cause the device to toggle between sleepy and active modes with each Data Request (i.e. 50% expected operation). This is continuing to be investigated as it concerns behavior of the lower 802.15.4 MAC layers.

Regards,
Ryan

0 Aries Lord over 3 years ago

Genius 5390 points

Pollrate more than 7-second is not effective in whole network, parent-node can keep messages for end-device only 7-second.

If you want End-device sleep for long time, you can set Pollrate to "0", and call "NwkPollReq" when you want end-device wakeup

0 Ryan Brown1 over 3 years ago in reply to Aries Lord

TI__Guru**** 220737 points

Aries is referring to the default NWK_INDIRECT_MSG_TIMEOUT from the SysConfig Z-Stack -> Advanced -> Routing settings.

Regards,
Ryan

0 Aries Lord over 3 years ago in reply to Ryan Brown1

Genius 5390 points

NWK_INDIRECT_MSG_TIMEOUT can be set only on Coordinate and router. If one of coordinate or routers is not designed by yourself, there will be a large trouble.

Zigbee & Thread

Zigbee & Thread forum

CC2652P: How to use API to customize pollrate for ZED devices