• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 55 subscribers
  • Views 430 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.

CC1352P: Some issue on BDB-Reporting

Aries Lord
Genius 5390 points
Part Number: CC1352P
Other Parts Discussed in Thread: Z-STACK

In ZCL Specification, every attribute under same cluster in same end-point is independent. The report-enabled attribute is allowed to have own reporting-period. Differend attributes under same cluster are allowed to have differend MAX-Reporting-Time, so they can be reported in differend time. 

Only if many attributes under same cluster in same end-point are triggering reporting in same time, they can be load into a same ZCL-Reporting-Command. The Reported attributes should be in same manufacture code and same direction.

Now I'm trying to fix DBD-Reporting.

  • 0
    TI__Guru**** 220187 points

    Hi Aries,

    Can you please provide your SDK version and give more details about the parameters required to recreate the behavior (i.e. the attributes and clusters involved)?  Can you provide steps to recreate the issue in code and a sniffer log to review the problem you are experiencing?  What is the output versus your expectation, where in the ZCL 7 Spec is this behavior defined, and what function from the Z-Stack ZCL solution needs to be modified?

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Genius 5390 points

    I can't prove ZCL 8 Spec to force every attributes must be reporting in own frame when they are reporting in differend time. But in others Chip-factory(Silabs, Telink, NXP) 's production, every attributes can report in its own frame.

    My idea is that every attributes can report when it trigger reporting, but it is not really sent by ZCL-Report-Command. When an attribute triggers reporting, it is push into a queue-cache. A function will pop the reporting attributes from this queue-cache and fill them into ZCL-Report-Command. If many attributes are under same cluster and same end-point and same manufacture-code and same direction, they can be filled into same ZCL-Report-Command

  • 0 in reply to Aries Lord
    TI__Guru**** 220187 points

    Developers are given complete access to the zcl_*.c/h and bdb_reporting.c/h files for further modification of the ZCL/BDB layers which would meet their application's reporting requirements.  Please note that Z-Stack provided with SDK v7.10 still integrates ZCL Spec v7 and that Zigbee R23 support is planned for SDK v7.40 which is set to release at the beginning of 2024.

    Regards,
    Ryan