HDC2080: Part Recommendation to Read Temp & Humidity on power up

Brad -

No, we don't have any with an MCU or a "from POR" auto state machine.

in this case, the issue is just with using this Aardvark tool, correct? in a real development, there would be an MCU - and this device looks to be standing in for that. IN reading the user manual, i don't see any blocking points to using the Aardvark (as the MCU) with the HDC2080. I can see that is has APIs for I2C writes and reads, which is all that is required. 

Perhaps if you shared details of where they saw a blocking point, we can help get past that. 

I would actually recommend that you use one shot mode, since you are not using the interrupt line - but if you really need to use AMM, then you should at least read 0x04 register before reading out the data.

So, in this case, for AMM with no DRDY/INT usage, after power up, you would send 0x50 to 0x0E, then a 0x01 to 0x0F, then about each second, you should read 0x04 for 0x80, if 0x80, then read 0x00 through 0x03 registers.  

Byte swapping or left shifting is just one line of c code. 

For example, from an Energia sketch for the HDC2080 (not directly translatable, but you can see how simple it is): 

Wire.beginTransmission(65); // transmit to HDC2080 device address 0x41 (0x82 (write), 0x83 (read))
Wire.write(04); // pointer
Wire.endTransmission(); // stop transmitting
Wire.requestFrom(65, 1, 1); // request 1 bytes from HDC2080 slave device, register 0x04 (should be 0x80)
Wire.readBytes (iBuff_INT_REG, 1);
HDC2080_INT_REG = iBuff_INT_REG[0];
if (HDC2080_INT_REG == 128)
{
Wire.beginTransmission(65); // transmit to HDC2080 device address 0x41 (0x82 (write), 0x83 (read))
Wire.write(00); // pointer
Wire.endTransmission(); // stop transmitting
Wire.requestFrom(65, 4, 1); // request 4 bytes from HDC2080 slave device, registers 0x00 through 0x03
// math here for HDC2080 output
while (Wire.available())
{
Wire.readBytes(iBuff_HDC2080, 4);
HDC2080_hum_MSB = iBuff_HDC2080[3] << 8; // shift left
HDC2080_hum_DEC = (HDC2080_hum_MSB + iBuff_HDC2080[2]); // get value for calculation, made from iBuff index array values 3 and 2 for humidity reading.
HDC2080_hum_percentage = ((float)(HDC2080_hum_DEC) / 65536) * 100; // do math according to the HDC2080 datasheet, page 18 www.ti.com/.../hdc2080.pdf
Serial.print(", ");
Serial.print(HDC2080_hum_percentage); // print out %RH to terminal
Serial.print(" ,");
HDC2080_temp_MSB = (iBuff_HDC2080[1] << 8); // shift left
HDC2080_temp_DEC = (HDC2080_temp_MSB + iBuff_HDC2080[0]); // get value for calculation, made from iBuff index array values 0 and 1 for temp reading.
HDC2080_temp_celcius = ((float)(HDC2080_temp_DEC) / 65536) * 165 - 40; // do math according to the HDC2080 datasheet, page 18 www.ti.com/.../hdc2080.pdf
Serial.print(" ");
Serial.println(HDC2080_temp_celcius); // print out T to terminal
}

Its no issue I think - but is there a reason for using the Aardvark vs. using MCU platform like LaunchPad? we can provide sketches that will work on all TI MCU platforms, from MSP430 G series to SimpleLink.