thingy 52 crash

RE: thingy 52 crash

Karl Ylvisaker — Tue, 07 Jul 2020 07:31:45 GMT

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

RE: thingy 52 crash

Marty de Vries — Mon, 06 Jul 2020 12:42:30 GMT

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.

RE: thingy 52 crash

Karl Ylvisaker — Thu, 02 Jul 2020 11:10:05 GMT

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

[quote user="Marty de Vries"]I think that we need to go through the FW carefully, and tweak the performance.[/quote]

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

RE: thingy 52 crash

Marty de Vries — Thu, 02 Jul 2020 10:57:01 GMT

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

RE: thingy 52 crash

Karl Ylvisaker — Thu, 02 Jul 2020 09:35:51 GMT

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

RE: thingy 52 crash

Karl Ylvisaker — Wed, 01 Jul 2020 08:07:39 GMT

Thank you for the information, Marty!

I will discuss this with my colleagues to see if anyone else have heard about similar measurements.

Best regards,
Karl

RE: thingy 52 crash

Marty de Vries — Tue, 30 Jun 2020 15:20:55 GMT

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

batch number: 2019.42

RE: thingy 52 crash

Karl Ylvisaker — Tue, 30 Jun 2020 14:50:43 GMT

I understand, thank you for performing the test.

Did all the three thingy's had the same temperature measurement, regardless of if they were still in the casing or not, and regardless of how long the battery had been in use?
This sounds very strange - I have not heard any other complaints about offset in the temperature sensors, to my knowledge they are fairly accurate. From the datasheet of the supplier the minimum accuracy is stated to + - 0.5 C within the 15 - 40 C operating range.
Could you provide me with the production week numbers for the Thingys you have on hand? There should be a small sticker on the side of the thingy:52 box.
With this, I can go through the logs to see if there has been any other mention about inaccurate measurements earlier.

Best regards,
Karl

RE: thingy 52 crash

Marty de Vries — Tue, 30 Jun 2020 14:31:04 GMT

I ran a test on three thingys sitting next to each other. There was about a -/+2 degree difference between them. Removing the thingy from the casing didn't improve matters either. Perhaps the temperature sensor is a little crappy, or that there's a issue with the compensation algorithm?

RE: thingy 52 crash

Karl Ylvisaker — Tue, 30 Jun 2020 13:19:44 GMT

Hello,

[quote user="Marty de Vries"][/quote]

Placing two thingys next to each other, and also an analog and digital indoor weather station device next to the thingys, I compared the temperature readings. The analog and digial weather station were very comparable, but the Thingys were a little high.

The temperature seems a little better today, when comparing this with a digital thermometer. I assume that the device needs to be on for a while for the readings to settle. Is this true for temperature? Another explanation could be that the when the Thingys were on for a while (1 hour), the battery got hotter.

I have not heard anyone else mention an increasing offset in temperature readings from the Thingy:52, but I suppose it is reasonable following 1 hour of operation, especially considering that you could feel a temperature increase in the battery, along with the temperature sensors close proximity to the battery.
Could you remove the PCB from the plastic casing with the battery(leave the battery connected to the PCB, but leave the battery in the casing), and repeat the measuring procedure? If it is the battery causing the offset in temperature then this should be evident by this test. The PCB is secured in the casing by the two clips.

The sensors can continue writing to the nrf52 while it is sleeping if they are using easyDMA. This will only require that the MCU wakes up when the data is written to RAM, to process it.
However, I do not think that the 2.2.0 firmware uses easyDMA for its sensors by default. Looking into the source code on github it seems that they do not use the easyDMA feature.
Are you able to see data for the time the device has been sleeping when you wake it up from sleep?

Best regards,
Karl

RE: thingy 52 crash

Marty de Vries — Tue, 30 Jun 2020 10:05:18 GMT

This FW is the default Nordic 2.2.0 version - no modifications.

I assume that all sensors keep on running when the Thingy is in sleep?

thanks.

RE: thingy 52 crash

Karl Ylvisaker — Tue, 30 Jun 2020 08:41:06 GMT

Hello Marty,

[quote user="Marty de Vries"]It's the flashing yellow, which means DFU mode. That's clear now -thanks![/quote]

I am happy that my comment proved useful to you!

[quote user="Marty de Vries"][/quote]

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.

[quote user="Marty de Vries"]On another note, I also noticed that the temperature reading is about 2-3 degrees too high. Any ideas?[/quote]

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

RE: thingy 52 crash

Marty de Vries — Mon, 29 Jun 2020 16:03:14 GMT

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?

RE: thingy 52 crash

Marty de Vries — Mon, 29 Jun 2020 12:21:59 GMT

Dear Karl,

It's the flashing yellow, which means DFU mode. That's clear now -thanks!

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.

Perhaps I've missed something?

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

-Marty

RE: thingy 52 crash

Karl Ylvisaker — Mon, 29 Jun 2020 11:41:34 GMT

Hello,

[quote user=""]we're very impressed with the simplicity![/quote]

I am happy to hear that you enjoyed the Thingy:52!

[quote user=""]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.[/quote]

Could you elaborate on what application or sample you were running the Thingy:52 with at the time? Could you also elaborate how you have programmed your device?
Please see this ticket regarding flashing .hex files to the Thingy:52.
Blinking green means that the Thingy:52 is in bootloader mode. Bootloader mode can be entered by holding down the button upon power-up. Is this something you might have done accidentally?
Rapidly fading in an out yellow LED means that the Thingy:52 has entered DFU mode.
Both of which will be resolved by a power-cycling, placing the device back at the application start.
So, what remains is to identify the reason for the Thingy:52 to enter the bootloader/DFU mode.

To find out more about why this happens, I will need to know more about what application the Thingy:52 is running.

Looking forward to resolving this issue together,

Best regards,
Karl