Canon CXDI-60G, Руководство по обслуживанию

Страница: 167 / 186

6. Troubleshooting
3
3. Primary-Level Response
The primary-level response is defined as the work which is carried out at the customer's site
(hospital or clinic). Only medical engineers (ME) and service technicians are permitted to
undertake this work. When service technicians are dispatched to the customer's site, they must
take with them the sensor cables (for the imaging unit side) and a power box (and, if possible,
an imaging unit and notebook PC).
[Troubleshooting when errors have occurred]
3.1 Steps to deal with errors occurring at CXDI software startup
(1) Execute the log gathering tool.
(2) Check the power cable connections.
(3) Check the imaging unit, power box, and blue lamp transmission of the remote switch.
(4) Check the LAN cable connection. (Connection port at FC-24VE/E21A side: LAN2)
(5) Check the LAN cable connection. (Connection port at power box side)
(6) Check the LAN cables used.
· Crossover cable: Connect directly between the control PC and power box.
· Straight cable: Used for the switching hub (for connecting a multiple number of imaging
units).
· Category 5 or above
(7) Re-connect the sensor cable (connections at imaging unit and power box sides).
(8) Check the connection of the sensor cable (connections at power box side).
(9) Replace the sensor cable (at power box side).
(10) Conduct a ping test check (IP: 192.168.100.1*).
(11) Replace the power box.
(12) Replace the sensor cable (at imaging unit side).
The sensor cable (at imaging unit side) must be replaced only by a service technician who has
completed the service training.
Steps (10), (11) and (12) must be performed by the service technician who has been dispatched
to the customer's site.
If the error recurs after the steps outlined above have been taken, the imaging unit must be
returned to the office of the distributor (agent).
The secondary-level response steps are then undertaken.
* When a secondary-level response is requested, the following information must be provided
without fail:
· Details of how the system has been operated on-site (system configuration, optional
software, etc.)
· CXDI software version
· Shock sensor statuses
· Files saved using the log gathering tool
· Frequency with which the problem occurs