• State TI Thinks Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 2 answers
  • Subscribers 40 subscribers
  • Views 543 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.

CC3200STK-WIFIMK: CC3200STK-WIFIMK: Stop working after a few hours

user3864770
Prodigy 60 points
Part Number: CC3200STK-WIFIMK

I'm trying to use CC3200STK-WIFIMK as a way to collect environmental data. I know this is supposed for demo purpose only, but it's the best solution I found on the market.

I have a pythons script that pulls sensor data from 6 SensorTags from "http://[sensortag_ip]/param_sensortag_poll.html" once every one minute. However, it seems that one or two SensorTags will always stop working after a few hours. When the SensorTag stop working, I can still access the WiFi management interface by going to "http://[sensortag_ip]/", but if I access any sensor data from "http://[sensortag_ip]/param_sensortag_poll.html" or "http://[sensortag_ip]/sensortag.html", the connection will simply timeout without giving me any data back.

Any idea why this is not working?

Thanks in advance

  • 0
    TI__Mastermind 22935 points
    Hello,

    Hard to tell why it's not working without any feedback from the device. Have you tried using a packet sniffer to see what's going on over the network? Maybe you can discover an issue there.

    Does this failure consistently happen on the same devices? Also, does it always happen in the same time range?

    Jesu
  • 0 in reply to Jesu
    Prodigy 60 points

    I just got a few devices that failed again today. It's not consistently happening on the same device, it's very random.

    Also, I managed to get some response from the sensortag in the broken state:

    # curl http://192.168.141.2/param_sensortag_poll.html
<html>
<body>
<p id="tmp">Unknown Token</p>
<p id="hum">Unknown Token</p>
<p id="bar">Unknown Token</p>
<p id="gyr">Unknown Token</p>
<p id="acc">Unknown Token</p>
<p id="opt">Unknown Token</p>
<p id="mag">Unknown Token</p>
<p id="key">Unknown Token</p>
<p id="syn">Unknown Token</p>
</body>
</html>
    # curl http://192.168.141.2/param_sensortag_conf.html
<html>
<body>
<p id="tst">Unknown Token</p>
<p id="cfg">Unknown Token</p>
<p id="led">Unknown Token</p>
<p id="ito">Unknown Token</p>
<p id="rte">Unknown Token</p>
<p id="act">Unknown Token</p>
<p id="ots">Unknown Token</p>
<p id="fwr">Unknown Token</p>
<p id="mac">98:7B:F3:9A:D3:XX</p>
<p id="url">Unknown TokenUnknown Token</p>
</body>
</html>

  • 0 in reply to user3864770
    TI__Mastermind 22935 points

    Hello,

    Is this the behavior you've been getting originally or did you not get a response at all originally? If not, what did you change to start getting a response? Also, have you tried analyzing the network traffic to see what changed (if anything) when the sensor data request stops working?

    If the device misses just one of your data requests it will then enter hibernate because it goes to sleep after 90 seconds of inactivity.At that point which you have to a press a button on the sensortag to wake it back up.

    Jesu

  • 0 in reply to Jesu
    Prodigy 60 points

    After the restart, each tag works with no problem, it will return the correct result(param_sensortag_poll.html). After about 5-10 hours, some of my 6 tags (a random one or two) will start giving me the same result every time I query the sensors. Then, if I try to figure out what's wrong(param_sensortag_conf.html or sensortag.html), It will take a few minutes to load, and after that, I will consistently get that "Unknown Token" from my sensor data (and it takes a few minutes to load). I can only overcome this problem by manually restart the sensor.

    As for the hibernate, I have already set those sensors to stay awake, so I don't think that's the issue here. Also, the WiFi config interface is still up when the sensor data freezes.

    About network traffic, what do you want me to capture specifically? Also, is there a way to stop the sensors to upload to IBM cloud?

  • 0 in reply to user3864770
    TI__Mastermind 22935 points
    Hello,

    Okay so you start getting "Unknown Token" after try requesting information from the sensor to see what is going on? Otherwise it will just send the same data as if the values are not updating? Please confirm.

    Capturing the network traffic might help you discover the cause of the behavior your getting. Have you tried isolating one sensortag from other sensortags in the area and network to see if that changes anything?

    Also, there is no way to disable MQTT (IBM cloud) on the Sensortag. On a side note, I found a post token (__SL_P_REB) that can trigger a reboot on the Sensortag. A workaround could be to trigger a reboot when the data stays after some amount of data points.

    Jesu
  • 0 in reply to Jesu
    Prodigy 60 points

    To your first question, yes. It will work for a few hours, and after that, sending the same data.

    You mean setup a wireshark and capture all traffic of a sensortag? I'll try that.

    Can you tell me how to use the reboot token? I have tried "__SL_P_UM0=reboot" before, and the sensortag that freezes won't respond to this. I'll try you token then.

    Thanks!

  • 0 in reply to user3864770
    TI__Mastermind 22935 points
    Hello,

    Yes Wireshark. I don't see __SL_P_UM0 as a defined token. What caused you to try that?

    Sending a post request with (__SL_P_REB) should do the trick. I'm not exactly sure how the request needs to be sent but it shouldn't be too hard after checking how other post request are sent on Wireshark.

    Jesu
  • 0 in reply to Jesu
    Prodigy 60 points
    I see that from this website, and it seems to be working for other sensortag whose sensor data is still updating.

    github.com/.../wifi-sensortag
  • 0 in reply to user3864770
    TI__Mastermind 22935 points

    Hello,

    I saw the reset for the post request you're referring to. It works a little different from the one I suggested. Let me know if it works for you.

    Jesu

  • 0 in reply to Jesu
    Prodigy 60 points

    I just tried to force it to reboot. When the sensor data just freezes, it won't reboot and the request returned immediately. After I access "sensortag.html" and make the sensortag return "Unknown token", the reboot request (like all the other request to sensortag at this state) takes around 1 minute and the sensortag still won't reboot.

    # curl -d "__SL_P_REB=1" -X POST http://192.168.141.2
# curl 192.168.141.2/param_sensortag_reg.html
<html>
<body>
<p id="dev">Unknown Token</p>
<p id="reg">Unknown Token</p>
</body>
</html>

  • 0 in reply to user3864770
    TI__Mastermind 22935 points
    Hello,

    Have you tried to isolate a problematic sensortag to operate in it's own network? Also have you seen anything worth nothing on Wireshark around the time of failure? The idea is to figure out if there's a network or environment issue causing the freeze. Unfortunately apart from debugging that there is not much that can be done. The sensortag is for demo purposes only and cannot be debugged directly.

    Jesu