If you’ve ever had a LogTag throw an error message at you, don’t stress. Most issues are easy to sort out once you know what’s going on. Whether you’re downloading data or setting up a logger, here’s a quick guide to common LogTag errors and how to fix them.
Low battery can cause all sorts of weird behaviour. If your logger’s been in use for a while or stored somewhere cold, check the battery status and let it warm up to room temp before trying again.
Here are a few of the usual suspects and how to deal with them:
These errors mean the software can see the logger but can’t talk to it properly. Try this:
Clean the contact pads – use a soft cloth or a pencil eraser to remove any grime or corrosion.
Check the cradle pins – there should be three spring-loaded pins inside. If one’s stuck, gently loosen it.
Use a powered USB hub – unpowered hubs might not give enough juice. Plug directly into your computer or use a powered hub.
Try again – sometimes a second go does the trick.
Switch USB ports – faulty ports can cause connection issues.
Don’t yank the logger too early – wait until the download finishes before removing it.
If your logger’s just come out of a freezer, let it warm up before downloading. Cold batteries can drop voltage and mess with performance.
Not all LogTags are waterproof. If water’s gotten in, the unit might still work for a bit but eventually stop communicating. Check your model’s IP rating and usage guidelines.
Strong electromagnetic fields or radiation can corrupt internal memory. If you suspect this, get in touch with support for help.
Still stuck? Explore more troubleshooting tips in our Support section or get in touch with our team. Keeping your software up to date and your hardware clean goes a long way in keeping things running smoothly.
Why can’t I see the LogTag interface?
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.
