• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 299 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

HDC2080: Taking more time for data ready

HDC2080: DRDY_STATUS || Bit is not setting some times after starting measurement

Rakesh Rajbhar
Intellectual 630 points
Part Number: HDC2080


Hi All,

I had an issue with HDC2080 and I posted the query on the forum and below is the link, I have provided my code flow as well. please go through this

The solution provided on that thread seems to be working fine, but now we found that sometime after starting the measurement and waiting for more then 300ms when I am checking DRDY_STATUS bit in 0x04 register it is not getting set.

can you please help us with the solution?

Please let me know if you need some more information from my side.

  • 0
    TI__Mastermind 28075 points

    Hi Rakesh,

    Is this workaround no longer working? Keep in mind that you would need to reapply it after any soft resets or POR. 

    I think the only way to debug this would be to setup the DRDY/INT pin, and capture the behavior (along side your reads) on an oscilloscope or logic analyzer. That way we can ensure that no other reads are inadvertently clearing the interrupt.

    Best Regards,
    Brandon Fisher

  • 0 in reply to Brandon Fisher94
    Intellectual 630 points

    Hi Brandon,

    Thanks for the response.

    regarding the workaround suggested in that post, I was not able to run that custom commands I was not getting acknowledge for that commands, so instead that  I just applied soft reset and that seems to be working but here the issue is different, here DRDY_STATUS bit is not getting set even though start measurement gets success.

    Is there any reason or when it is possible that this bit may not get set of get's cleared before we read that?

    we are reading temperature at every 1 min. and at every one minute after reading temperature we are turning OFF the sensor using microcontroller GPIO which is the power source for the sensor.

    this issue comes sometimes only, arround once in 30-40 minutes.

    we might not be able to check Interrupt pin on CRO as this issue is random.

  • 0 in reply to Rakesh Rajbhar
    TI__Mastermind 28075 points

    Hi Rakesh,

    Rakesh Rajbhar said:
    regarding the workaround suggested in that post, I was not able to run that custom commands I was not getting acknowledge for that commands, so instead that  I just applied soft reset and that seems to be working but here the issue is different, here DRDY_STATUS bit is not getting set even though start measurement gets success.

    The custom command workaround from that thread should eliminate the issue entirely, but we should have noted that the writes of 0xF1 and 0xE7 will both be NAK'd, the write to 0xFF will be ACK'd though.

    Rakesh Rajbhar said:

    we are reading temperature at every 1 min. and at every one minute after reading temperature we are turning OFF the sensor using microcontroller GPIO which is the power source for the sensor.

    this issue comes sometimes only, arround once in 30-40 minutes.

    we might not be able to check Interrupt pin on CRO as this issue is random.

    If you ignore the NAKs from the custom command mode and try that method I think that would be the easiest path forward, since the intermittent nature of the failure seems to make it difficult to capture. Conveniently, since you are using GPIO power and shutting down between reads, the higher current draw that Josh mentioned as a tradeoff should also not be a problem. You would need to enter those custom commands every time you power the device back up though. 

    Best Regards,
    Brandon Fisher