• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 426 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.

LPSTK-CC1352R: Zigbee Commissioning with CC1352R1 Launchpad and LPSTK-CC1352R SensorTag Kit

coder11
Prodigy 80 points
Part Number: LPSTK-CC1352R
Other Parts Discussed in Thread: CC1352R

I'm currently trying to use the two kits mentioned in the title to create a Zigbee network with the coordinator (CC1352R1 Launchpad) acting as a thermostat, and the end device (LPSTK SensorTag) acting as a temperature sensor.  I bought these two kits to experiment with different features of Zigbee.  As I understand it, for these two projects, they require use of the Application UI to commission the two nodes into the same network.  In the application notes for the LPSTK it mentions that the CC1352R1 Launchpad acts as the XDS110 for the LPSTK module.  When I do this, I am not able to see the consoles for both of the applications.  I don't even think the Launchpad is running while it is used as the debugger for the LPSTK.  So my question is, how do I successfully commission a Zigbee network using the zc_thermostat and zed_temperaturesensor projects with these two boards/kits?

  • 0
    TI__Mastermind 28450 points

    Hi,

    coder11 said:
    As I understand it, for these two projects, they require use of the Application UI to commission the two nodes into the same network. 

    You don't necessarily need to use the UI for commissioning. On the examples, pressing BTN-1 (DIO15) should begin the commissioning process.

    coder11 said:
    When I do this, I am not able to see the consoles for both of the applications.

    I believe the XDS110 on the launchpad may be used for one device at a time (e.g. either the CC1352R on the launchpad itself, or the CC1352R on the connected LPSTK).

    Hope this helps.

    Regards,
    Toby

  • 0 in reply to Toby Pan
    Prodigy 80 points

    I saw that in the notes too, but when I press BTN-1 on both devices, all I see for the Coordinator (Launchpad) is the following line, with the number counting down from 180 to 0.

       BDB Info: -- JOIN Open051 Id051 Srch051/00

    Pressing BTN-1 on the LPSTK board doesn't seem to do anything.  Does it sound like the temperature sensor program running on the LPSTK is not working correctly?

    In terms of viewing the UART consoles of both boards, that is not possible with just those two boards, correct?

    Thanks,
    Anthony

  • 0 in reply to coder11
    TI__Mastermind 28450 points

    coder11 said:
    In terms of viewing the UART consoles of both boards, that is not possible with just those two boards, correct?

    Correct.

    coder11 said:
    I saw that in the notes too, but when I press BTN-1 on both devices, all I see for the Coordinator (Launchpad) is the following line, with the number counting down from 180 to 0.

    Yes, this is the expected behavior for the ZC (Zigbee coordinator). It's an indication that the network has been opened for other devices to join.

    coder11 said:
    Pressing BTN-1 on the LPSTK board doesn't seem to do anything.  Does it sound like the temperature sensor program running on the LPSTK is not working correctly?

    If this is the out-of-box example, then the two devices should be commissioned shortly after both sides have started the commissioning process. Afterwards, the temperature sensor should report at least every 10 seconds. For the thermostat example, what do you see in the "APP Info" section on the UI?

  • 0 in reply to Toby Pan
    Prodigy 80 points

    This isn't the out-of-the-box example.  I flashed these using debug in CCS.  Here is what I see for App Info on the Thermostat device:

       APP Info: [Remote Temperature] Invalid [System Mode] OFF
       APP Info: [Cooling Set Temp] 24C [Heating Set Temp] 19C

  • 0 in reply to coder11
    TI__Mastermind 28450 points

    Thanks for confirming.

    Flashing through CCS should be ok.

    I tried this and was able to receive temperature reports on the the thermostat. What is displayed on the thermostat's APP Info lines:

    APP Info: [Remote Temperature] 17C [System Mode] HEAT
    APP Info: [Cooling Set Temp] 24C [Heating Set Temp] 20C

    This happens about 10-12 seconds after performing the commissioning process.

    Do you see a green LED light up on the LPSTK (after pressing btn-1 on the thermostat, then pressing btn-1 on the LPSTK)?

  • 0 in reply to Toby Pan
    Prodigy 80 points

    I tried this again after some time away and I now see the Green LED light up on the LPSTK after pressing BTN-1.  I wonder if I wasn't waiting long enough to press the LPSTK's BTN-1 after pressing the Launchpad's BTN-1.  Anyhow, I'm now seeing a valid Remote Temperature Value on the thermostat side.

       APP Info: [Remote Temperature] 17C [System Mode] HEAT
       APP Info: [Cooling Set Temp] 24C [Heating Set Temp] 20C

    Is the Commissioning menu in the Sample App UI there for individually controlling the steps rather than it being done by a single button press on each board?

  • 0 in reply to coder11
    TI__Mastermind 28450 points

    Glad to hear it's working now!

    coder11 said:
    Is the Commissioning menu in the Sample App UI there for individually controlling the steps rather than it being done by a single button press on each board?

    Commissioning is started essentially the same way, whether it is initiated from the UI or for pressing the button (compare zclSampleThermostat_processKey and uiActionStartComissioning).

    With the UI, there is more flexibility on configuring which commissioning modes are enabled, while the button press triggers the default commissioning mode (should generally be applicable for typical applications).

  • 0 in reply to Toby Pan
    Prodigy 80 points

    Awesome, thank you for your help!