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.

LP-CC1352P7: Slight Alteration to "Zigbee Fundamental Project Development"

Part Number: LP-CC1352P7

Hello, 

    I have just finished following the guide: https://dev.ti.com/tirex/explore/content/simplelink_academy_cc13xx_cc26xxsdk_6_10_01_00/modules/zigbee/zigbee_03_fundamentals/zigbee_03_fundamentals.html 

I want to make a slight alteration to it where instead of sending one signal when BTN-2  of the "coordinator" is pressed, it sends a signal that doesn't end. To do this, I just put the action in a forever loop (shown).

   

However, after uploading the code to the boards, and pressing the button, I noticed that it only send about 20 signals before crashing and interrupting the connection between the coordinator and the switch. This interruption did not clear after doing a regular reset so I need to do a factory reset every time. What can I change to make sure that the signal is continuously sent and the connection is maintained? Thank you

  • Hi,

    zclSampleLight_processKey is called as part of the main application process loop (see zclSampleLight_process_loop and zclsampleApp_ui_event_loop), and it is not a good idea for zclSampleLight_processKey not to return (because it will prevent the process loop from executing).

    You might be able to set an event or a flag or something in zclSampleLight_processKey that can be read in the process loop, and send the signal if the flag is set.

    Regards,
    Nikolaj  

  • Adding on to what Nikolaj has said, zstackmsg_CmdIDs_AF_DATA_CONFIRM_IND should return successfully for the previous message before another Zstackapi_AfDataReq is used, and thus avoid overflowing the buffers.  Please see the Z-Stack API Guide.  Sending a signal continuously does not appear to achieve any function other than determine the maximum rate at which you can send data packets on the network.  In this case the channel traffic, CSMA control, packet sizes, and retry settings are also important.

    Regards,
    Ryan