• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 518 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMP006EVM: SW-tool gives incorrect temperature reading.

Arun Krishna34
Prodigy 40 points

Part Number: TMP006EVM

 Hi

I’m trying to log temperature data by using the sm-usb-dig module with a TMP006EVM module. The SW I’m using is also called TMP006EVM.

I have more than 5 devices of each which I have tried to get in contact with and even interchanged them with no luck.

I mostly get a failure “TMP006 did not ack” on almost all of them. One of the sensor does give data but it is incorrect. I have attached the log data from this sensor.

The data are recorded in normal ambient condition.

Most of the devices have been working before when I was running windows 7. Now we have upgraded to win 10 and it is not working anymore.

Is it because the driver is not compatible with windows 10? Have anyone else similar experience with windows 10 and this device + SW tool?

Please advice

Time,Local Temp,Object Voltage,Object Temp
1,128,218,312,0,001,238,9
2,157,154,312,0,001,180,3
3,143,90,312,0,001,127,5
4,16,154,312,0,001,180
5,11,90,312,0,001,127,5
6,125,218,312,0,001,238,9
7,127,154,312,0,001,180,3
8,157,90,312,0,001,127,7
9,173,90,312,0,001,127,7
10,125,90,312,0,001,127,6
11,127,154,312,0,001,180,2
12,156,90,312,0,001,127,7
13,157,90,312,0,001,127,6
14,157,90,312,0,001,127,5
15,189,90,312,0,001,127,5
16,159,218,312,0,001,238,9
17,156,90,312,0,001,127,6
18,159,90,312,0,001,127,7
19,159,90,312,0,001,127,7
20,157,154,312,0,001,180,2
21,202,90,312,0,001,127,9
22,208,90,312,0,001,127,8
23,22,90,312,0,001,127,6
24,187,90,312,0,001,127,6
25,203,154,344,0,001,180,2
26,206,218,344,0,001,239
27,202,90,344,0,001,127,7
28,22,90,344,0,001,127,7
29,22,90,344,0,001,127,8
30,22,218,344,0,001,239,1
31,234,90,344,0,001,127,7
Time,Local Temp,Object Voltage,Object Temp

br

Arun

  • 0
    TI__Mastermind 35775 points
    Hi Arun,

    I don't have a Windows 10 machine available to me, but I'm working on solving that. I'll update you when I know more.

    Thanks,
    Ren
  • 0 in reply to Ren Schackmann
    Prodigy 40 points
    Hi Ren

    Thank you very much.

    br
  • 0 in reply to Arun Krishna34
    TI__Mastermind 35775 points
    Arun,

    I don't see any issues with TMP006EVM on Windows 10.

    Have you made a modification to the EVM connections? This error should indicate that the TMP006 is not connected to the SM-USB-DIG.

    Thanks,
    Ren
  • 0 in reply to Ren Schackmann
    Prodigy 40 points
    Hi Ren,

    I have a bunch of these devices and we have modified some of them with a "loose" to address multiple devices in our test setup. Which still is working by the way, and we have some without any modification. The test setup we have is a bit bulky and impractical to move around therefore I wanted to use this SM-USB-DIG device for that purpose.

    I am almost 100% sure that the SM-USB-DIG device is found:
    1. When I do not have in connected to the PC and start the TMP006EVM program then I get an error msg. stating no device is located.
    2. By toggling the EVM Power control button I can see the indicator LED reacts accordingly.
    3. With one device I DO get data but the values I get are incorrect -231 on local temperature and 1,4E+2 on Object temperature.
    4. With other devices I get a "TMP006 not ack".

    I have not modified any I2C address the values are A0 = 0, A1 = 0, I2C Read = x81, I2C Write = x80.
    Are they still correct?

    I will try with another PC just in case and get back to you.
    br
  • 0 in reply to Arun Krishna34
    TI__Mastermind 35775 points
    Yes, I agree that SM-USB-DIG is found and correctly working on your computer. I say this based on the lack of error message and the toggling of the power indicator. This eliminates the possibility of a driver conflict in Windows 10.

    My question remains: Have you created an issue between the SM-USB-DIG and the TMP006 device? The "did not ack" message indicates that the TMP006 is not responding to the SM-USB-DIG's attempts to communicate with it.

    Yes, the 8bit addresses are 0x81 and 0x80 when the A0 and A1 pins are connected to DGND.

    Please contact me over email if you would like to setup a call regarding this issue.

    Thanks,
    Ren
  • 0 in reply to Ren Schackmann
    Prodigy 40 points
    Hi Ren

    I found one device that works... There is something with the TMP006 like you mention...
    But I'm still puzzled that the ones I had which were not working SM-USB-DIG, are working fine in our test setup.

    Most importantly I can continue with what I wanted to do.
    Thank you very much for your assistance.

    Have a great day!

    br
    Arun