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.

CC3200STK-WIFIMK: cc3200 sensortag crashed every 20-24 hr

Part Number: CC3200STK-WIFIMK
Other Parts Discussed in Thread: CC3200

Hi, my cc3200 sensortag stops advertising and sending data every 20-24 hours that I need to power recycle to make it works again. any thoughts why this is happening and how to fix it ? 

Thanks

  • Hi Sepehr,

    How do you have the SensorTag configured? Have you tried changing out the batteries?


    Thanks,
    Alexis
  • I configured as connecting to my home Wifi router and not going to sleep. and also I am using 3V DC adapter (so Iam not using battery).

  • I set it in station mode and test it for 5 days and I logged data and I tracked exactly how long does it take to crash and it stopped working every day as below :

    day 1 : crashed after 19Hr - 6 min

    day 2 : crashed after 22 Hr - 48 min

    day 3 : crashed after 18 Hr - 25 min

    day 4 : crashed after 20 Hr - 10 min

    day 5 : crashed after 19 Hr - 22 min

    I also checked my internet by sending a ping every 30 second from my computer to make sure I didnt have any internet down when the CC3200 crashed.

    Is it possible that it get out of memory for some reason after some time ? 

    has anybody else had that issue ? 

    Is there any timer/counter in FW that needs to be reset ?

    Do we have access to FW ?

  • Hi Sepehr,

    Unfortunately no you do not have access to the FW. The CC3200STK-WIFI is only for demonstration purposes whereas the Launchpad is the primary development platform. It may be beneficial for you to switch over to the CC3220 LaunchPad and the Sensors BoosterPack Plug-In Module, as this option provides you with access to the same sort of sensor data while also allowing you to debug your application.

    Thanks,
    Alexis
  • Hi Alexis,

    Thank you for your reply. I know this is a demonstration purpose device but it just stops working after ~20 hours which doesn't make sense.

    I bough the devpack display for it and it actually shows the time remaining on it which is 56536 seconds (18.2 hours) written on the display which is 2^16 which means its the 16 bit number for timer events. so there is really no way to run this device more than 56536 seconds ? or I am doing something wrong. why this is never documented anywhere ? at least you should know this when you buy this ? as I couldn't find any documentation regarding this, I keep thinking I am doing something wrong. 

    Thanks,

    Sepehr

  • Hi Sepehr,

    I understand your concern. I'll go ahead and review the application to try an confirm whether this is a limitation in the design. If so, I'll make sure the documentation is updated to reflect it.

    Best Regards,
    Ben M