Hi Jacob, thanks for your hard work! We have been trying to use the labview utility and it definitely works marvels and we are perfectly capable of viewing both time series data and FFTs. When using the python, though, we have not been as successful. We see the time series data now, but we are unsure of what the data we see in python means. When we run the example, it returns a list of 340 RMS values (with which we are happy) in a dictionary and temperature, battery status, etc. From time to time it returns a mems buffer error and the data doesn’t make much sense (temperatures skyrocket, battery percentage goes above 100%) we are, therefore, unsure about the veracity of the read acceleration, and we would like to know what the errors mean and if we can solve them.

Just so that you get an idea of what we are talking about, this is what we see upon executing the example code:

```
312: {'rms_z': -1071, 'rms_y': 1825, 'rms_x': 2306}, 313: {'rms_z': -1143, 'rms_y': 1745, 'rms_x': 2282}, 314: {'rms_z': -1144, 'rms_y': 1766, 'rms_x': 2268}, 315: {'rms_z': -1029, 'rms_y': 1826, 'rms_x': 2324}, 316: {'rms_z': -1053, 'rms_y': 1745, 'rms_x': 2289}, 317: {'rms_z': -1127, 'rms_y': 1760, 'rms_x': 2280}, 318: {'rms_z': -1111, 'rms_y': 1894, 'rms_x': 2323}, 319: {'rms_z': -1112, 'rms_y': 1786, 'rms_x': 2290}, 320: {'rms_z': -1115, 'rms_y': 1765, 'rms_x': 2279}, 321: {'rms_z': -1005, 'rms_y': 1846, 'rms_x': 2314}, 322: {'rms_z': -1096, 'rms_y': 1737, 'rms_x': 2324}, 323: {'rms_z': -1105, 'rms_y': 1781, 'rms_x': 2236}, 324: {'rms_z': -1035, 'rms_y': 1832, 'rms_x': 2326}, 325: {'rms_z': -1133, 'rms_y': 1777, 'rms_x': 2322}, 326: {'rms_z': -1127, 'rms_y': 1711, 'rms_x': 2247}, 327: {'rms_z': -1050, 'rms_y': 1786, 'rms_x': 2308}, 328: {'rms_z': -1099, 'rms_y': 1809, 'rms_x': 2317}, 329: {'rms_z': -1090, 'rms_y': 1773, 'rms_x': 2298}, 330: {'rms_z': -1069, 'rms_y': 1855, 'rms_x': 2328}, 331: {'rms_z': -1137, 'rms_y': 1739, 'rms_x': 2297}, 332: {'rms_z': -1098, 'rms_y': 1747, 'rms_x': 2244}, 333: {'rms_z': -1114, 'rms_y': 1778, 'rms_x': 2314}, 334: {'rms_z': -1042, 'rms_y': 1841, 'rms_x': 2317}, 335: {'rms_z': -1108, 'rms_y': 1758, 'rms_x': 2288}, 336: {'rms_z': -1107, 'rms_y': 1747, 'rms_x': 2331}, 337: {'rms_z': -1071, 'rms_y': 1829, 'rms_x': 2282}, 338: {'rms_z': -1079, 'rms_y': 1817, 'rms_x': 2329}, 339: {'rms_z': -1161, 'rms_y': 1758, 'rms_x': 2323}, 340: {'rms_z': -1162, 'rms_y': 1768, 'rms_x': 2324}, 'temperature': 2312}
counter NA
sensor_type_id 40
battery_percent 8259.58128078818%
source_address 0013A20041941854
battery 168.9695
nodeId 0
sensor_type_string Vibration Time Series
firmware 6
odr 6
error reported in V2 Mems Buffer
error reported in V2 Mems Buffer
error reported in V2 Mems Buffer
error reported in V2 Mems Buffer
error reported in V2 Mems Buffer
```

We appreciate the ability to read temperature, but it is a piority for us to read acceleration time domain data in order to compute the FRF.