Part Number:LAUNCHXL-CC1352R1
Hello,
I am using CC1352R REV E boards with SDK 3.10.00.11.
1) I started with the basic examples of ZigBee. I uploaded one board with Zc_doorlock_Controller and another with Zc_doorlock. But I noticed a difference in the way they used to interact in SDK 2.3 and in SDK 3.10.
In the newer version, the doorlock controller is not able to control the doorlock from its terminal. Pressing ‘W’ and ‘S’ won’t show unlock or lock the doorlock terminal and neither on its terminal. It reflects a state on its own terminal but it is always the locked state.
May I know the reason why it is behaving in such a way?
2) I have a doubt regarding the 2nd DMM example provided in ZigBee (dmm_zr_light_remote_display_app). I went through the Readme file of that particular example but I couldn’t understand the Projects used. It has asked to use a ZigBee Light Coordinator (which, if I am not wrong is Zc_Light) in conjunction with dmm_zr_light_remote_display_app. And it has no mention of any other example to be used. So how are 2 Light examples supposed to communicate with each other?
Is it that, this example is an extension/continuation of the previous example (dmm_zed_switch_remote_display_app) or is it a standalone example?
If it is the later can you please suggest me where I am going wrong with the setup?
Also, found this line (in the screenshot below) which confused me even more, Do end devices have routing capabilities?
![]()
Can anyone help me in knowing where I am going wrong with this?
Thanks and Regards,
Yash.