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

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.

CC2530: ZCL_CMD_WRITE_UNDIVIDED command to operate ATTRID_IDENTIFY_TIME(dentify Cluster).

Alvin Chen
Expert 3925 points
Part Number: CC2530
Other Parts Discussed in Thread: Z-STACK

In Z-stack3.0.1,  When using ZCL_CMD_WRITE  command to write ATTRID_IDENTIFY_TIME(dentify Cluster). will start Identify timer. If using ZCL_CMD_WRITE_UNDIVIDED command to operate ATTRID_IDENTIFY_TIME(dentify Cluster), need to start  Identify timer?

  • 0
    TI__Guru**** 202256 points
    Alvin,

    WRITE will continue to make attribute changes even if one entered is not supported. WRITE_UNDIVIDED will not change any attribute values if one or many cannot be written, therefore you have to ensure that all the attributes are supported and writable or none will be altered. If IDENTIFY_TIME is the only attribute that you are trying to change then there are no worries as operation will be exactly the same between either command.

    Regards,
    Ryan
  • 0 in reply to Ryan Brown1
    Genius 5250 points

    When IDENTIFY_TIME is written and changed,the identify-timer should also run to count down IDENTIFY_TIME value. In z-stack 3.0.0, both WRITE CMD and WRITE_UNDIVIDED CMD will not effect  identify-timer running when write (change)  IDENTIFY_TIME. In z-stack 3.0.1,only  WRITE but not WRITE_UNDIVIDED could effect  identify-timer running.