The good news is: it’s usually not a sign of a fault, but rather a result of how the logger was handled during setup or download.
Here’s a breakdown of what causes non-validated data points and how to avoid them.
A non-validated data point is a reading that was recorded by the logger but couldn’t be fully verified during download. These points are still shown on the graph, but they’re flagged to let you know they weren’t confirmed through the usual validation process.
In most cases, yes. The readings are still accurate and reflect what the logger recorded — they just haven’t gone through the full validation process. If you’re using the data for internal monitoring, it’s usually fine. However, for regulatory or audit purposes, validated data is preferred.
If you’re seeing non-validated data regularly or have concerns about your logger’s performance, feel free to reach out to us
Latency, when it comes to temperature logging, refers to the delay between a change in temperature and when that change is detected and recorded by the logger. This delay can be due to the sensor’s design, the materials it’s placed in, or the logging interval. While it might sound like a disadvantage, latency can actually serve a useful purpose in certain environments—particularly where short-term temperature spikes are common but not harmful.
For example, in a busy commercial fridge, the temperature may briefly rise every time the door is opened. A logger with high latency won’t immediately react to these short fluctuations, helping to avoid unnecessary alarms or false data indicating a problem when there isn’t one. In these cases, a slight delay in response acts like a filter, focusing attention on real issues—such as prolonged exposure to unsafe temperatures—while ignoring the everyday ups and downs that don’t affect product quality or safety.
Depending on the type of logger you have, connecting your logger to your PC means either:
First Generation LogTags use a separate Reader (sometimes called a dock) for configuration and for downloading recorded data.
The Second Generation loggers only require a USB port or cable. Apart from saving the cost of the Reader, this makes them much better suited for shipping, because the recipient doesn’t need a LogTag Reader to download a report about the shipment’s journey.
