Save log messages from the LogWin tool to a file

Configure the settings for the LogWin tool in order to save its output — that is, the log messages from a project running on a remote computer — to a file. The output is saved continuously as long as the LogWin tool is open and the project is running.

Before you begin, verify the project is running on the remote computer and the project's LogWin task is started.

To configure the settings for the LogWin tool:

1. In the LogWin window, go to Options, and then select Log To File.

   The Log To File dialog box is displayed.

2. Select how you want to save the output.

   Option	Description
   Disable	Saving is disabled. This is the default when you open the LogWin tool.
   Date	The output is saved in dated files, using the name format YYMMDD.log (for example, 150513.log).
   Custom File Name	The output is saved in a single file at a specified location.

3. If you selected Custom File Name, use the File Name box to specify where the file should be saved:

   1. Click the browse button to the right of the File Name box.

      A standard Save As dialog box is displayed.

   2. Locate the folder in which you want to save the file, and then in the File name box, type the custom file name.

   3. Click Save.

      The Save As dialog box is closed, and the file path and name are displayed in the File Name box.

4. Click OK to close the Log To File dialog box.

Assuming the project is running and generating log messages, the LogWin tool immediately starts saving the file(s). If you selected the Date option, the files are saved in the project folder of the project that was most recently opened in the project development environment, regardless of whether that is the project to which the LogWin tool is currently connected. If you selected the Custom File Name option, the file is saved at the specified location.

The saved log files can quickly fill the available storage space, depending on how active the project runtime is and how the log settings are configured, so you should be careful about letting the LogWin tool run for extended periods. This should be for testing and debugging purposes only. If you want to save a more permanent record of runtime behavior or performance, use Alarms, Events, Trends, Reports, and other such features in your project.