Philips IntelliVue Series, Installation And Service Manual

Page: 321 / 522

Troubleshooting
Maintenance, Troubleshooting, and Repair
7-35
Step 1. Access the
!Windows Explorer
from the
Diagnostics
menu in the
Service
window.
Step 2. Select the path c:\stardate\logs .
Step 3. The
SystemInfo.log
will be displayed.
Step 4. Print this file by clicking on Print in the File menu at the top left corner of the
screen.
or
Step 1. Go to c:\stardate\bin and double-click on LogViewer.exe
Step 2. The Log Viewer application opens. Go to File -> Open to select the log files. More
than one log file can be displayed, as shown in Figure 7-9
Export Log
Files
Software errors that are related to the export features (HL7, paging, 12-Lead ECG
Management, Holter, Patient Data Transfer) are logged into
Export Log
text files. The file
can be accessed as follows.
Step 1. Access the !Windows Explorer from the Diagnostics menu in the Service
window.
Step 2. Select the path
c:\stardate\logs
.
Step 3. The Export.log will be displayed.
Step 4. Print this file by clicking on
Print
in the
File
menu at the top left corner of the
screen.
or
Step 1. Go to
c:\stardate\bin
and double-click on LogViewer.exe
Step 2. The Log Viewer application opens. Go to File -> Open to select the log files. More
than one log file can be displayed, as shown in Figure 7-9
Exception
Error Log Files
If the system crashes or “exceptions” occur, the state of the system when it crashed is stored
in special
Exception Error Log files. These files can be useful to the Response Center or
factory personnel for determining the state of the system when the exception or crash
occurred. These files can be accessed as follows.
Step 1. Access the
!Windows Explorer
from the
Diagnostics
menu in the
Service
window.
Step 2. Select the path c:\stardate\logs .
Step 3. Double click on the file drwtsn32.log and this log will be displayed.
Step 4. Print this file by clicking on Print in the File menu at the top left corner of the
screen.
The
drwtsn32.log
file can keep track of exceptions. When the capacity is reached, the
original file is renamed
drwtsn32_old.log
, and the original
drwtsn32.log
file is erased so
that new exceptions can be added.