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.

HDC2010EVM: Humidity data is not linear at over 60-%.

Guru 11170 points
Part Number: HDC2010EVM

Hello E2E,

Our customer have two EVM. They are evaluating now them. However, two EVMs output data are not look like for normaly.

No.1-EVM;
At over 60-% humidity, the output data is less than ambient. Please see the Humidity.pdf.

No.2-EVM;
In registor address 0x09, the value is be change during operation.
There is a phenomenon that "0x22" is arbitrarily set in the humidity offset register at address 0x09, and it returns to "0x00" irregularly.
Please see the follow files;

180524 HDC2010 Reg.zip

180524 HDC2010.xlsx

 :png
          GUI graph view with EVM.
 :zip
          Red squares. Points the value of register changes arbitrarily.
 :excel
          Log data output.
Measure in paper bag.
Address 0x04 and 0x09, them register value are frequent to change.

Are they simply failure? or malfanction for device?
Do you know the means to correct it?

Please help us.

Regards,
ACGUY

  • Hi AC guy,

    Thanks for sharing the data.
    Bit 5 of reg 0x4 is TL_STATUS, the Lower threshold value programmed that will trigger an interrupt from "0" to "1" when the measured temp goes below the predetermined value. What value was programmed there, reg 0x00?

    The other behavior is not something expected. We will have to check in our labs. SInce Monday is holiday in US someone will reply on Tuesday with results of the investigation.

    Regards,
    Jose
  • Hello Jose,

    Thank you for reply and your concern.
    They tried devices swap on two EVMs. Issues are incident on devices.
    They didn't modify the firmware for MSP430. It remains in its initial state.

    If their EVMs are failed, please let me know the similar case and solution.

    Regards,
    ACGUY
  • AC guy,

    As Jose mentioned, register 0x04 is an interrupt register and will convey if any thresholds have been tripped during device operation.

    Can you verify what happens when register 0x09 is programmed to '0'? Can you confirm if this offset value changes during operation? We'll have to confirm in the lab, but expect to have some more information and will update the post accordingly.

    Best Regards,
    Matt
  • Hello specialist,

    I captured the GUI movie. Please look at those attachments.

    "Data streaming.wmv"

    At room (normal room environment), ambient temperature was to be -40degC instantaneously. Humidity was to be 0% too. We didn't use the liquid nitrogen.

    "Regs.wmv"

    Measured under the same conditions as above.

    Address 0x04 (time at 01:05) and 0x09 (time at 02:25) value are frequentry modified. We didn't change the firmware. It's left default.

    Is device broken? Please let me know the cause.

    Regards,

    ACGUY

  • Hi ACGUY,

    You may need to navigate to another page to set the conversion rate (data output rate) of the device, as the register read is much faster than the default data output rate (1s).  Register 0x04 is periodically outputting 0x20, because each period is specifying that the temperature low limit is being tripped. I've noticed that the temperature lower limit is programed to 0x8E, which translates to a lower temperature value of 51.52, therefore it can be seen that after each period of conversion, the device will output 0x20 on register 0x04.

    The humidity offset register seems like it may be a software issue, however I would need to verify if I see any unusual behavior in my studies.

    Can you turn off the autoread and confirm this issue by performing a manual read?  This would be my next recommendation.

    Best Regards,

    Matt

  • Hi Matt,

    Thank you for reply.

    >> Can you turn off the autoread and confirm this issue by performing a manual read?
    ->No. I could not it by manual.

    >> The humidity offset register seems like it may be a software issue,
    -> I see. Can I solve this problem by changing the register on GUI? Or, necessary to change the firmware?

    Regards,
    ACGUY
  • Hi ACGUY,

    Have you tried to reduce the speed of the autoread?  This issue will be logged in our system and the software will be updated in future revisions.  For now, I recommend that you perform a manual read to get register information.  One experiment you can try is to reduce the speed of the software autoread, this may make it less like to create the issue you've observed.

    Best Regards,

    Matt