Temperature recorded on MetaMotionR do not make sense

The MetaMotionR devices that we have purchased were working perfectly for some time. However, at some point in time, we were experiencing issues whereby the devices were recording temperature at -25, below 0 and 85 degrees Celsius.

Comments

  • edited September 2019

    This will be deleted as being a useless post if you do not update as per our rules: https://mbientlab.com/community/discussion/3167/how-to-report-an-issue#latest

  • The MetaMotionR devices that we have purchased were working perfectly for some time. We are located in a tropical country with average temperatures ranging from 25 to 32 degrees Celsius. However, at some point in time, we were experiencing issues whereby the devices were recording temperature at -25, below 0 and 85 degrees Celsius. Please kindly refer to the screenshot below.

    We have tried resetting the devices by manually pushing the reset button and via the Metabase Application but to no avail.

    Here are some information that could be helpful :
    Hardware revision : 0.4
    Firmware revision : 1.4.5
    Host Device Model : Samsung A70 with Android 9



  • open the data file in a text editor and not in excel.
    It looks like excel might be reading the numbers wrong.
    Get back to me with more pics.

    • How exactly are you using the boards?
    • Is this issue affecting all of your boards?
      • How many are you using?
  • Hi Laura and Eric
    1) It is not a viewer problem. That was libre office, and also the data on our database is the same. We double checked and opened it as a raw file. It is also attached for you to view

    2) We are using the boards attached to a watch strap
    3) It is affecting 5/16 mbients.
    - 2 are displaying temperatures at 85.123C
    - 2 are displaying temperatures of -85.125C
    - 1 is displaying 0 degrees

    The rest of the boards are fine

    We also tried using an iPhone iOS13, and Raspberry Pi Metabase. Regardless they all give the same reading.

  • Also attempting to update the firmware creates the following error

  • edited September 2019

    MetaBase does not work on iOS 13 so DFUs will fail.
    We will be releasing a new version next week that will work on iOS13 (Apple has to approve the app and everyone is trying to release right now - it is a busy time of year from app releases with the new OS!).

    Regarding the temp readings, can you remove the Metawears from all the bands, hold them side by side, and display the temperature from each unit live.

    Also please make sure you are getting the temperature readings from the thermistor and not the on-die or external sensor. It is highly likely your setting of this may be wrong.

    1. Attached is the data comparing a functional mbient sensor and a broken one. The functional mbient's have been working without issue for over 6 months now.
    2. The temperature readings are coming from the thermister. It is being set using the phone, see image attached

    I believe that there is a circuit board failure causing an input to create a "high" signal.

  • @peejaay, you can file a ticket if you want -> www.mbientlab.com/support

Sign In or Register to comment.