After boots-up, the HDC2080 value seems to be working fine i.e. value between 27 to 32 degrees C.
But after some time (approx after an hour), the temperature drops to 22 degrees C.Withing 10 seconds, the temperature reading drops to 22C from 32C.
We have few sensors running on trial(testing) units but only one board gives this type of value, i.e. common software is used across all the boards.
I2C protocol analyzer screenshot for your reference.
Hi Josh,
I have corrected the timing/delay in the application code. But still, issue persists maybe for a different reason.
Could you help me to locate the issue?
Temperature drop issue #1:
The results are fine till the value of temp MSB 0x01 [timestamp 101.17.898]
Still, I am seeing a sudden drop in temperature. Any comments?
Measurement Configuration issue #2:
Do you know why the value of the reg Measurement Configuration reading 0xF6?
Hi Josh,
This issue is getting reproduced in my setup again.
Do you have any recommendations?
Is there any initialization I need to do for this part?
The application does the following init(HDC2080_open) on boot-up and then goes in a loop: trigger + delay + read TRH
HDC2080_Handle HDC2080_open(unsigned int HDC2080Index, I2C_TypeDef * i2cHandle,
HDC2080_Params *params)
{
HDC2080_Handle handle = &HDC2080_config[HDC2080Index];
HDC2080_Object *obj = (HDC2080_Object*)(HDC2080_config[HDC2080Index].object);
// HDC2080_HWAttrs *hw = (HDC2080_HWAttrs*)(HDC2080_config[HDC2080Index].hwAttrs);
uint16_t data;
//if (obj->i2cHandle != NULL) {
// return (NULL);
//}
obj->i2cHandle = i2cHandle;
if (params == NULL) {
params = (HDC2080_Params *) &HDC2080_defaultParams;
}
/* Perform a Hardware HDC2080 Reset */
if (HDC2080_writeRegister(handle, CMD_SW_RST, HDC2080_RST_DRDY_INT_CONF_REG)) {
//usleep(WAIT_POST_RESET * 1000U);
//for (volatile int i = 0; i < WAIT_POST_RESET * 1000U; i++) {
// Do nothing
//}
//UDELAY_Delay(WAIT_POST_RESET * 1000U); //DES test to allow I2C to settle???
#ifndef LX_MICRO_SECONDS_DELAY_NOT_SUPPORTED
UDELAY_Delay(WAIT_POST_RESET * 1000U);
#else
sl_sleeptimer_delay_millisecond(WAIT_POST_RESET);
#endif
data = (uint8_t)params->measurementMode | (uint8_t)params->tempResolution |
(uint8_t)params->humResolution;
if (HDC2080_writeRegister(handle, data, HDC2080_MEAS_CONFIG_REG)) {
data = (uint8_t)params->outputDataRate | (uint8_t)params->interruptEn |
(uint8_t)params->interruptMode | (uint8_t) params->interruptPinPolarity;
if(HDC2080_writeRegister(handle, data, HDC2080_RST_DRDY_INT_CONF_REG)){
data = (uint8_t) ~(params->interruptMask);
if(HDC2080_writeRegister(handle, data, HDC2080_INT_MASK_REG)){
//Reset Interrupt Masks
if(HDC2080_readRegister(handle, (uint16_t *) &data, HDC2080_DRDY_INT_STATUS_REG)){
if (params->callback != NULL) {
obj->callback = params->callback;
//GPIO_setCallback(hw->gpioIndex, obj->callback);
//GPIO_enableInt(hw->gpioIndex);
}
}
}
}
}
return (handle);
}
obj->i2cHandle = NULL;
return (NULL);
}
Dear Ganesh -
there is no real reason to issue a software reset on the device after power up - I know some of the competitive devices require it, but the HDC2 does not. If you implemented the firmware workaround for the register issue previously - every time you do a POR or software reset, you need to re-run that.
Also, I would still recommend to read all the measurement value registers at once, it will save you time.
like this:
