1) Cài đặt cáp USB ?

2) Cài đặt và gỡ bỏ phần mềm LogTag^®?

3) Truyển thông và kết nối máy tính với thiết bị LogTag^®?

4) Cấu hình thiết bị LogTag^®?

5) Sử dụng thiết bị LogTag^®?

6) Tải dữ liệu, xem và lưu lại dữ liệu từ thiết bị LogTag^®?

7) Các dịch vụ cho thiết bị LogTag^®?

8) Báo lỗi thiết bị LogTag^®?

1) USB Installation Issues

Can I use my interface on a USB 3.0 port?

No, unfortunately not. At this stage all major computer manufacturers provide USB 3.0 ports mainly to support storage devices such as external hard drives. There are known driver incompatibilities between some of the controlling hardware and the interface drivers, and our own tests have verified this. Unfortunately this is outside LogTag's control.

Therefore at this stage we cannot support use of the interface on a USB 3.0 port.

As soon as updated drivers become available we will release them through the Windows Update feature.

I am having difficulties communicating to my USB interface.

Driver installation with USB devices can sometimes have problems that are outside the control of LogTag Recorders LTD. 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.

Are the USB interface drivers certified by Microsoft?

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.

The LogTag^® Analyzer Installer asks for all USB devices to be disconnected - what do I do?

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 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 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.

How do I uninstall my LogTag^® Interface cradle USB Interface drivers completely?

Following steps are required to uninstall USB interface drivers completely:

1. 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.
2. Open "Control Panel" - "Add/Remove Programs", highlight the LogTag^® USB interface drivers and select "remove"
3. Delete usbint.inf and usbint.pnf
4. Delete ftdibus.sys from Windows/system32/drivers folder
5. Delete all DLL's starting with "ftdi" from Windows/system32 folder.

2) Software Installation/Uninstallation issues

Can I use LogTag^® Analyzer with Windows 7?

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. Since the detection process is faster when installing the drivers from a local disk we still recommend you install the software before you plug the interface into a USB socket.
We recommend that any version prior to 1.9r11 be upgraded through the "Help-Check Internet for Update" facility from within LogTag^® Analyzer.

Can I use LogTag^® Analyzer with Windows 8?

LogTag^® Analyzer will be compatible with Windows 8 once it is commercially available. You can install version 2.2r20 on Windows 8 at your own risk, but we cannot guarantee full functionality yet. Please be aware the USB Interface drivers are not available through the Windows 8 update feature. If you decide to install LogTag^® Analyzer, you must do so before you plug the interface into a USB socket. If you have specific concerns please e-mail mailto:support@logtagrecorders.com for further details.

Can I use LogTag^® Analyzer on an Apple Mac?

You can useLogTag^® 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".

Can I use LogTag^® Analyzer with Linux?

You can use LogTag^® Analyzer versions 2.0r17 and later on computer running Linux OS, however you must use the translation layer software WINE (see http://www.winehq.org/). You can find a summary of the steps in the document about "Installing LogTag^® Analyzer on Linux".

Can I use LogTag^® Analyzer in a Citrix environment?

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".

How can I uninstall LogTag^® Analyzer completely?

Open "Control Panel" - "Add/Remove Programs", or "Control Panel" - "Programs and Features" highlight the LogTag^® Analyzer 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
• 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

HELP - have accidentally switched to a different language and now I don't know where I am!

Exit theLogTag^® 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). Please refer to the Windows Operating System's online help. Once this file is deleted, upon re-starting 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.

3) LogTag^® Communication Issues

The LogTag^® Access Wizard reports "COM1, COM2, COM3, COM4 not found"
The LogTag^® Access Wizard reports "COM1, COM2, COM3, ... COMXX already in use"
What do I do?

This error means that LogTag^® Analyzer cannot find an attached interface or LogTag^®. 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.

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?

"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. 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 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 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^®'s 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; different 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.

I am getting an error message with a strange code - what does it mean?

Please find a summary of error codes and solutions at LogTag^® Analyzer Error Codes

4) Configuring a LogTag^®

My LogTag^® can not be configured!

Some LogTag^®s 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 Configure screen. The LogTag^® will need to be returned to your distributor to have the lock removed. There may be a charge for that.

I can start a LogTag^® by pressing the start button, how do I stop it logging?

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.

What happens if I press the "Again Button" with a different type of LogTag^®?

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.

What exactly is Pre-Start fail-safe logging?

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 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.

I want to start recording at a specific date and time, but the Software won't let me do that!

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.

5) Using LogTags

Can we use a LogTag^® to measure temperature of liquids?

LogTag^® products are not rated for direct immersion into any liquid. A waterproof enclosure is available for some models. Please visit http://www.logtagrecorders.com/products/pe.htm for more details. 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. Specifications for these product are also available in the product section of the LogTag Recorders LTD web site.

Can we fit an external temperature sensor to a TRIX-8?

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

How fast will TRIX-8 react to a change in temperature?

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.

What is the hibernate feature?

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).Recorders 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 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.

How long does a LogTag's battery last?

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 is at 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.

The published specifications state a 2-3 year estimated battery life in normal conditions, based on monthly download and 15 minute logging. Clients have reported battery life as low as 18 months for applications of frequent downloading (twice a day) with relatively rapid logging (every minute or less). At the other end of the spectrum we have seen TRIX-8 well exceed 3 year battery life, particularly if they are hibernated between uses.

How is battery condition shown and how can this be represented as %remaining?

LogTag^® recorder products incorporate a battery status circuit which measures the battery voltage and returns 'OK' or 'LOW' to LogTag^® Analyzer during configuration and download. 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. Therefore if a unit shows 'OK' duringing configuration there is typically enough operational life left to complete a trip before being completely exhausted. A logger should, however, not be reconfigured and used again once the battery status during configuration is reported 'LOW', as this can result in unexpected behaviour and in a worst-case scenario cause data loss.
Please note that the LogTag^® battery status may sometimes temporarily read LOW if the LogTag^® is downloaded/configured immediately after being removed from a very cold environment due to the characteristics of the battery chemistry. In this case simply wait for the unit to be at room temperature (between 15°C and 30°C) before evaluating the battery status.

In SRIC-4, TRIL-8 and SRIL-8 loggers a new design has been incorporated with a much improved battery life monitoring system. These loggers now communicate the actual battery voltage to the software and keep track of the activity to allow software calculation of a '% battery life remaining' value once the battery capacity falls below 50% of its original value. The software can also calculate the estimated % remaining at the conclusion of a given configured logging trip and block configurations that appear to result in an exhausted battery before the trip end.

What do the different light patterns on the LogTag^® mean?

The LogTag's 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.

6) Downloading, Viewing and Saving Data from a LogTag^®

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?

LogTag^® Analyzer versions prior to 1.5 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^®. From version 1.5 onwards annotations are stored in a separate annotation file, which will satisfy the FDA requirements. This file allows annotations and Graph titles to be stored and retrieved for viewing later.

What causes some of the data points on the charts to be non-validated? What is non-validated data?

LogTag^® products use 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. As new data is written over a block of already existing 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^®.

My older network files get overwritten, but I have the Option "Always create a unique copy of files" enabled.

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.

How is the downloaded data stored and how can this data be accessed if I send it to another person?

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^® 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.

I want to view data in Microsoft Excel - how can I export data?

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, go to "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

7) Servicing LogTag^® products

Can LogTag^® recorders be calibrated?

Let us first start by explaining 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 with a readout can be calibrated. What clients usually want is the ability to "adjust" a LogTag^®. Adjustment (or recalibration 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 LogTag^® products can be adjusted (re-calibrated) 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 product 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 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.

My LogTag^® is reporting an empty battery, can I change it myself?

It is possible to change the battery in some of the LogTag^®products.

Following models have user replaceable batteries:

• TRID30-7R
• TRED30-7R

They come with instructions for battery replacement and use a commonly available battery.

Following models cannot have their batteries replaced:

• SRIC-4
• SRIL-8
• TRIL-8
• TRID30-7F
• TRED30-7F

For the remaining models the battery change process will involve opening the case; it requires some dexterity, soldering equipment and some electronics soldering experience:

• TRIX-8
• TRIX-16
• HAXO-8
• TREL-8
• TREX-8

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.

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 LTD 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:

1. Hibernate the LogTag^® with the LogTag^® Analyzer software
2. Remove the front label, remove the countersunk screws and open the case
3. De-solder the battery from the PCB
4. Replace the foam dot on the battery
5. Solder the new battery in place, watch out for correct polarity
6. Re-assemble the case (reverse process of above dis-assembly)
7. Fit a new front label
8. Test the logger function correctly

LogTag Recorders LTD also strongly recommends a calibration of a logger after the battery has been replaced.

The cost of the replacement components plus the cost of labour and calibration 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.

8) LogTag^® Analyzer 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.