• State Not Answered
  • Replies 15 replies
  • Subscribers 75 subscribers
  • Views 1840 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 252198
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

thingy 52 crash

Marty de Vries

We recently purchased a few Thingy 52s, and we're very impressed with the simplicity!

After playing with the Thingy 52,and upgrading the FW to 2.2.0, I noticed that the device locks up after a while. This manifests itself as a blinking yellow/green LED, and it's not possible to connect to the Thingy anymore.

The only way to get back control is to turn the power off and then back on again.

In 'normal operation', the blue LED is flashing away happily, and when the device enters sleep, pressing the button on the front of device or shaking it usually works. However, this 'locked up' state appears quite often.

Any ideas?

-Marty.

Parents
  • 0

    Pressing the button to wake up the device seems to be the problem. Any chance that you can update the FW to make this less sensitive?

  • 0 in reply to Marty de Vries

    Hello Marty,

    Marty de Vries said:
    It's the flashing yellow, which means DFU mode. That's clear now -thanks!

    I am happy that my comment proved useful to you!

    Marty de Vries said:

    I noticed that the flashing blue LED turns off after a while, and that you can't connect to the thingy anymore via the app, without waking it up.

    I pressed on the front button to wake up the device, as the plan would be to have the thingy attached to the wall.

    Are you running the firmware as provided, or have you made any modifications to it?
    Have you seen the Thingy 52 SDK github? You may change this behavior to me more in line with what you would like.
    The provided Thingy:52 firmware showcases all the platforms functionality - which might be more than you need for your project. To conserve power and increase battery life I would recommend creating an application that does the specific job you have in mind.

    Marty de Vries said:
    On another note, I also noticed that the temperature reading is about 2-3 degrees too high. Any ideas?

    I have never heard about the sensor being off by 2-3 degrees before.
    How did you identify this offset - did you measure the temperature with an alternate source for cross referencing, and if so: what is this other source?
    Could you also elaborate more on the test setup?

    Best regards,
    Karl

     

Reply
  • 0 in reply to Marty de Vries

    Hello Marty,

    Marty de Vries said:
    It's the flashing yellow, which means DFU mode. That's clear now -thanks!

    I am happy that my comment proved useful to you!

    Marty de Vries said:

    I noticed that the flashing blue LED turns off after a while, and that you can't connect to the thingy anymore via the app, without waking it up.

    I pressed on the front button to wake up the device, as the plan would be to have the thingy attached to the wall.

    Are you running the firmware as provided, or have you made any modifications to it?
    Have you seen the Thingy 52 SDK github? You may change this behavior to me more in line with what you would like.
    The provided Thingy:52 firmware showcases all the platforms functionality - which might be more than you need for your project. To conserve power and increase battery life I would recommend creating an application that does the specific job you have in mind.

    Marty de Vries said:
    On another note, I also noticed that the temperature reading is about 2-3 degrees too high. Any ideas?

    I have never heard about the sensor being off by 2-3 degrees before.
    How did you identify this offset - did you measure the temperature with an alternate source for cross referencing, and if so: what is this other source?
    Could you also elaborate more on the test setup?

    Best regards,
    Karl

     

Children
No Data
Related
Terms of service