Specifications

AE/LZB 119 1897 R1A SOFTWARE CONFIGURATION
68
10. To (re)start the display of data messages, click the <Run> button. When running, this button automatically changes
to <Stop>.
11. Use the Options dialog box to change any desired monitor settings such as its window size, enable/disable data
logging, enable/disable various data message filters, etc. Open this dialog box by clicking the <Opts> button.
12. Click the <Hide> button to make the monitor (and thus the Communications Interface program) invisible. In the
invisible state, the monitor is not displayed and it is not visible in the Windows NT Task List, even though it is
active, running, and logging data messages if data logging is enabled.
13. Press <Ctrl><Esc> on the standard PC keyboard to open the Windows NT Task List. Observe the monitor no longer
appears in the list.
14. Close the Task List via its <Cancel> button or an <Esc> keystroke.
15. Using one or more <Alt><Tab> keystrokes, switch to the Dispatch Manager. Toggle the monitor back to the visible
(“shown”) state via menu selection within the Dispatch Manager.
16. Again, press <Ctrl><Esc> on the standard PC keyboard to open the Windows NT Task List. Observe the monitor
appears in the list.
17. Using the Task List, switch to the monitor or another application as required/desired.
6.4.1.2 Monitor Data Logging
As previously stated, data displayed within the monitor may be logged to the hard disk drive. Refer to Table 3-1 for the
exact path to and file name of the log file.
NOTE
Typically, monitor data logging is only required during troubleshooting/diagnostic periods. As the size of the log file
can become excessive during extended console operational periods, logging should be disabled when it is not
required by clearing the Active check box within the monitor’s Options dialog box. Typically, the only exception to
this is when a log file must be generated over an extended period of time for troubleshooting/diagnostic purposes.
By default, monitor data logging is always disabled when the console application starts. To enable/disable monitor data
logging during console operation open the monitor’s Options dialog box and check or clear the Active check box setting. As
stated in the previous note, logging is disabled when this check box cleared (not checked). Whenever logging is enabled any
previous monitor data log file in the same directory is deleted.
In the monitor’s data area, displayed transmit (TX) and displayed receive (RX) data messages may each have a unique
color setting per MAESTRO.INI settings. For example, transmit messages may be configured to display with white text on a
red background and receive messages may be configured to display with white text on a green background. User-friendly
color configurations may be accomplished with Configuration Editor’s Comm Monitor dialog box as described in section
6.2.2.2 of this manual (page 32).
The contents of the monitor data log file may be viewed and/or printed with any text editor. However, if the console
application is running, disable logging before attempting to open this log file with a text editor. Failure to do this will prevent
the text editor from being able to open the log file. In addition, if the log file is open with a text editor and the console is
running and logging is enabled, do not save the log file with the text editor using the same file name.
Since the log file is a straight ASCII text-based file, it cannot store color information. Therefore, the first character
position in each line of the log file is utilized to indicate if the data message is a transmission (from the console) or a reception
(to the console). Transmit messages are indicated by the presence of an asterisk (“*”) in the first character position and
received messages are indicated by the lack of an asterisk.
If time-stamp logging is enabled via the monitor’s Options dialog box, each data message in the log file is preceded by a
minute:second.millisecond time stamp. For example, if time-stamp logging is enabled at exactly 15:47:35.000
(hours:minutes:seconds.milliseconds), the first logged message in the log file may be time-stamped “47:35.789”.
NOTE