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.

[Marty de Vries]

Thanks. There was about a -/+2 degree difference between them. 

batch number: 2019.42

[Karl Ylvisaker]

Hello again, Marty

I have spoken with some project engineers with experience working on the Thingy:52 platform, and while they were not completely unsurprised that the temperature measurements had an offset, they had never heard of / experienced themselves that it would be as much as +/- 2 C. Perhaps you could try to average the temperature readings from the gas and humidity sensor to achieve a better result - thought I have not tested this myself, so this is just a guess on my part.
However, if you require very accurate sensor data for your application then you might have to add this as an external sensor for this purpose.

Furthermore, there are no notes from testing relating to the temperature sensors for the batch you mention.

Best regards,
Karl 

[Marty de Vries]

Thanks for looking into this. I think that we need to go through the FW carefully, and tweak the performance.

[Karl Ylvisaker]

No problem at all Marty, I am happy to help!

Marty de Vries said:

I think that we need to go through the FW carefully, and tweak the performance.

This sounds like a good idea to really get familiar with the Thingy:52 prototyping platform!

Please do not hesitate to open a new ticket if you should encounter any issues or questions in the future.

Good luck with your development!

Best regards,
Karl

[Marty de Vries]

thanks. Actually, there was one last question that I had regarding the motion sensor. Although the app works well, I noticed that when I dropped the thingy, not all 3 axes converged to 0g. At most, only two axes registered 0g. Any ideas?

-Marty.

[Karl Ylvisaker]

Hello Marty,

How was the thingy dropped? I would assume it was dropped "flat" - no spin, and no rotation.
Just to be sure, which of the eMPL outputs are you referring to by the way, and what was their values?
Depending on which output you are reading, this might be as expected.

As we diverge further from the original ticket, I would ask that you open a new ticket for further questions in order to keep the forums tidy.
If you tag me in any future ticket then we may continue the conversation there.

Best regards,
Karl