• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 55 subscribers
  • Views 350 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.

CC2652R: Delay in zed_doorlockcontroller

Alberto Alfonso
Prodigy 90 points

Part Number: CC2652R
Other Parts Discussed in Thread: Z-STACK

Hello team, I am using two examples provided by you, the first one is zed_doollockcontroller and the other one is zc_doorlock, I can connect this two examples and send lock and unlock command and it is working properly but it has a delay between 2 and 4 second, I would like to know if this is the expected behavior and if there is any way to reduce that delay. 

  • 0
    TI__Guru**** 223727 points

    Hello Alberto,

    You've described the average delay induced by the Poll period, 3000 ms, which determines how frequently the ZED asks for new data from its parent, the ZC in this instance.  You can access the Poll period inside of zed_doorlockcontroller.syscfg -> Z-Stack -> Power Management -> Poll period and reduce as necessary.  I would have expected this type of behavior more from the door lock server waiting on the door lock controller client, although perhaps you are waiting for an attribute report for confirmation of the door lock status.

    Regards,
    Ryan