TI HDC1000EVM Sensor Evaluation Module

Look under tab for Create, you should see RoadTest Review to click on.

Clem

That's a good point, I don't see the write review link anymore. Is this an artifact of the new invisible applicant feature? element14Dave

Hi.. can somebody plz help me out I am not able to publish my review of this roadtest

Interesting. I still have my suspicions that the constant offset is actually related to the constant heat on the board generated by the circuitry. When I mentioned nearby source, I didn't really mean nearby external sources like PC vents, and I instead meant sources external to the sensor on the board.

I am currently working on an application that uses these sensors, and I've compared the Humidity with a few calibrated meters (lower cost ones mind you), but it does appear to fall within the datasheet specifications for accuracy. Best of luck with your testing!

I had the EVM at the usb port furthest from the processor and I placed the NIST traceable next to it.  If I really wanted to be serious about the temperature, I'd compare it to our Ertco-Hart, which is accurate to 0.001C.  The difference in the temperatures is most likely just a basic offset issue.  Since the temperature varied by the same amount throughout the testing (with one exception).  Since the humidity was my main item of concern, I wanted a comparison with a known source.

Not sure how your testing was done, but the temperature accuracy is supposedly +/-2C. I suspect a possible reason for the .6C discrepancy may be heat from nearby sources (like other chips and analog circuitry on the board).

Finished my comparison to an NIST traceable source.  It fell within the accuracy of the device, so nothing new there.  I didn't check the accuracy of the temperature, and but it seemed about 0.8C high.  I've begun the testing of the device in the crawlspace under the house.  Immediately noted a 70%+ humidity condition, so personally, that's something for me to deal with.  It will also give an idea about harsher environments.  I would like to also note that the I2C on the EVM handles 7m of CAT5 cable for signals without a problem.

I'm working on a project that utilizes this sensor and an MSP430 (just like this devkit). TI is working on releasing source code to do this (or so they said 6 months ago in the e2e forums, and then again when I inquired recently), but I ended up just taking a few days and doing it myself from scratch. Sensor is excellent.

I'm in Central Kentucky and still haven't recieved mine yet! Planning to test it outside with a RPi2 camera and make a nice video when we're done! We have a few more applications for the device, but they will be revealed when we make the video.

Patiently waiting arrival!

I'd really like to post my number crunches, but my overnight logging crapped out as did my attempt from 6:30pm until now.  I'll try to check the sensor against the one at work tomorrow, then I think I'll be detaching it to try it with my pi or my mini.

I did have the same issue.  The GUI also didn't log anything in the file.  So far the readings have been fairly steady for the 0.5 seconds 36000 reading set.  I'm running a 1 second set for overnight, then I'll crunch the numbers for both datasets and post the statistics.   Let me know how the arduino trial goes.  I'm thinking of trying that after I do a calibration run against a traceable source.

John, I'm having the exact same issues. Sometimes it takes decent data. I've also seen it hiccup as well, as in I ask for data every 5 seconds and it's clear that one data point took 10 seconds.

I'll have to check my logfile from last night.  The GUI wasn't updating the graphs, but I had been messing around with the zoom on it.  I was working on a different project, so I didn't really think about it.  I'll let you know what I find.

Has anyone else been seeing reliability problems with the GUI for this board?  Sometimes it runs fine, but at least half the time for me the logging just stops and the EVM becomes non-responsive.  I end up having the disconnect and reconnect the EVM and restart the GUI to recover. I'm running it on two different PCs both with Win7 (64 bit) and seeing the same problems on both.  I'm not sure what is going on, but I plan to detach the sensor tonight and give it a test run connected to an arduino.

Oh, yes, I've noticed that too.  It's a bit annoying and confusing.  Definitely worth a mention for the review.

I've found the number of samples does not actually mean number of samples for me. Once I start collecting data it doesn't stop until either there was an error or I click stop. Samples only changes the horizontal scale on the graphs below.

Michael, yes, I've got it on a Windows 7 box.  I hadn't noticed any problems with the GUI, but I've just been trying stress test and logging.  I'll give it a look with giving it a specific number of samples tonight.  I did notice that if you're trying for a reading every 1/2 second, it takes about 5 seconds or so to settle into the proper interval.  I also didn't have any noticeable heating effect from going under 1 second.

You're running Windows 7 I'd assume? I'm in Windows 8 and I had to do the advanced boot to install the unsigned drivers. The software is also acting up. Sampling either stops early or keeps going beyond the requested number. I haven't wired it into an embedded system yet.

It's HERE!!!!!  Now is it sad or awesome that I already had the software installed and just threw everything else I had on the floor, opened the package and had it running less than five minutes after I got home.  And just to let you all know...it's 22.1C and 34.7%RH!

I guess my should be here soon.  This is so cool.  My first experiment is going to be to compare its output to an NIST traceable temp/humidity device.