Other Parts Discussed in Thread: TMP117
Hi
I am kind of struggling with the TMP117EVM. The GUI starts with no problems, however after this there are some issues:
1. When I go to the Settings tab, if i want to select a contonuous data mode with 1 sec sampling rate, is it correct to select CC from the uppermost left scroll and then the corresponding averaging method that yields 1 sec CC? Because when I do this and then save the cvs I get a series of identical data points with slightly different timestamps, like
0,29.796875,13:45:34:865 1,29.796875,13:45:34:963 2,29.796875,13:45:35:245 3,29.796875,13:45:35:386 4,29.8203125,13:45:35:521 5,29.8203125,13:45:35:654 6,29.8203125,13:45:35:792 7,29.8203125,13:45:35:929 8,29.8203125,13:45:36:062
it is like the sensor does not care and gives me just the average values for all the timestamps used for averaging. Is this counted in the max samples point that can be saved? Because if even if I say sampling rate 1Hz and then the sensor keeps sending at 100-130 ms than the max data points to be saved are too few for my application
2. In the plot tab it seems the logging does not start until I change the read delay from 100ms to 1s. No lines are plotted until that moment. When I change it I see some kind of graph rolling out but then maybe the graphs stops (I suppose it is because it has reached max number). It is not clear at all when the logging starts and if changing the read delay I influence the sampling rate at all. In the csv file I always see the same 100-130 ms interval between timestamps no matter what. And then what happens when the graph stops? Is it still logging but overwriting previous data?
3. If I want to do another measure is there some way to restart the logging without having to quit the EVM GUI and then restarting from terminal? Because now every time the plot gets stuck I can hit "Erase data" or "reset" until the end of time and still no answer apparently
Overall the system seems not responsive