|
Signal |
Sequence |
Occurrence |
|
Wake-up signal |
4 alternate flashes of green/red LEDs |
Displayed after configuration has been successfully applied to the Logger. When a Logger is woken from hibernation state. |
|
Start-up signal |
10 alternate flashes of green/red LEDs |
Displayed when the Logger starts its recording cycle. The delay time is re-started (followed by delay signal). |
|
Logging active, no alert present |
Single flash of green LED every 4 seconds |
Indicates the Logger is recording. This is not displayed when pre-start is active and the main logging cycle has not yet started. It is also not displayed when the green LED has been turned off in the configuration screen. |
|
Logging finished, no alert present |
Single flash of green LED every 8 seconds |
Indicates Logger has finished recording. This is not displayed when the green LED has been turned off in the configuration screen. Will also be displayed when unit has been woken up from hibernation. |
|
Logging finished, alert condition present |
Single flash of red LED every 8 seconds |
Indicates the Logger has finished recording and an alert condition was present during the trip. |
|
Logging active, alert condition present |
Single flash of red LED every 4 seconds |
Displayed when the Logger has been detected an alert condition and the Alert LED has been activated. If an alert is present you cannot determine if the unit is still logging or has finished its log cycle. If the Alert LED has not been activated during configuration, in essence the visual indicators have been disabled, and the green LED will flash every 4 or 8 seconds as above. |
|
Stopping (only applies to USB Loggers) |
Sequence of very quick simultaneous flashes of green/red LEDs for 2 seconds |
When this LED sequence starts, the STOP button must be released for the recorder to stop. This Logger can’t be stopped manually, however, it’s possible to use the hibernation mode to stop the recording. |
|
LEDs are not active |
Hibernation reduces the current consumption on Loggers to very low levels. |
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.
