USB Installation issues
Software Installation Issues
LogTag Communication Issues
Configuring a LogTag
Using LogTags
Downloading, Viewing and Saving Data from a LogTag
Servicing LogTags
LogTag Analyser Error Messages
USB Installation issues
Q: I am having difficulties communicating to my USB interface.
A: Driver installation with USB devices can sometimes have problems that are outside the control of LogTag Recorders.
We would advise to read through the special manual on USB installation available for download from the LogTag 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.
Q: Are the USB interface drivers certified by Microsoft?
A: Yes, the drivers have been certified in versions 1.7R14 and later.
Older versions of LogTag Analyzer still use the unsigned drivers, and you need to click "Continue Anyway" to complete the installation when asked. 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, Windows® Vista or Windows® Server 2003 Operating Systems installed for the drivers to be available through Windows® Update. Windows 2000 does not have a driver certification process and a driver upgrade through Windows Update is not possible.
Q: The LogTag Analyser Installer asks for all USB devices to be disconnected – what do I do?
A: When the LogTag Analyser 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 here.
Q: How do I uninstall my LogTag Interface cradle USB Interface drivers completely?
A1: For Windows 2000, Windows XP and Windows Vista, 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.
A2: For Windows 98, Windows 98SE and Windows Me, following steps are required to uninstall USB drivers completely:
- With USB interface cradle plugged into the computer, Open "Control Panel" – "System"
Select the "Device Manager" tab in the "System Properties"
- Open "Control Panel" – "Add/Remove Programs", highlight the interface drivers and select "remove"
- Delete the files "usb_ic.inf" from the "Windows/inf/other" folder
- Delete ftdibus.sys from Windows/system32/drivers folder
Back to top
Software Installation/Uninstall issues
Q: How can I uninstall the LogTag Analyser completely?
A: Open "Control Panel" – "Add/Remove Programs", highlight the LogTag Analyser section 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
- userprofile.dat file from C:\Documents and Settings\#USER#\Application Data\LogTag
In VISTA, this file is located in C:\Users\#USER#\AppData\Roaming\LogTag
Q: HELP – I have accidentally switched to a different language and now I don’t know where I am!
A: Exit the LogTag Analyser software and delete the file "userprofile.dat" from C:\Documents and Settings\#USER#\Application Data\LogTag. In VISTA, 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. Please refer to the Windows Operating System’s online help. Once this file is deleted, the software menus will be displayed in English or the same language of the operating system, if LogTag Analyser includes support for that language. Please note, that other settings you may have made like Communication port settings or default chart parameters are also lost.
Back to top
LogTag Communication issues
Q: The LogTag Access Wizard reports "COM1, COM2, COM3, COM4 not found", what do I do?
A: This error means that LogTag Analyser can not find an interface plugged into any of these ports. If you are using an RS232 interface, and it is not found by the software, the most likely cause is the plug not being inserted correctly.
If you use a USB interface, and you do not wish to see this error message all the time, simply 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.
Q: I am getting an error message "Internal error: $4:USB.0012345"
I am getting an error message “LogTag failed to respond [20]” – what do these mean?
A: "Internal error $4" and "LogTag failed to respond [20]" are very general error messages which simply mean that LogTag Analyzer found an interface and a LogTag unit inside the interface, but was unable to establish communication. In other words, a these errors mean there was no reply from the LogTag. 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 contact between the LogTag and the interface contacts; this can happen if the contacts are dirty or have suffered from exposure to a corrosive environment. Usually this can be rectified by cleaning the contacts on the LogTag (a good way is to use a soft pencil eraser.)
- There is a "stuck" contact pin in 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)
- There is not enough power to the interface (USB); We have seen this error when USB interfaces are used on non powered 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 disconnect the LogTag 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 LogTag battery is critically low; This could happen after a long trip, and would be amplified by trying communication if the unit came out of a cold environment. Lithium cells and in fact all batteries do have the habit of exhibiting a lower battery voltage in cold conditions, so downloading units that have come e.g. directly out of a freezer could experience 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; individual LogTag models have different ingress protection and are not waterproof. If there is water ingress the unit will keep working for a time, but eventually the communication will cease to work.
Q: I am getting an error message with a strange code – what does it mean?
A: Please find a summary of error codes and solutions here.
Back to top
Configuring a LogTag
Q: My LogTag can not be configured!
A: Some LogTags are purchased as single trip loggers and can not be reconfigured once used to record a trip. This will be shown by a lock symbol  next to the USB interface in the program screen. The LogTag will need to be returned to your distributor to have the lock removed. There may be a charge for that.
Q: I can start a LogTag by pressing the start button, how do I stop it logging?
A: 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 Analyser Software.
Note that if you wish to indicate when a load has safely reached its destination, you can use the "Inspection Mark" feature instead of stopping the LogTag. 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.
Q: What happens if I press the "Again Button" with a different type of LogTag?
A: You can reconfigure different types of LogTag with the "Again" button, however recommend caution when doing this. LogTag Analyser Software will only set those parameters that are present in both LogTags. If you enter a HAXO after you just configured a TRIX only the temperature parameters will be correctly set.
Q: What exactly is Pre-Start fail-safe logging?
A: This function allows the LogTag to record temperature data even if the "Start" button is not pressed.
Under normal circumstances the logger is configured using Analyser software, then the user presses the "Start" button to initiate data collection. This is usually done when the LogTag is placed in the consignment of goods. However if 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 Analyser.
Please note that Pre-Start logging can be enabled or disabled when configuring the logger. Obviously this function has to be enabled for Pre-Start logging to work.
Pre-start logs do not count towards the total number of readings configured. In other words, you can not 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.
Q: I want to start recording at a specific date and time – but the Software won’t let me do that!
A: 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.
Back to top
Using LogTags
Q: Can we use a LogTag to measure temperature of liquids?
A: LogTags Trix-8 and HAXO-8 are not rated for direct immersion into any liquid without the use of a waterproof bag or casing. We do however have another version of the product, TREX-8, which is fitted with an external sensor. This external sensor is suitable for immersion. Specifications for this product are available on this web site
Q: Can we fit an external temperature sensor to a TRIX-8?
A: Sorry, external temperature sensors can only be fitted to the TREX-8.
Q: How fast will TRIX-8 react to a change in temperature?
A: The most common industry standard expression for temperature reading stabilisation 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.9x25 = 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.9x15 = 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.
Q: What is the hibernate feature?
A: LogTags can be switched to hibernate mode manually in the LogTag menu. When hibernated, all logging functions are suspended, all indicators are turned off and internal components are put into low power consumption mode. This reduces the current consumption on LogTags that support full hibernate to very low levels equivalent to around 1/10th or less current than normal operation. This basically extends the battery life to around the shelf life of the battery (5-10 years). All Humidity LogTags (HAXO-8) support this feature. LogTag Temperature (TRIX-8 & TREX-8) will support this feature from ex-factory units shipped June 2006 onwards. Units manufactured before this date are just put in the lowest possible power state no logging, no indicators blinking).Recorders are automatically ‘woken up’ from hibernate 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 recorders may wake up from hibernate if static discharges into the contacts of the recorder as a result of handling the recorder after it has been hibernated.
Q: How is battery condition shown and how can this be represented as remaining?
A: The LogTag design incorporates a 'battery status' circuit which measures the battery voltage and returns 'OK' or 'LOW' to Analyzer. This is not a physical value, just a status so it is not possible to calculate a %remaining from this data.
However, the point at which the battery starts indicating battery LOW is typically when the battery has around 15%-20% capacity left and therefore still has around 3-4 months of typical use remaining before totally failure.
Q: What do the different light patterns on the LogTags mean?
A: The LogTag's LED's signal a number of different events or status information:
| Signal |
Sequence |
Occurrence |
LogTag wake-up signal |
Sequence of four alternate flashes of green-red LED’s |
- displayed after configuration has been successfully applied to the LogTag.
- when a LogTag is woken up from hibernation state.
Not to be mixed up with...
|
LogTag start-up signal |
Sequence of sixteen alternate flashes of green-red LED’s |
- displayed when the LogTag starts its recording cycle.
|
Mark signal |
Sequence of five simultaneous flashes of green and red LED’s |
- displayed when pressing start/mark button while recording to indicate a mark in the software.
- displayed directly after the start-up signal following a push button start where a recording delay has been configured. In this instance the start-up signal is repeated when the actual recording begins.
|
Logging active, no alert present |
Single flash of green LED every 4 seconds (approx.) |
- indicates unit 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 (approx.) |
- indicates unit 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.
|
Alert condition present |
Single flash of red LED every 4 seconds |
- displayed when the unit has 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. It was deemed more important to ensure an alarm condition is not overlooked, and 8 seconds seemed to long a time to still achieve that
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.
|
Communication |
The green LED will flash occasionally |
- during communication with the interface the green LED will flash occasionally; no information is conveyed in this.
|
Start button press |
red LED glows faintly |
- This is by design but conveys no information.
|
Back to top
Downloading, Viewing and Saving Data from a LogTag
Q: I made annotations to my chart and changed the graph title before I saved it, but now they have disappeared – what did I do wrong?
A: LogTag Analyser version 1.4 can not 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. In version 1.5 and later annotations are be stored in an accompanying file which will therefore satisfy the FDA requirements and allow them to be retrieved for viewing later. You can then also save graph titles.
Q: What causes some of the data points on the charts to be non-validated?
What are non-validated data?
A: LogTag uses a very sophisticated method to automatically insert error detection codes during recordings. 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 are displayed differently on the chart and data list. The most common cause for non-validated readings is when the LogTag has been configured to do continuous recording (i.e. the new recordings 'wrap around' over previous recorded values). As new data is over-written on a block of protected recordings, the data integrity error check for the original block of recordings will indicate an error, thereby technically putting the block of data into doubt.
The same mechanism is also responsible if the logger is not configured for continuous recording, but has been configured for pre-start readings. Once the logger is started by pressing the button, these pre-start readings are retained at the start of the memory, and the logger will overwrite them once the remaining memory is full, regardless of whether configured for continuous reading or not, thereby invalidating the first block of pre-start readings.
Non-validated data may also be displayed if there have been communications issues during data transfer from the LogTag, or if problems occurred during logging where either the readings or the error detection code was not correctly written to memory. This situation may occur if 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).
In very rare cases this could be a result of a memory fault in the LogTag.
Q: How is the downloaded data stored and how can this data be accessed if I send it to another person?
A: Downloaded data are stored in a LogTagData file (*.ltd) which is a proprietary secure format that is tamperproof. 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 application 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 here) or the data needs to be exported to another format.
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 Excel, however, exported data are no longer secure/tamper proof.
Q: I want to view data in Microsoft Excel – how can I export data?
A: LogTag Analyser 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, go to "EDIT" - "OPTIONS" and select "EXPORTS 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.
- When you are viewing any data or summary tab simply select "Edit" – "Copy" and paste it directly into an Excel spreadsheet
Back to top
Servicing LogTags
Q: Can LogTag recorders be calibrated?
A: There is a common misconception about the meaning of certain terminology used in connection with calibration. Calibration is the process of checking a given instrument against a reference with a calibration table of values and errors being generated. Any instrument 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
All LogTags can be re-calibrated (adjusted) with an application called "LogTag Calibrate". Please discuss this requirement with your local distributor.The LogTag is designed to operate to the published accuracy over the typical 2 year life provided it is 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 they 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.
Q: My LogTag is reporting an empty battery, can I change it myself?
A: It is possible to change the LogTag battery, but the process requires some dexterity, soldering equipment and some electronics soldering experience.
PLEASE NOTE THAT ALL NECESSARY SAFETY PRECAUTIONS MUST BE IN PLACE. THESE INCLUDE BUT ARE NOT LIMITED TO PROPER ANTI-STATIC PRECAUTIONS, EYE PROTECTION AND SOLDER FUME EXTRACTION. LOGTAG RECORDERS WILL NEITHER WARRANT NOR ACCEPT LIABILITY FOR ANY DAMAGE OR HARM CAUSED AS A RESULT OF PERFORMING THE FOLLOWING SERVICE OPERATION.
The process is as follows:
- Hibernate the LogTag with the LogTag Analyser software
- Remove front label, remove the countersunk screws and open the case
- De-solder the battery from PCB
- Replace foam dot on battery
- Solder new battery in place, watch out for correct polarity
- Re-assemble case (reverse process of above disassembly)
- Fit new front label
- Test function
You will need a replacement battery and a replacement front label. The battery and label are custom made and must be purchased from LogTag Recorders Ltd or an authorised distributor.
The cost of the replacement components plus the cost of labour to do this job is typically much higher than the cost of a replacement logger. However, if you wish to proceed, you can enquire about the cost of a replacement battery and label with your local distributor.
Back to top
LogTag Analyser Error Codes
The following 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.
| Value |
Definition |
Possible Resolution |
$0 |
Operation completed successfully |
|
$1 |
General failure |
Obtain and install a newer version of the software.
If problem persists please contact support for further assistance. |
$2 |
Unable to communicate – No access to the communication port |
Unplug the interface for at least 10 seconds and then re-plug interface.
Try connecting the interface to a different port socket. |
$3 |
File/disk error while accessing LogTag information within a file. |
Use disk validation and repair tools, like scandisk or chkdsk, to attempt to repair the issue.
Obtain and install a newer version of the software.
If problem persists please contact support for further assistance. |
$4 |
Unable to communicate - No Response from LogTag |
See description above. If unsuccessful, replace or return to distributor |
$5 |
Unable to communicate – Communication Port not responding |
Check that an interface is connected, if not disable the usage of the port in the Options.
Uninstall the port and then restart the computer.
If using a converter, like a USB-RS232 cable, try using a LogTag USB interface cradle. |
$6 |
Memory allocation error |
Software has run out of RAM to operate successfully.
Close some applications that are currently running. Increase the physical amount of RAM in computer. |
$7 |
Invalid parameter in communication |
An internal error. Obtain and install a newer version of the software.
If problem persists please contact support for further assistance. |
$8 |
The hardware and/or operating system of the system accessing the library method does not support the system requirements of the library. |
Check that the system meets minimum requirements of the software. Update IE from Microsoft. |
$9 |
Password required but not supplied |
Software was unable to gain secure access to the LogTag. Obtain and install a newer version of the software.
If problem persists please contact support for further assistance. |
$A |
Data format error – please upgrade software |
Upgrade your software. |
$B |
Unsupported product – please update software |
$C |
Unsupported file – please update software |
$D |
LogTag version error – please update software |
$E |
Communications protocol error – please upgrade software |
$F |
LogTag configuration error – not supported or incorrect |
Obtain and install a newer version of the software.
If problem persists please contact support for further assistance.
This error may require the unit to be returned for repair. |
$10 |
The software failed to perform the operation because the user cancelled the operation before it was completed. |
Try again.
Obtain and install a newer version of the software.
If problem persists please contact support for further assistance. |
$11 |
An internal error has occurred. |
Close all copies of the software and/or restart computer.
Obtain and install a newer version of the software.
If problem persists please contact support for further assistance. |
$12 |
LogTag Trip Usage limit exceeded |
Return to distributor |
$13 |
Unable to communicate – Communication Port unsupported or Modem Port |
Plug the interface cradle into a different communication port on the computer.
Contact your IT support to investigate and resolve hardware conflicts on this communication port. |
$14 |
User Server cannot establish TCP connection |
Check TCP/IP network support is installed and enabled.
Check there is an active network connection, which is able to communicatE/connect to the reset of the network.
Contact your administrator to check TCP/IP connections and settings. |
$15 |
User Server cannot connect to locked user account |
Contact your administrator to grant access to your account. |
$16 |
Internal error code indicating that a component of the software is out of date. |
Obtain and install the latest version of the software. If problem persists please contact your distributor. |
$17 |
The software is unable to successfully connect to the LogTag User Server software. |
Obtain and install the latest version of the software. If problem persists, contact your administrator to update the copy of LogTag User Server. |
Back to top
[FAQ v9 Last updated 29/11/08] |
