• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 56 subscribers
  • Views 246 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

CC2340R5: The node's poll period does not match the sending time of the Data request packets.

CC2340R5: Poll period larger than 5 seconds

Tiago Lone
Prodigy 80 points

Part Number: CC2340R5
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

In a previous message it was said that Texas was aware of an issue in SimpleLink F3 SDK v9.11 that prevents the poll rate going above 5s and that it would be solved in the next release.

I am using SimpleLink F3 SDK v9.12 and would like to set a poll period larger than 5 seconds but it did not work,setting larger values in SysConfig, the maximum period that works is 5s in my case. I tried the suggested workaround calling zb_zdo_pim_set_long_poll_interval() with larger values in application but it also did not work.

Could someone confirm that this issue was corrected in SimpleLink F3 SDK v9.12, and if not, could you give me an example how to use the workaround in the onoff_switch example?

Thanks,

  • 0
    TI__Genius 14494 points

    Hello Tiago Lone,

    I found the internal ticket about the bug and it looks like there was a "fix" implemented that moved "zb_zdo_pim_set_long_poll_interval(ED_POLL_RATE);" above the "#ifdef DISABLE_TURBO_POLL"

    These fixes were only applied to the files on_off_light.c, and on_off_switch.c. 

    As for the description for the fix:
    "Move zb_zdo_pim_set_long_poll_interval above #ifdef DISABLE_TURBO_POLL or else the SysConfig poll period is not used for a default F3 SDK Zigbee project" 

    Thanks,
    Alex F

  • +1
    Prodigy 80 points

    Thank you for the answer, but this fix do not solve the problem here. I solved the problem by calling zb_zdo_pim_set_long_poll_interval(ED_POLL_RATE) after the join procedure, as stated in this function documentation.

    "  - Long Poll interval configuration should be done after the join procedure because during join the Long Poll interval will be set to the default value @ref ZB_PIM_DEFAULT_LONG_POLL_INTERVAL."