When the temperature logger TAG is logging data, the data can be read out over the NFC interface at any time during the active lifetime of the TAG.
When using a smartphone or other supported NFC device to read out the TAG data, a condition can occurr where the TAG must choose between performing the temperature logging or sending the data to the NFC device. In these rare occasions, the temperature logger TAG will prioritize the communication and send the data to the NFC device. When this happens, the data log will contain one "empty" logging point at the time of NFC interaction. Following data points will be correctly sampled and stored.
The temperature logger TAG uses only 180 ms to perform the temperature measurement and saving the data, so the chance of such an event occurring are very slim, but it can often be found during trials where the users are doing excessive testing, thus reading data from the TAG much more often than in a real life applications.
The table below shows the chance of the issue occurring when the TAG is read at a random time in its logging state.
Chance of issue occurrence
|1 min||3 in 1000 (0.3%)|
|5 min||6 in 10000 (0.06%)|
|10 min||3 in 10000 (0.03%)|
|15 min||2 in 10000 (0.02%)|
|30 min||1 in 10000 (0.01%)|
|1 hour||5 in 100000 (0.005%)|
|5 hours||1 in 100000 (0.001%)|
When the issue does occur, the missing data point is gracefully handled by TAG Portal and no time skew or other consequential errors will be found in the dataset in TAG Portal, exported data or generated reports.
Example of a data log with a missing temperature data point is whown below.