• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 57 subscribers
  • Views 2307 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.

CC2652R: Cannot make touchlink work successfully using LAUNCHXL-CC26X2R1 running zr_light and zed_switch in SIMPLELINK-ZIGBEE-SDK-PLUGIN_2.20.00.06

YiKai Chen
Guru 735695 points

Part Number: CC2652R
Other Parts Discussed in Thread: LAUNCHXL-CC26X2R1, CC2530, , CC2538

I cannot make touchlink work successfully using LAUNCHXL-CC26X2R1 running zr_light and zed_switch in SIMPLELINK-ZIGBEE-SDK-PLUGIN_2.20.00.06.

The followings are my step

1. start zr_light and press "E" on <COMMISSION> to form ZR DIST network.

2. enable "T.L. TARGET" on zr_light and I can see the final count down

3. start zed_switch and enable "T.L. INITIATOR". Go to <COMMISSION> and press "E" to initial T.L. INITIATOR.

4. I can see zed_switch joins zr_light (I see the same PANID(0x2168) and same channel c25 on UART output of both zed_switch and zr_light). I also attach my sniffer log for your reference.

5. I try to toggle LED from zed_switch <APP SWITCH> but I don't see toggle command is sent.

There is no detail steps to show user how to use T.L. example so can TI provide exact steps or user guide to test T.L. on zed_switch and zr_light?

CC2652TL.zip

  • 0
    TI__Intellectual 2780 points

    Hey YK,

    You are not required to form a network to begin with for TouchLink, but you can if you'd like.

    Touchlink commissioning ONLY occurs on channels 11, 15, 20, and 25. Any other channel is classical commissioning, so unfortunately getting the sniffer captures is harder for Touchlink.

    The process is as the following:
    - Ensure that either your initiator OR target have NWK Formation enabled. (Optional)
    - For the initiator, enable T.L. INITIATOR in the Configure page.
    - have your Target device enable 'T.L. TARGET' and you should see the timer begin counting down. This will have the target begin searching for initiator's scan requests on the channels listed above.
    - While the Target is counting down, start commission on the initiator.
    - The target should have left any network it was joined to, and either form its own network or join the initiator's network - if the initiator is on a network. (According to the spec)

    However, we see there is an issue currently with Find&Bind when Touchlink is enabled. This is why the toggle is not working properly. We are currently looking into this issue, and performing some tests on this. I will make sure to update you as soon as we find a solution for you.

    Edit: Added detail that NWK Formation enabled is option for the TL commissioning process.

  • 0 in reply to Sean M
    Guru 735695 points

    Thank your for the detail information. So, who should be the T.L. INITIATOR using zr_light and zed_switch? zr_light or zed_switch?

  • 0 in reply to Sean M
    Guru 735695 points
    I also have another touchlink test using CC2538DK as SampleLight ZR and CC2530DK as SampleSwitch ZED and I also see touchlink commission success (the same PANID and channel on both LCD of SampleLight and SampleSwitch). However, I also cannot send toggle command from SampleSwitch to SampleLight. Is this the same issue with Find&Bind when Touchlink is enabled as I tested with CC2652?
  • 0 in reply to YiKai Chen
    TI__Intellectual 2780 points
    Thanks for the information, replicating your test with two CC2538's I can see that the same issue we saw with the CC2652R is occuring also on the CC2530/CC2538DK. We are looking into this right now and will hopefully get a fix asap.

    As for your question on who should be the Initiator versus the Target, the specification doesn't define Touchlink initiator/target to device applications, meaning the implementation of Touchlink commissioning for init/target is application dependent.

    Typically in the case for light/switch examples, the light should act as the target and switch as the initiator, simply because the switch acts as a remote controller which starts commissioning actions and the light is the device that typically is the one commissioned. However, since the specification does not have any definition on which device should be what, you can choose to have the light/switch be either.

    Hopefully that clarifies the TL role question.

    Again, I'll update you once I hear back on a Touchlink Find&Bind resolution.

    Best,
    Sean
  • 0 in reply to Sean M
    Guru 735695 points

    Thanks confirming this finding and binding issue, and explaining the touchlink initiator/target role in details. Look forward to seeing your fix.

  • 0 in reply to YiKai Chen
    Guru 735695 points
    Any update on this issue?
  • 0 in reply to YiKai Chen
    TI__Intellectual 2780 points

    Sorry for the wait YK, we have a resolution for the Find & Bind issue, however, with our resolution, it was found to cause another issue. I have been told that we are hoping to have a fix soon for this. This fix will be in the new SDK.

  • 0 in reply to Sean M
    Guru 735695 points
    Cool. Will wait your further updates.
  • 0 in reply to Sean M
    Guru 735695 points
    Since this is verified issue and will only be fixed in next SDK version, I suggest you to list it on processors.wiki.ti.com/.../Zigbee_Known_Issues_and_Proposed_Fixes