Configuration of Xbee S2C Coordinator’s ZCL data to be sent to sensor

XBee & XBee Gateway XBee Programamble (S2C & 900 HP)
, , , ,
1

The Xbee s2c module that connected with uart serial port of my mcu and set Coordinator mode received the data from open/closed smartsesnse through ZDO command.

the next step of simple description response is ZCL request to read a cluster attributes (app. version, manufacturer, model request etc.), following as below references, so coordinator sent End-point ZCL data.
But I could not receive ZCL attributes data because of ‘not found network’ error.

How do I configure ZCL packets using the endpoints and cluster values obtained in the process below?

Let me know if there is a process that needs to be added to form a network between Coordinator and End-device before using ZCL data.

(data logs from coordinator)

Rx << 7E | 001E | 91 00 0D 6F 00 04 05 5D 07 F8 38 00 00 00 13 00 00 02 D9 38 F8 07 5D 05 04 00 6F 0D 00 80 | CE
Explicit Rx Indicator
DestAddr64 : 000D6F0004055D07
DestAddr16 : F838
Src.EP : 00
Dst.EP : 00
ClusterId :0013
ProfileId :0000
RxOption : 02
Payload : D938F8075D0504006F0D0080
DEVICE ANNOUNCE FROM ENDDEVICE
FrameId : D9
NWKAddr : F838
IEEEAddr : 000D6F0004055D07
Capability : 80

Tx > 7E | 0017 | 11 DA 00 0D 6F 00 04 05 5D 07 F8 38 00 00 00 05 00 00 00 00 DA 38 F8 | EC
Explicit Addressing Command Frame
FrameId : DA
DestAddr64 : 000D6F0004055D07
DestAddr16 : F838
Src.EP : 00
Dst.EP : 00
ClusterId :0005
ProfileId :0000
Broadcast Radius : 00
Option : 00
Payload : DA38F8

Rx << 7E | 0019 | 91 00 0D 6F 00 04 05 5D 07 F8 38 00 00 80 05 00 00 01 DA 00 38 F8 02 01 02 | C0
Explicit Rx Indicator
DestAddr64 : 000D6F0004055D07
DestAddr16 : F838
Src.EP : 00
Dst.EP : 00
ClusterId :8005
ProfileId :0000
RxOption : 01
Payload : DA0038F8020102
ACTIVE ENDPOINT RESPONSE
FrameId : DA
Status : 00
NWKAddressOfInterest : F838
ActiveEPCount : 02
ActiveEPList : 0102

Tx > 7E | 0018 | 11 DA 00 0D 6F 00 04 05 5D 07 F8 38 00 00 00 04 00 00 00 00 DA 38 F8 01 | EC
Explicit Addressing Command Frame
FrameId : DA
DestAddr64 : 000D6F0004055D07
DestAddr16 : F838
Src.EP : 00
Dst.EP : 00
ClusterId :0004
ProfileId :0000
Broadcast Radius : 00
Option : 00
Payload : DA38F801

Rx << 7E | 002F | 91 00 0D 6F 00 04 05 5D 07 F8 38 00 00 80 04 00 00 01 DA 00 38 F8 18 01 04 01 02 04 00 07 00 00 01 00 03 00 02 04 00 05 20 00 05 0B 01 19 00 | 42
Explicit Rx Indicator
DestAddr64 : 000D6F0004055D07
DestAddr16 : F838
Src.EP : 00
Dst.EP : 00
ClusterId :8004
ProfileId :0000
RxOption : 01
Payload : DA0038F81801040102040007000001000300020400052000050B011900
SIMPLE DESCRIPTOR RESPONSE
FrameId : DA
Status : SUCCESS
NWKAddrOfInterest : F838
Length : 18
SimpleDescriptor

  • Endpoint : 01
  • Application profile identifier : 0104 - ZIGBEE HOME AUTOMATION
  • Application device identifier : 0402 - IAS Zone
  • Application device version : 00
  • Application input cluster count : 07
  • Application input cluster list : 0B05 0020 0500 0402 0003 0001 0000
  • Application output cluster count : 01
  • Application output cluster list : 0019

Tx > 7E | 0018 | 11 DA 00 0D 6F 00 04 05 5D 07 F8 38 00 00 00 04 00 00 00 00 DA 38 F8 02 | EB
Explicit Addressing Command Frame
FrameId : DA
DestAddr64 : 000D6F0004055D07
DestAddr16 : F838
Src.EP : 00
Dst.EP : 00
ClusterId :0004
ProfileId :0000
Broadcast Radius : 00
Option : 00
Payload : DA38F802

Rx << 7E | 002B | 91 00 0D 6F 00 04 05 5D 07 F8 38 00 00 80 04 00 00 01 DA 00 38 F8 14 02 DF C2 0C 00 00 05 00 00 01 00 03 00 05 0B 0F FC 01 03 00 | DB
Explicit Rx Indicator
DestAddr64 : 000D6F0004055D07
DestAddr16 : F838
Src.EP : 00
Dst.EP : 00
ClusterId :8004
ProfileId :0000
RxOption : 01
Payload : DA0038F81402DFC20C000005000001000300050B0FFC010300
SIMPLE DESCRIPTOR RESPONSE
FrameId : DA
Status : SUCCESS
NWKAddrOfInterest : F838
Length : 14
SimpleDescriptor

  • Endpoint : 02
  • Application profile identifier : C2DF - Unknown device or Add Profile ID Info.
  • Application device identifier : 000C - Simple Sensor
  • Application device version : 00
  • Application input cluster count : 05
  • Application input cluster list : FC0F 0B05 0003 0001 0000
  • Application output cluster count : 01
  • Application output cluster list : 0003

Tx > (zcl) 7E | 001B | 11 5D 00 0D 6F 00 04 05 5D 07 E0 3C 01 01 00 00 01 04 00 00 00 00 00 00 00 01 00 | 84
Explicit Addressing Command Frame
FrameId : 5D
DestAddr64 : 000D6F0004055D07
DestAddr16 : E03C
Src.EP : 01
Dst.EP : 01
ClusterId :0000
ProfileId :0104
Broadcast Radius : 00
Option : 00
Payload : 00000000000100

Rx << 7E | 0007 | 8B E1 FF FD 00 24 02 | 71
Transmit Status : Access Not found / Route Discovery

(references)

2

Try looking over https://www.digi.com/resources/documentation/DigiDocs/90002002/default.htm#reference/r_zb_send_zcl_commands_with_api.htm?Highlight=13

Take a closer look at the destination and source end points.

3

Your article helps me to understand the payload structure of the HA profile cluster.

Thank you!