Part I Service Scenarios
Repair 89
3.1.10 Self-Test
The self-test function is inherent in MX series products and aims to test the connections of hardware
boards and the running status of the system. According to the access permission and test content, there
are three types of tests: production self-test, maintenance self-test and user self-test.
For details about the self-test procedure, see Part I Service Scenarios: 2.3.5 Self-Test. For details about
the description of self-test items, see Part III Appendix: 2 Description of Self-Test Items.
3.1.11 Logs
The log framework of MX mainly includes the following four process logs, respectively corresponding
to four configuration files. See the following table.
Log Name Log Description
Doppler_log_volumerender.properties 3D/4D process record
Doppler_log_backupapp_volumerender.properties 3D/4D background process record
Doppler_log_ backupapp.properties Background Doppler
Doppler_log_properties Doppler log
The following table describes the major logs.
Log Name Log Description Remarks
Crash
Dump information about software
crash
A crash log is generated upon
software crash, including the
assertion information and
dump file.
Dcmlog DICOM log
PenriLog Details about peripherals: multi-
functional monitoring and more
accurate peripheral information
with redundancy information
removed
Appmon.txt Appmon process log. The
Appmon process manages the
Doppler process.
XX_Back_Log Background process log
Xx_Log Operation log recording user
operations, error information, and
alarm information
The corresponding log is
generated after the Doppler
process is started. After the
Doppler process is started
normally, an operation log is
written in response to this
function. Error logs are
recorded upon problems.
To Next Page
Loading...
Need help?
General
