• State TI Thinks Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 3 answers
  • Subscribers 58 subscribers
  • Views 1334 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: Zigbee with Digi-XBee and CC1352P

SmartEnrg
Expert 1165 points
Part Number: LAUNCHXL-CC1352P
Other Parts Discussed in Thread: CC1352P, Z-STACK,

Hi,

We’ve a Zigbee-Pro 2007 based Digi-XBee Zigbee coordinator and we’re trying to get them to work with CC1350P launchpad.

Is there any app note or demo code that could get us started with this? From what I understand – the Digi-XBee modules are

Zigbee compatible, though there’s something peculiar about their packets; so trying to ensure they will interoperate with 1352

TI-Zigbee stack. Please advise.

Thanks.

  • 0
    Guru 735625 points
    Basically, CC1352P runs Z-Stack 3.10 which is based on Zigbee 3.0 and it should be backward compatible to XBee module running Zigbee HA profile.
  • 0
    TI__Mastermind 33640 points
    Hi,

    In general, they should be interoperable, given the correct configurations.

    Does the CC1352P join the network successfully? What about the packets seems peculiar?

    If possible, please provide sniffer logs for further analysis.


    Regards,
    Toby
  • 0 in reply to Toby
    Prodigy 130 points

    It does not join the network. Do you know out of the box what the Xbee module uses for a profile? I think it has custom endpoints, which also shouldn't be an issue to connect to.

    I started out with zr_genericapp in CCS. Is this the correct example to start with? Also, the example and Xbee coordinator does not have security/encryption enabled to make it a little easier to start off.

    Is there any other customers or documentation that you can provide to help out connecting to an off the shelf Digi XBee coordinator running default firmware?

    I will work on getting you some sniffer logs, but they really didn't have anything in them when the cc device tried to associate.

    Thank you

  • 0 in reply to eb1
    TI__Mastermind 33640 points

    Sniffer logs are useful when developing with wireless protocols such as Zigbee.
    As far as I know, we don't have any documentation regarding use with XBee devices.

    Note that the genericapp does not have any endpoints.


    Please make sure that the sniffer device and the Zigbee devices are all operating on the same channel. Then you can see traffic from both the XBee device and the CC1352P.

  • 0 in reply to Toby
    Prodigy 130 points

    Toby,

    Attatched is the Sniffer file (Wireshark) from the unsuccessful attempt to join the network. It does the Beacon Request and gets a reply,  but then it does not continue on to what I assume should be the association request.

    Thank you.CC1352AssociationToCoordinator.zip

  • 0 in reply to eb1
    Guru 735625 points
    There is only one beacon request and one beacon frame then everything stops. The permit join is on and end device capacity of coordniator is fine so everything looks good but don't know why device doesn't do association. Do you have two LAUNCHXL-CC1352P to use one as coordinator and another as end device to make sure it works first.
  • 0 in reply to eb1
    TI__Mastermind 33640 points
    The XBee coordinator's beacon indicates that its stack profile is "Network Specific", which is a likely cause of the issue.
    There's no guarantee that Network Specific stack profiles will interoperate with devices using the Zigbee specified stack profile.

    By default the CC1352P examples use the Zigbee PRO stack profile. Please search for the macro "STACK_PROFILE_ID" to verify this.
  • 0 in reply to Toby
    Prodigy 130 points

    Thanks for the info. I changed the Profile on the coordinator to ZigBee Pro and now the cc1352 device does the Association Request. It receives an Association State = Success from the coordinator, but then does a whole bunch of Data Requests and tries to re-associate. What are the Data Request packets it's trying to do and why is it re-associating ? Does this have to do with the security settings? I have the coordinator set to disable security but the cc1352 has a define to enable security. I can't set SECURE=0 and not sure where else to set to disable security.

    CC1352AssociationToCoord-ZigbeeProProfileOnCoord.zip

  • 0 in reply to eb1
    TI__Mastermind 33640 points
    The data requests are normal. The examples are configured to poll every second (see POLL_RATE in Stack/Config/f8wconfig.h).

    Please read the security section (Section 10) in the Z-Stack overview (found in C:\ti\simplelink_zigbee_sdk_plugin_2_20_00_06\docs\zigbee_user_guide\html\zigbee\developing_zigbee_applications\z_stack_developers_guide). There is also other content contained within that document regarding interoperability between Zigbee 3.0 and Zigbee PRO.
  • 0 in reply to eb1
    Guru 735625 points
    I suppose you should use Zigbee HA profile on your XBee Coordinator so CC1352P Running Z-Stack 3.10 example can join.