• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 55 subscribers
  • Views 687 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.

LP-CC1352P7: Commercial PIR sensor not binding to ZC Zone Example application.

vincent hartman
Intellectual 750 points
Part Number: LP-CC1352P7


Good day, 

Commercial motion sensor not successfully binding to Coordinator.  I am using a Sonoff SNZB-03 sensor as ED and LP-CC1352P7-4 as Coordinator. I am running the stock-standard "zc_zone" software example from the TI resource Explorer package (listed under the CC1352P7-4 Launchpad device.  Which is listed under the SimpleLink CC13xx CC26xx SDK 7.10.01.24)  on the Launchpad.  Both devices are running Zigbee 3.

It appears that the Coordinator starts and creates a network.  I then do Trip-To-Pair by manual button-press on ZC and ZED side.

The Motion sensor announces itself (Device Announcement) but then an END Device Timeout Request is sent by the ED.

The ED then sends a Zone Enroll Request, followed by a Zone Status Change Notification.

The coordinator then sends an End Device Timeout Response, Success

Then finally the coordinator sends a Default Response  (0x0b) command with status = "Unsupported Cluster Command"

I am attaching a wireshark trace. I would appreciate some input on this.

Best regardsPIR1.zip

  • +1
    Guru 735695 points

    I suppose you should run zc CIE instead of zone to test IAS zone device.

  • +1
    TI__Guru**** 219737 points

    Hi Vincent,

    I agree with YK, please see the zc_cie README to further understand the roles of each IAS application.

    CIE sample application is meant to interact with other Intruder Alarm System (IAS) devices, for which it uses the following IAS clusters:

    Cluster as client Purpose of the cluster
    IAS Warning device Works as an interface to a Warning device to issue warning indications that trigger sirens, strobes, lights, etc. at the warning device.
    IAS Zone Performs enrollment of devices from which the CIE will receive notifications. Those notifications depend on the Zone device type; this sample app processes fire detector alarms only (see zclSampleCIE_ChangeNotificationCB).

    CIE sample application illustrates the usage of these two clusters when interacting with either Zone Device or Warning Device.

    Cluster as server Purpose of the cluster
    IAS ACE Interface to manipulate the IAS System. Eg. Trigger an alarm, bypass an alarm, retrieve status, etc.

    If you have a second LaunchPad, you could also test the expected operation of these examples by commissioning a ZR/ZED zone/warningdevice project to the ZC CIE.

    Regards,
    Ryan

  • 0 in reply to YiKai Chen
    Intellectual 750 points

    Thanks, I had success with the ZC CIE and the ED Zone. The enrolment, descriptor matching and IEEE address writing worked. Must say, I would have been completely lost without the Wireshark + sniffer combo and of course this forum's help. 

    Best regards  

  • 0 in reply to Ryan Brown1
    Intellectual 750 points

    Thanks for the great and detail help Ryan, I was actually looking for explicit bind requests, but the enrolment appears to be sufficient.

    Best regards