Frequently Asked Questions

This error means that LogTag^® Analyzer cannot find an attached interface or LogTag^® product. In the following example:

• COM1 cannot be used for attaching an interface (most likely this is a modem port or similar)
• COM2 is available for use, but no interface was detected. If you are using an RS232 interface on COM2, but it is not found by the software, the most likely cause is the plug not being inserted correctly.
• A USB interface was found in one of the USB ports, but no logger was detected.

If you only use USB interfaces we recommend you go to “Options" – “Communication Ports" and remove the tick in front of the Communication ports you are not using. This will also speed up your download process as the software no longer uses these ports.

Each time you configure or download a LogTag^® via the menu, all available communication ports are checked for interfaces with LogTag^® products. LogTag Analyzer restricts this search to ports that can physically have an interface attached, and are also enabled in the communication options.

If you cannot see any interfaces in the access screen, and the progress bar stalls at 0% you should check the following:

• All interfaces have been disabled or disconnected: in this case select “Edit – Options – Communication Ports" and enable the interfaces you wish to communicate to. Plug any disconnected USB or RS232 interfaces back into the PC.
• LogTag Analyzer is running twice. If you have accidentally started LogTag Analyzer a second time, the first running instance will prevent the second one from accessing any interfaces. In this case simply close the second copy.
• Communication ports have been enabled that may no longer be present. For example, if a Bluetooth device or a LAN manager device has created virtual COM ports, LogTag Analyzer will still try to communicate to these ports, although they may no longer present. In this case it will take significant time (minutes) for the Operating System to report back that this port is no longer present, and it may seem as if LogTag^® Analyzer “hangs".
• The USB driver is still being installed from Windows Update. By default the Windows Operating System will check the Windows Update repository if a driver for any newly connected device is available, and download it. Depending on your location, connection speed and operating system it can take a long time for this download to proceed. If you want to speed up this process you can click on the “Installing driver" icon in the notification area and select “Skip obtaining device driver software from Windows Update". Use this option only if you already have LogTag Analyzer installed on your PC.
  
  



• There is an issue with the USB driver. You can execute a small utility that will re-install the USB drivers on your computer. This utility can be downloaded from here. You need to make sure you have all USB interfaces disconnected when running the utility. Also, to prevent these drivers from being replaced with a newer version, you need to disable your internet connection when you re-attach the USB interfaces, or disable automatic driver downloading from Windows update.

If the progress bar stops, there is a communication issue between the logger and LogTag^® Analyzer, and LogTag^® Analyzer subsequently retries to get the correct information from the logger. In most cases where the communication is not successful this will be followed by an error message “Internal error $4" or “LogTag failed to respond [20]". Please see Error Messages FAQ section for assistance regarding these error messages.

You should also disable all communication ports currently not in use by selecting “Edit – Options – Communication Ports" and removing the check marks for the unused ports.

If the progress bar stalls, LogTag Analyzer may be trying to communicate with a Bluetooth COM port that has no interface attached. Please disable all unused COM ports. If you exclusively use USB interfaces, you can select “Disable all serial interfaces" from the Edit – Options – Communication Ports dialogue.

This will speed up communication, as LogTag^® Analyzer will not need to check for connected serial interfaces.

At this stage all major computer manufacturers provide USB 3.0 ports mainly to support storage devices such as external hard drives with higher speed requirements. On some computers driver incompatibilities between some of the controlling hardware and the LogTag^® interface drivers could exist, which is unfortunately outside LogTag Recorders control.

Although we have tested LogTag^® Interfaces on USB 3.0 ports of different computer manufacturers without issues we would still advise using USB 2.0 ports where available. There is no advantage of using LogTag^® interfaces on a USB 3.0 port.

USB Device Driver Installation can sometimes fail due to reasons that are outside the control of LogTag Recorders LTD. We would advise to read through the special manual on USB installation published on this website.

Occasionally the drivers de-register themselves, which is an issue of the operating system. In this case, simply unplug the USB interface and plug it back again (for at least 10 seconds), this should resolve the issue.

It is highly unlikely that a USB interface is faulty.

Yes, the drivers have been certified in versions 1.7R14 and later.

Older versions of LogTag^® Analyzer used the unsigned drivers, and we strongly recommend you update your software to the latest version. Functionally both drivers are identical, which is why they will not be automatically installed when you upgrade from a version prior to 1.7R14.

You may still upgrade your drivers to the signed version by selecting the optional hardware upgrade (FTDI USB interface) as part of the Windows^® Update feature. If you wish you can also update the drivers by selecting “Update Driver" through the Windows^® System Device Manager.

Please note this needs to be completed separately for every USB port with an interface connected.

You must have at least Windows^® XP or Windows^® Server 2003 Operating Systems installed for the drivers to be available through Windows^® Update.

When the LogTag^® Analyzer Installer determines that the USB drivers need to be updated while one or more USB interface cradles are connected, it will prompt the user to disconnect them.

You will only need to remove your LogTag^® USB equipment, having other USB devices like Mouse, keyboard or memory sticks connected during this process is OK. Once you have disconnected the USB interface cradles, the ‘Next’ button in the installer will allow you to continue with the installation.

However, if the USB drivers do not successfully unload, because for example the Analyzer software is running, when you click the ‘Next’ button, the installation software will prompt you to disconnect the USB interface cradles again. To force the USB drivers to unload, please follow the manual removal steps described in the next question.

Following steps are required to uninstall USB interface drivers completely:

• With USB interface cradle plugged into the computer, Open “Control Panel" – “System" Select the “Hardware" tab in “System Properties" and select the “Device Manager" button. Scroll to the “Universal Serial Bus controllers" entry, expand the list by clicking on the “+" symbol". Right click any “USB Interface" entries and select the “Uninstall" command from the popup context menu.
• Open “Control Panel" – “Add/Remove Programs", highlight the LogTag ® USB interface drivers and select “remove".
• Delete usbint.inf and usbint.pnf.
• Delete ftdibus.sys from Windows/system32/drivers folder.
• Delete all DLL’s starting with “ftdi" from Windows/system32 folder.

LogTag^® Analyzer versions prior to 1.5 cannot save any annotations directly to a file. This is a result of FDA Chapter 21 CRF Part 11 which prohibits a change to the *.ltd file data once downloaded from the LogTag^®. From version 1.5 onwards annotations are stored in a separate annotation file, which satisfies the FDA requirements. This file allows annotations and Graph titles to be stored and retrieved for viewing later.

LogTag^® products automatically insert error detection codes into the log memory while they record. This assists in detecting corruption and/or manipulation of data. These error detection codes are saved with the file so any attempts to manipulate data in a saved file are also detected.

Non-validated readings occur when a block of readings fails a data integrity check; these readings can be displayed differently on the chart and data list. There are a number of reasons why data can become non-validate:

• A communication error occurs during data transfer from the LogTag^® to the PC.
• Problems occurred during logging where either the readings or the error detection code was not correctly written to memory due to a low battery.
• The LogTag^® was operated in an environment far beyond the production specification (i.e. very cold or very hot or in a heavy industrial environment with high electro-magnetic fields present).

Only in very rare cases is this a result of a memory fault in the LogTag^®.

Some Network Attached Storage Devices (NAS Drives) use versions of SAMBA (Server Message Block) file servers which do not correctly report back whether a file exists or not. Consequently, LogTag^® Analyzer will overwrite an already existing file with the same name, regardless of the settings made in the Automation options. To check if your server displays this behaviour, set the appropriate storage location in the Options dialogue, configure a LogTag^® for 30 seconds logging and download the LogTag^® twice a few minutes apart. The second download should create a file with “….copy 1" attached at the end of the file name.

If you cannot see this additional file in the storage location, you should select a different storage folder to maintain the integrity of your data. It is always good practice to include a field element into the file name that differentiates the file by its date or trip number.

You can use Google’s SMTP server to send automated e-mail through your Gmail account. This requires special settings, which are slightly different than typically found with other ISP’s.

• Enter smtp.gmail.com as the SMTP server.
• The SMTP connection must be made over SSL, so you need to select the SSL check box.
• In the Authentication section select the User name and password check box and enter your Gmail account’s user name (your full email address) and password in the text entry fields.
• In Advanced Settings enter 465 in the Port number field.

Complete the remaining entries in the SMTP section as you would for all other ISP’s.

Downloaded data are stored in a LogTag^® Data file (*.ltd), which is a proprietary secure format that is tamper-proof. This is a requirement in many applications and standards (such as the FDA 21 CFR Part 11 in the US).

*.ltd files can only be accessed and viewed by LogTag^® Analyzer software, so if another person wishes to view the data on different computer then either they need to install LogTag ® Analyzer (which is free for download and use) or the data needs to be exported to another format.

LogTag^® Analyzer stores data in a folder which can be set in the Options, where you can also choose to automatically store data upon downloaded. LogTag^® Analyzer can export data either manually or automatically to formats capable of being imported by other applications such as MS Excel, however, data exported this way are no longer secure/tamper proof.

LogTag^® Analyzer has the option to save *.CSV files, which can be read directly into Microsoft Excel. Please see your MS Excel documentation if you have difficulties with this step. To create a *.CSV file there are three options you can choose from:

• In LogTag^® Analyzer, select “Edit – Options" and select “Export and Reports". Tick the selection box next to “CSV (Comma delimited)" files. From now on anytime you download a LogTag^®, a CSV file will automatically be saved together with the ltd file in the directory chosen in “File and Folder settings". This is usually the “My Documents\My LogTag Data" folder.
• If you wish to export a previously saved file to Excel, open that file, select “File – Save as…", and in the drop down box “Save as type" at the bottom select “CSV (Comma delimited)". The file extension will be automatically be added. You can also select a list separator if you do not wish to use the default Windows separator.
• When you are viewing any data or summary tab simply select “Edit – Copy" and paste it directly into an Excel spreadsheet

“Internal error $4" and “LogTag^® failed to respond [20]" are very general error messages which simply mean that LogTag^® Analyzer found an interface and detected the presence of a LogTag^® product inside the interface, but was unable to establish communication. The letters and numbers after $4 represent type and serial number of the interface. Often this error will disappear by simply repeating the action you were performing when the error occurred, but sometimes it can be a bit more difficult to locate the cause.

Here are some scenarios in which these errors could occur and what to do to rectify the issue:

• There is poor electrical connection between the LogTag^® contact pads and the interface pins; this can happen if the contact pads are dirty or have been exposed to a corrosive environment. Usually this can be corrected by cleaning the contact pads on the LogTag^®. Use a soft, damp cloth. For stubborn stains you can also use a soft pencil eraser.
• There is a “stuck" contact pin inside the interface; look inside the slot, there should be three contact pins visible, they should slide in and out with moderate resistance when force is applied (e.g. with the end of a pencil). Make sure all pins move freely.
• There is not enough power being supplied to the interface (USB); We have seen this error when USB interfaces are used on unpowered USB hubs with other equipment also connected. USB ports have a limited ability to supply power and we would always recommend to connect the USB interfaces directly to the computer or to use a powered hub.
• Communication has been interrupted prematurely; sometimes a user will remove the LogTag^® from the interface too early, which will cause this error to be displayed. In this case simply re-do the action with the LogTag^® connected properly throughout the communication.
• The USB port is defective; Try a different port and see if the error persists.
• The LogTags^® battery is critically low.
• The LogTag^® has just been removed from a cold environment. Lithium cells and in fact all batteries typically exhibit a lower battery voltage in cold conditions, sometimes significantly lower, so downloading units that have come e.g. directly out of a freezer could show communication problems. In that case it may pay to wait until the unit has acclimatised to room temperature or slightly above.
• There was water in the unit; different LogTag^® models have different ingress protection and are not waterproof. If water got inside the unit, it will keep working for a time, but eventually the communication will cease to work.
• The LogTag^® has been subjected to strong EMC fields or radiation, causing a corruption in its internal memory.

The “Internal error $1" message will appear if you try to communicate with a model that is newer than your current version of LogTag^® Analyzer supports. LogTag Recorders LTD continually expand the range of products, adding new models and improved functionality for existing models. When your version of LogTag^® Analyzer reads one of those loggers and cannot interpret the data inside, it will display this error message.

To communicate with this logger please update your LogTag^® Analyzer software. You can either use the “Check Internet for Update…" functionality from the Help menu in LogTag^® Analyzer, or download the updated version from the Download Page. The version available for download will always support all models currently sold by LogTag Recorders LTD.

The following table describes the error code values, their meaning and possible remedies. If problems do persist, please check that you have the latest version of the software available, which can be confirmed through the “Check for updates" command in the “Help" menu.

Starting with version 2.5r19, LogTag^® Analyzer is compatible with Windows 10, however on 64-bit versions the native mail application will not work with the “Send mail" and “Request Help" functions of the LogTag^® Analyzer Application. If you need this functionality you will need to install a 32-bit mail client such as Windows Live Mail 2012, which is available as a free download from Microsoft^®.

You also need to make sure you install LogTag^® Analyzer before you plug in any of the interfaces, as the required drivers are not available from Windows Update yet. If LogTag Analyzer does not recognise your interface cradles, please unplug them and run the USB Interface Cradle Driver Installation utility, which is available from the “All Apps" section of the Start Menu.

Starting with version 2.3r18, LogTag^® Analyzer is compatible with Windows^® 8, however on 64-bit versions the native mail application will not work with the “Send mail" and “Request Help" functions of the LogTag^® Analyzer Application. If you need this functionality you will need to install a 32-bit mail client such as Windows^® Live Mail, which is available for free from Microsoft^®.

Drivers are now available from Windows^® Update.

Yes, LogTag^® Analyzer versions 1.9r12 and later are fully compatible with Windows^® 7 in both the 32-bit and 64-bit versions.

The USB Interface drivers are now available through the Windows^® 7 update feature as well as being installed as part of the software installation. The detection process is faster when installing the drivers from a local disk, so if you install the software before you plug the interface into a USB socket you can skip the Search for drivers on Windows^® Update.

We recommend that any version prior to 1.9r11 be upgraded through the “Help-Check Internet for Update" facility from within LogTag^® Analyzer.

You can use LogTag^® Analyzer versions 2.0r17 and later on an Apple Mac computer, however you must use a virtual machine software such as VMWare Fusion, Parallel Desktop or similar. You can find a summary of the steps in the document about “Installing LogTag^® Analyzer on an Apple Mac", which you can download from here.

Unfortunately at this stage we cannot recommend installation of LogTag^® Analyzer on Linux using WINE. Some users have reported success these instructions, this is however experimental and LogTag Recorders^® can only offer limited support. We will continue to monitor the suitability of WINE for LogTag^® Analyzer and will publish new information as required.

You can use LogTag^® Analyzer versions 2.0r17 and later in a Citrix environment, however there are certain restrictions. You can find a summary of the requirements in the document about “Installing LogTag^® Analyzer in Citrix environments", which you can download from here.

Open “Control Panel" – “Add/Remove Programs", or “Control Panel" – “Programs and Features"; highlight “LogTag^® Analyzer" and select “remove".

If you are removing version 2.3 or higher, you also need to remove the USB drivers: highlight “USB Interface Cradle Drivers" and select “remove"

On some occasions this may not remove every single file from your computer. In that case please delete following files also:

• All LogTagIO*.dll files in #Windows#\System32 folder
• The ‘User profile.dat’ file from C:\Documents and Settings\#USER#\Application Data\LogTag
• In VISTA and Windows 7 this file is located in C:\Users\#USER#\AppData\Roaming\LogTag

This message typically indicates an incomplete download, which invalidates the digital signature of the installer file. In the email you received with the download links you will find a link to a zip file; download that file, extract it and then run the resulting exe file. If the file unzips correctly, the download has succeeded and the software should install correctly.

Exit the LogTag^® Analyzer software and delete the file “User Profile.dat" from C:\Documents and Settings\#USER#\Application Data\LogTag. In VISTA and Windows 7, this file is located in C:\Users\#USER#\AppData\Roaming\LogTag. You may need to change the display settings in Windows Explorer to be able to navigate to this file (Note: The Windows search feature will likely not find this file, however you can quickly navigate to the Roming profile location by typing “%APPDATA% into the Windows Explorer Address Bar). Please refer to the Windows^® Operating System’s online help.

Once this file is deleted, the software menus will be displayed in the language set in the Regional Options of the operating system (if LogTag^® Analyzer software supports this language, otherwise in English). Please note, that other settings you may have made like Communication port settings or default chart parameters will be lost.

This application note explains how to distribute user settings to multiple PC’s, copy user settings from one PC to another and from one user to another on the same PC.

Some Multi-Trip LogTags^® are purchased as single trip loggers and cannot be reconfigured once used. This will be shown by a lock symbol Lock next to the USB interface in the Configure screen. The LogTag^® will need to be returned to your distributor to have the lock removed. There may be a charge for that. Single-Trip Loggers cannot be re-used at any stage.

Logging cannot be manually stopped on the LogTag^® itself. If you want a LogTag^® to stop recording at a specific time, select a specific number of readings or select a specific time period to be covered in the “configure for next use" screen. The LogTag^® will then stop recording data when that point is reached. If you choose “Record Readings Continuously", the oldest recording will be overwritten once the memory of the LogTag^® is full, and the LogTag^® can only be stopped by re-configuring or hibernating it with the LogTag^® Analyzer Software. An exception to this are TRID30-7 and TRED30-7 loggers, which can be stopped with the Start/Stop/Clear button, but this feature must be enabled when the loggers are configured.

Tip: Use the “Inspection Mark" feature to indicate when a load has safely reached its destination. When the “Start-Mark" button is pressed while logging is in progress, an inspection mark is inserted in the recorded data. This enables confirmation that the load has been manually checked at certain times in the journey, and also enables the recipient of the shipment to show when the load arrived at its destination.

You cannot reconfigure different types of LogTag^® with the “Again" button. A warning message such as in this example will be displayed:

If you have many different loggers that require setting with the same or similar configuration parameters we recommend setting up configuration profiles for each type. If you want to configure units with the same configuration as used for the last trip use the quick-reconfigure function. This function is described in more detail in the User Guide.

This function allows the LogTag^® to record temperature data even if the “Start" button is not pressed. When a logger is configured for push button start using LogTag^® Analyzer software the user has to press the “Start" button to initiate data collection. This is usually done when the LogTag^® is placed in the consignment of goods. If, however, the user forgets to press the “Start" button, the logger will still collect data in “pre-start" mode, and this data can be viewed in the normal way using LogTag^® Analyzer.

Pre-Start logging can be enabled or disabled when configuring the logger. Pre-start logs do not count towards the total number of readings configured. In other words, you cannot expand the memory size by utilising pre-start logging. If a LogTag^® is configured to take readings up to its memory capacity and has pre-start enabled, the pre-start readings will no longer be available once the Start button has been pushed AND the LogTag^® has completed its intended full logging cycle. The pre-start readings will be overwritten to ensure the “main" recordings can use the complete memory.

Earlier versions of LogTag^® Analyzer did not support recording from a set date and time. Later versions do, so please upgrade to the latest version and you will be able to select “Date and Time" as a startup option in the configuration screen.

Unfortunately there is no clear cut answer to this question. Battery life is affected by many different factors:

• If the logger is permanently used in very cold temperatures (<20°C for example) battery life is reduced as the battery needs to work considerably harder to deliver the required power.
• If the logger is permanently used in very hot temperatures (>50°C for example) the battery’s internal self-discharge increases as does the average current drawn by the electronics, hence battery life decreases.
• If the download rate is high, battery life decreases.
• If the alert LED blinks often, more power is used and battery life decreases.
• If the logging rate is high, more power is used and the battery life decreases.
• If the logger is hibernated between uses, battery life increases, as the power consumption between trips is kept to a minimum.

It should also be noted that not all battery cells have exactly the same characteristics. Although they are manufactured to stringent quality specifications, some cells have naturally longer life than others due to the processes used in their manufacture.

Each data sheet contains an estimate for typical battery life in normal conditions; this is based on monthly download and 15 minute logging. Clients have reported shorter battery life for applications of frequent downloading (twice a day) with relatively rapid logging (every minute or less), but also well exceeding the specifications, particularly if they are hibernated between uses.

LogTag^® Analyzer displays the current battery condition of a logger during configuration and also after download.

TRIX-8, TREX-8 & HAXO-8 models contain a simple battery diagnostic circuit, which measures the battery voltage and returns ‘OK’ or ‘LOW’. This is just a status and it is not possible to calculate a %remaining battery life from this data. The point at which the battery reports ‘LOW’ is typically when around 15%-20% capacity is left, which in normal operating conditions is equivalent to around 3-4 months of typical use.

SRIC-4, TRIL & SRIL designs contain a battery life monitoring system. These products not only return the actual battery voltage to the software, but also keep track of their activities so LogTag Analyzer can calculate a ‘% battery life remaining’ value, once the battery capacity falls below 50% of its original value. TRID30-7 and TRED30-7 models report high or low based on battery voltage.

An incorrect low battery indication can occur if the logger is still very cold during communication, as it is more difficult for the battery to deliver power at low temperatures due to the chemistry used. The battery condition is therefore more representative when reported at room temperature, around 20°C.

If a LogTag^® reports a battery as ‘OK’ during configuration, there is typically enough operational life left to complete a trip before being completely exhausted. Sometimes such a trip can even last several months, as the battery threshold that triggers a ‘LOW’ reading has enough safety margin built in to allow for the battery to go ‘low’ during the trip. If, however, a product shows ‘LOW’ when being configured or downloaded, it should not be used again, but discarded in accordance with local regulations.

If you continue to use the logger despite a LOW battery warning, there may not be enough power left to correctly record and store data, or to communicate with a PC. Often this leads to data corruption and sometimes complete data loss. For SRIC-4, TRIL & SRIL models the software can calculate the estimated % remaining at the conclusion of a configured logging trip and block configurations that can result in a battery being empty before the trip end.

All LogTag products have non-rechargeable Lithium-Metal type batteries. You must not attempt to recharge these batteries.

Following models have user replaceable batteries:

• TRID30-7R
• TRED30-16R
• UTRID-16

They use a commonly available battery (CR2032); to safeguard your data we recommend you use a reputable, branded battery. Detailed instructions for battery replacement can be downloaded from here.

Following models cannot have their batteries replaced:

• SRIC-4
• SRIL-8, TRIL-8
• TRID30-7F, Vaxtag
• TRED30-7F
• USRIC-4, USRIC-8
• TRIX-8
• TRIX-16
• HAXO-8
• TREL-8
• TREX-8
• UTRIX-16
• TIC20
• TICT
• is0-Tag

LogTag^® data logging products can be calibrated and then adjusted (re-calibrated) with an application called “LogTag^® Calibrate". In this context, calibration is the process of checking a given instrument against a reference with a calibration table of values and errors being generated. Any instrument with a readout can be calibrated. What clients usually want is the ability to “adjust" a LogTag^®. Adjustment (or re-calibration as it is sometimes called) is when an instrument is adjusted to read in accordance with a reference instrument. The readout of the instrument after the adjustment is the same as the reference instrument.

Please discuss any requirements for calibration with your local distributor. All LogTag^® products are designed to operate to the published accuracy over the typical product life, provided they are operated in the rated environment defined in the product specification. Temperature calibration therefore should not be required, unless it is a third party requirement for the application in which the loggers are used. Due to the nature of the RH sensor it is advised that RH calibration is performed every 6-12 months, depending on the environment the logger is subjected to.

LogTag^® logger products that have had their case opened have potentially been exposed to electrostatic effects. In addition, units that had their battery replaced may not have been correctly hibernated or may have suffered from memory corruption if battery voltage was critically low during use. They should therefore be validated for correct operation and performance after the battery change. The preferred way of doing this is by way of re-calibration, where ideally the product should be exposed to its full temperature measuring range.

LogTag Recorders do not operate any return or recycling programme. The cost of recovering components exceeds the cost of replacement by far. Loggers which have reached the end of their working life should be disposed of in accordance with local regulations.

Please contact your local distributor, who may operate a recycling, rental or leasing system.

LogTag^® products are not rated for direct immersion into any liquid. A waterproof enclosure is available for some models. TREX-8, TRED30-7 and TREL-8 models are fitted with an External Sensor. The stainless steel tip of the external sensor is suitable for immersion.

Sorry, external temperature sensors can only be fitted to TREX-8, TRED30-7 and TREL-8 models.

The most common industry standard expression for temperature reading stabilization time is the ‘T90’. This is defined as the typical time taken of a given sensor in a given environment (e.g. moving air, still air, liquid etc.) to register 90% of an immediate step change in temperature.

The T90 of TRIX-8 is typically less than 5 minutes in moving air of 1m/s.

As the thermal step response is basically dependent on the latent heat of the two thermal masses involved (the LogTag^® and the surrounding environment) and the rate of thermal transfer between them, the T90 is the same irrespective of the difference of temperatures though at extremes (water freezing and boiling points for example) the environment does not behave homogeneously thereby changing the rates of thermal conduction and therefore changing the resulting T90 value.

For example: in a situation of a 25°C step change say starting at 10°C and moving to 35°C in moving air of 1m/s, the TRIX-8 will typically register 90% of the step after less than 5 minutes – i.e. 0.9×25 = 22.5 -> 10+22.5 = registering 32.5°C within 5mins.

The T90 for a 15°C step in 1 m/s moving air (say 10°C to 25°C) will be the same. 0.9×15 = 13.5°C +10 = registering 23.5°C within 5mins.

T90 is different in slower moving air or still air, though air is never totally ‘still’ when a temperature difference exists as convection will take place.

LogTags^® can be hibernated via LogTag^® Analyzer by selecting Hibernate from the LogTag menu. When hibernated, all logging functions are suspended, all indicators are turned off and internal components are switched to low power. This reduces the current consumption on LogTags^® to very low levels, equivalent to around 1/10th or less than during normal operation. If units are hibernated between uses, for example when the unit is not required for another trip straight away, the battery life can be significantly extended.

Loggers are automatically ‘woken up’ from hibernation if they are placed in an interface and accessed, and do not automatically return to the hibernate state. The green LED will blink every 8 seconds to indicate its ‘awake’ status, any previously recorded data, however, will no longer be accessible. Note that loggers may wake up from hibernate if static discharges into the contacts of the logger as a result of handling the logger after it has been hibernated.

The LogTags^® LED’s signal a number of different events or status information. The table below contains a summary of the light patterns you may come across during use.

Although we have no test data or specifications for the components used in a LogTag^® it seems generally accepted that CMOS semiconductor components may have marginal performance above 5 kilorads of Gamma radiation dose. Typically most commercial (i.e non rad-hardened) electronics will fail for doses greater than 10-50krad. Depending on the intensity of the radiation the failure could be just a memory corruption, temporary loss of function or permanent damage/loss of function.

Providing metal shielding for the logger (such as a lead container) will lessen the impact of the radiation.

The contacts are isolated from the critical internal component such that incidental static discharge will not harm the LogTag^®. Deliberate application of a full mains voltage (100˜240 volts AC or 12˜24 volts DC) to the LogTag^®, however, will cause permanent damage.

If you simply wish to change the unit used to display reports and graphs in LogTag^® Analyzer, select Edit – Options – General Settings and use the drop down list next to Show temperatures in to select the desired temperature unit.

If on the other hand you wish to change the display units on a LogTag^® model showing temperature on a built in display, you will need to reconfigure the unit using LogTag^® Analyzer; click on the Advanced Options button in the LogTag^® Configure window and select the desired temperature units in the Temperature display unit drop down box.

From time to time LogTag^® Recorders will add new functionality to USB loggers or enhance existing features. When a new version of LogTag^® Analyzer is released, we make these available to you – where possible – via a special upgrade function.

Although you may not always require the new functionality, or may not wish to spend the time necessary during configuration, we still recommend upgrading, as you can be sure you are always working with the most up-to-date product.

About 2 minutes from start to finish.

No, in most cases this is not possible.

This depends highly on the type of upgrade. Typically you can configure and download units even with previous versions, however you may not be able to use all the features. Normally if LogTag^® Analyzer encounters such a unit, you simply get a warning message to upgrade your software. You can do this free of charge via the software download page or the “Check Internet for update" function from LogTag^® Analyzer’s help menu. The release notes for LogTag^® Analyzer will identify any incompatibilities.

If the product is a single use USB logger, which will only generate a PDF at the end of the trip, this will not affect the receiver, and you should always upgrade the products. If, on the other hand, the product is downloaded at the receiving end, you may wish to confirm with the recipient that their internal IT policies will allow them to upgrade the software.

When you click on “Perform Upgrade" in LogTag^® Analyzer, the logger is switched into a state where it can receive upgrade instructions from the Upgrader program. In this state the red LED lights permanently. If you close the Upgrader program or remove the logger before the upgrade process is finished, it cannot be switched back automatically and will remain in this state, until the process is completed. To correct this, do the following:

• Close the LogTag^® Analyzer software, or make sure it is not running.
• Establish the model number of the unit you wish to correct (you can find this on the rear label).
• Plug the unit into a USB socket, wait until the red light is on and the unit is recognised by Windows (enumerated). You should hear a sound and receive a notification window on your screen.
• Start the Upgrader directly by clicking Start – All Programs – LogTag Loggers and then clicking the Product Upgrader for your model.
• The upgrade process will now start from the beginning. Let it finish without removing the unit. The Upgrader will indicate when the product can be removed.
• Close the Upgrader.

You can now start LogTag^® Analyzer again and configure the logger.

Yes, you can upgrade multiple units at the same time, as long as they have the same model number

No problem, do not remove the product and simply let the Upgrader finish the process.

No, you can start the Upgrader directly by clicking Start – All Programs – LogTag Recorders and then clicking the Product Upgrader for your model.

The time zone for a USB Loggers PDF time is set in the advanced dialogue during configuration and cannot be changed once the logger has completed its trip. LogTag^® Analyzer, however, has the ability to display the data using a range of time zones, depending on the settings you make in the Display Time Zone entry in the Date and Time window from the Edit – Options menu.

For example, if you work on the East Coast of the USA and have set the USB Loggers time zone to your local time zone of Eastern Standard Time (UTC -5), you will need to set LogTag^® Analyzer’s Date and Time settings to “Download Time Zone", so all times are reported in your local time. If this entry is set to “Configuration time zone" or “Logger display clock", times in LogTag^® Analyzer will be reported as UTC.