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-CC1350: Coordinator stops sending beacons after awhile

Part Number: LAUNCHXL-CC1350
Other Parts Discussed in Thread: CC1310, CC1350

Hello, 

I am implementing a star based beacon enabled network using four cc1350 launchpads ( I am using a CC1310 as a collector. But i think its not an issue. I have only changed the beacon order and super frame order). I expect to increase the number of sensors to more than 100 in near future. Currently I am using collector and sensor examples to test the network where beacon order is 6 and supper-frame order is 2. Sensors are configured to send data using their extended address. This is what i got on console for three sensors and the coordinator. 

Here is the data I tracked using wireshark.

This is the sensor and collector source-code i m using.

sensor_cc1350lp.zip

collector_cc1310lp.zip

Please help me to solve this issue. It takes some time to generate the issue.

Thanks and best regards, 

Kasun

  • What version of the CC13x0 SDK are you using?
  • Kasun,

    It looks like tx operations are being aborted on your sensor devices (error code 0x1D). Does the collector stop sending beacons when no devices join the network?
  • Hi Suyash Jain,

    Thanks for your attention. I am using CCS v7.1 with SDK 1.4.0.

  • Hi Brocklobsta,
    First of all, thanks for your reply. All three sensors are connected to the collector. These sensors send data on every second. Yes as you said, some of the tx operations are aborted but most of them are transmitted. Even the sensor data doesn't transmit, there is no reasons to stop beacons. As you can see in the wireshark log, sensors are connected and transmit data. But suddenly beacons get stopped. I have uploaded my source code and projects. If you have a time to look at it, it will be much appreciated. I suspect this happens from the stack. I don't get API MAC callbacks indicating any errors.

  • I tested this with co-processor (in collector mode as well). The same thing happens.
  • Kasun, I tested this scenario using the out-of-box firmware and am not able to reproduce your issue. Have you tried using the debugger to see where the device gets stuck?
  • Hi Brocklobsta,

    It dosen't get stuck. Its in CPUwfi() function.The out of the box firmware is not for beacon mode. Did you change the beacon order? And how many sensors did you connect? I got this issue after letting it run more than an hour or so. Also i changed the reporting interval of the sensor to 1 second. So the channel is a little-bit occupied. Please refer the projects i have uploaded.

    These are the settings I am using right now. Please note I m using beacon mode

    Sensor example:
       config.h
                 CONFIG_BEACON_ORDER                 8
                 CONFIG_SUPERFRAME_ORDER       2 
                 CONFIG_SCAN_DURATION                8
                 CONFIG_REPORTING_INTERVAL      1800

       sensor.c
                 MIN_REPORTING_INTERVAL              150
                 MAX_REPORTING_INTERVAL             1500

                 MIN_POLLING_INTERVAL                    500
                 MAX_POLLING_INTERVAL                  2000

    Collecotor example:
       config.h
                CONFIG_BEACON_ORDER                 6
                CONFIG_SUPERFRAME_ORDER       2

    Appreciate your help on this.

    Thanks and best regards,

    Kasun

  • The beacon order and super frame order need to match on the sensor and collector projects.

  • Hi,Brocklobsta.
    I meet the same problem in cc1310,simplelink cc1310 1.40 SDK,beacon mode.
    14 end devices join the network,and devices send a message to its coordinator per 30 sec.after two hours ,the coordinator stop sending beacon.I must reset it.
    But when no devices join the network,the coordinator works fine,and sends beacon normally.

    These are the settings I am using right now.
    Sensor example:
    config.h
    CONFIG_BEACON_ORDER 5
    CONFIG_SUPERFRAME_ORDER 4
    CONFIG_SCAN_DURATION 5
    CONFIG_REPORTING_INTERVAL 30000

    Collecotor example:
    config.h
    CONFIG_BEACON_ORDER 5
    CONFIG_SUPERFRAME_ORDER 4

    Thanks!
  • Ruimao,

    I was able to reproduce your issue on two occasions using the same config.h settings.

    I am currently debugging a potential cause.

    Derrick
  • Hi Ruimao,
    Did you find a solution for this one?
  • Hey,

    We have identified the issue and it can be fixed with a library update. Please use the attached library 7028.maclib_secure.a

    This issue will be patched in the next release coming in a month or so.