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.

LAUNCHXL-CC1352P: Setting up a CC1352P as an end device

Part Number: LAUNCHXL-CC1352P
Other Parts Discussed in Thread: CC1352P, Z-STACK

Tool/software:

Hello. First timer with Zigbee and these boards.

I believe I have successfully set up one of the boards to act as a coordinator, but I am trying to get one to act as an end device, and it seems to be failing at the point of requesting a Node Descriptor from the end device.

I'm using the zigpy_znp library.

This is roughly what I'm seeing on the coordinator side of things:

INFO:sncalternativebearer.bearer_interfaces.zigbee_802154_controller:Devices: {00:12:4b:00:22:7a:b0:5b: <ZNPCoordinator model='Coordinator' manuf='Texas Instruments' nwk=0x0000 ieee=00:12:4b:00:22:7a:b0:5b is_initialized=True>}
INFO:zigpy_znp.zigbee.application:on zdo message: ZDO.MsgCbIncoming.Callback(Src=0x0000, IsBroadcast=<Bool.false: 0>, ClusterId=32822, SecurityUse=0, TSN=0, MacDst=0x0000, Data=b'\x00')
INFO:zigpy_znp.zigbee.application:Trust center device join: ZDO.TCDevInd.Callback(SrcNwk=0x5D1A, SrcIEEE=00:12:4b:00:22:7a:d8:6f, ParentNwk=0x0000)
INFO:zigpy.application:New device 0x5d1a (00:12:4b:00:22:7a:d8:6f) joined the network
INFO:zigpy.device:[0x5d1a] Scheduling initialization
INFO:zigpy.device:[0x5d1a] Requesting 'Node Descriptor'
INFO:zigpy.device:[0x5d1a] Requesting 'Node Descriptor'
INFO:zigpy.device:[0x5d1a] Requesting 'Node Descriptor'
INFO:zigpy.device:[0x5d1a] Requesting 'Node Descriptor'
INFO:zigpy.device:[0x5d1a] Requesting 'Node Descriptor'
INFO:sncalternativebearer.bearer_interfaces.zigbee_802154_controller:Devices: {00:12:4b:00:22:7a:b0:5b: <ZNPCoordinator model='Coordinator' manuf='Texas Instruments' nwk=0x0000 ieee=00:12:4b:00:22:7a:b0:5b is_initialized=True>, 00:12:4b:00:22:7a:d8:6f: <Device model=None manuf=None nwk=0x5D1A ieee=00:12:4b:00:22:7a:d8:6f is_initialized=False>}

And on my end device:

INFO:sncalternativebearer.bearer_interfaces.zigbee_802154_end_device:Found network beacon: Beacon(Src=0x0000, PanId=0xB11F, Channel=15, PermitJoining=1, RouterCapacity=1, DeviceCapacity=1, ProtocolVersion=2, StackProfile=2, LQI=189, Depth=0, UpdateId=0, ExtendedPanId=12:5d:a6:ef:a0:c0:dc:8e)
INFO:sncalternativebearer.bearer_interfaces.zigbee_802154_end_device:Waiting for network beacon(s) to be found...
INFO:sncalternativebearer.bearer_interfaces.zigbee_802154_end_device:Network discovery complete: <Status.SUCCESS: 0>
INFO:sncalternativebearer.bearer_interfaces.zigbee_802154_end_device:End device has sent network join request
INFO:sncalternativebearer.bearer_interfaces.zigbee_802154_end_device:Received join confirmation: ZDO.JoinCnf.Callback(Status=<Status.SUCCESS: 0>, Nwk=0x5D1A, ParentNwk=0x0000)
INFO:sncalternativebearer.bearer_interfaces.zigbee_802154_end_device:Device announcement sent ZDO.EndDeviceAnnce.Rsp(Status=<Status.SUCCESS: 0>)

So the coordinator is recognizing the device's network join request, and scheduling the device for initialization, but that never resolves.

Is there something obvious I'm missing that I need to do to get my CC1352P to join my other CC1352P as an end device?

Thanks

  • Hi Ben,

    Are you able to set up a sniffer device to receive and parse the over-the-air packets?  Would you also be able to debug your ZNP ZED inside the CCS IDE to determine whether it is correctly running the application or receives the Node_Desc_rsp case in zsProcessZDOMsgs.  Do you observe similar behavior with a ZR device attempting to join the ZC, and have you tried using a non-sleepy ZED configuration?  Is the ZED capable of sending or receiving any other commands, and is it sending Data Requests at regular intervals?  Are you using a LAUNCHXL-CC1352P hardware version "1" or "-2", and what is the TX power initialized for either ZC or ZED? 

    Please keep in mind that zigpy-znp is a third-party solution which is not maintained by TI, so although E2E experts can advise towards the CC1352P MCU and SimpleLink F2 SDK they will not be as experienced with the zigpy-znp interface.

    Regards,
    Ryan

  • Hi Ryan, sorry for not getting back to you. I ended up figuring it out. Separate problem now, does Z-Stack not offer Sub GHz capabilities? I did some googling, I could only find answers from 6 years ago that it does not support Sub GHz capabilities. The entire reason I bought this CC1352 board was the dual band capability..

  • Hi Ben,

    Z-Stack does not offer Sub-GHz operation.  You could look at ZBOSS offered by DSR as this software stack does offer Sub-GHz Zigbee solutions with the CC1352.

    Regards,
    Ryan