Dialog: Start Logging / Create Log File(s)

<< Click to Display Table of Contents >>

Navigation:  Reference >

Dialog: Start Logging / Create Log File(s)

Menu Tools > logging Start Communication Logging ...


Log file format

The available log formats are plain text (.txt) files or HTML files for web browsers (.htm). Plain text files are a good choice if you expect your log files to become very large. HTML log files are more comfortable to analyze, because they include all the visual formatting of the communication windows (colors, bold characters, italic characters). However, the file will be larger than a plain text file and some browsers may process large HTML files quite slowly. If you have specific requirements on the output format, you can customize the HTML output.


Log file directory and base name

Choose the directory and base file name for the log file(s) here. The actual file path used for the individual log file representations are displayed in the text boxes within the "Log file representation" frame.


Overwrite / append mode

Choose "append new data" if you do not want Docklight to overwrite existing log file(s). Docklight will then insert a "start logging / stop logging" message when opening / closing the log files. This is so that when in 'append mode' it is still possible to see when an individual log file session started or ended.



A separate log file may be created for each data representation (ASCII, HEX, ...). Choose at least one representation. The log files will have a ".txt" or ".htm" file extension. Docklight additionally adds the representation type to the file name to distinguish the different log files. E.g. if the user specifies "Test1" as the base log file name, the plain text ASCII log file will be named "Test1_asc.txt", whereas the plain text HEX log file will be named "Test1_hex.txt".


High speed logging

If you are monitoring a high speed communication link or if you are running Docklight on a slow computer, Docklight may not be able to catch all the transmitted data or may even freeze (no response to any user input). In this case, try disabling the communication window output while logging the data to a file. Docklight will run much faster, since the display formatting uses considerable CPU time.