Discovery RF180 Troubleshooting Guide Table - SM - 5793731-1EN - 8

GE Healthcare Discovery RF180
5793731-1EN, Rev. 8 Troubleshooting Guide Table
GE Healthcare
Troubleshooting Guide Table

Discovery RF180
Discovery RF180
Troubleshooting Guide Table
5793731-1EN
Revision 8, November 2022
© 2019 General Electric Company
All rights reserved.
Page 1
This page is blank.
Page 2
Revision History
Original document release created by Mauro Fumagalli on February 2018
Revision Date Reason for change
1 May 2018 Initial Release - Released version

Revised error code list – Errors 02 50 nnnnn
Added reference to manuals PN
2 Apr 2019 Revised / Added « measured value range » where it was not indicated (but necessary for better understanding)
- Released version
Added new error and warning codes
3 May 2019 - Released version
Revised error codes 02 01 ccccc and 02 02 ccccc
4 July 2019 - Released version
Added error code list – Errors 02 08 ccccc
Revised error code 02 20 00012
5 April 2020 General Revision of Appendix 1 .. 4
General Revision
- Released version
Revision of some sentences
Added the manual reference code “5793727-1EN” where it was indicated (only) “service manual”
6 September 2020
- Released version
Added error code 02 04 00075 and related troubleshooting (new sub-case is present following a unit firmware update)
7 February 2022
- Released version
Swapped CN411  CN412 on schematics and instructions.
8 November 2022 Changed CAN Line “High Impedance” minimum value.
- Released version
Manufacturer: GENERAL MEDICAL MERATE S.p.A.

Via Partigiani, 25
24068 Seriate (BG) – Italy
Tel. +39 035 45 25 311
Fax +39 035 29 77 87 / 29 95 37
www.gmmspa.com
Distributor : GE Medical Systems, SCS

283, rue de la Miniére, 78530 Buc, France
The original version of this publication was drafted in English and will be referred to for any controversy
regarding interpretation of the eventual corresponding versions, translated into other languages.
The contents of this publication may not be reproduced in any manner with any electronic or
mechanical means. It cannot be distributed in any manner without written authorization issued by the
manufacturer. The manufacturer reserves the right to modify/update this document without notice.
Page 3
Table of Contents
Troubleshooting guide - Index

Preface page 5
Errors of "Tri-Phase" CPU card Codes 02 04 ccccc page 8

Errors of "SFD" CPU card Codes 02 05 ccccc page 62
Errors of "Collimator" CPU card Codes 02 06 ccccc page 64
Errors of "Main Console" CPU card Codes 02 07 ccccc page 69
Errors of "In-Room (Remote) Console" CPU card Codes 02 08 ccccc page 119
Warning messages of Tilting Table Codes 02 20 ccccc page 170
Errors & Warning related to “Stitching” Codes 02 50 ccccc page 189

Errors & Warning related to “Tomography” Codes 02 52 ccccc page 191
Errors & Warning related to “TomoSynthesis” Codes 02 53 ccccc page 192
Appendix 01 – CAN_GND line problem (“cut” or in “short circuit” to GND) page 193
Appendix 02 – Broken (or not properly terminated) Can line page 207
Appendix 03 – CAN line in short circuit (or not correctly terminated) page 230
Appendix 04 – CAN line insulation (to GND) problem page 247
Appendix 05 – Driver CAN line troubleshooting page 265
Appendix 06 – Brushless Drivers error codes page 284
o Column longitudinal motor driver Codes 02 00 ccccc

o Table Elevation motor driver Codes 02 01 ccccc
o SFD longitudinal motor driver Codes 02 02 ccccc
o Table Top longitudinal motor driver Codes 02 03 ccccc
Page 4
Tilting Table Troubleshooting guide

❖ Preface
WARNING
Some, few, of the actions described in this TSG could cause harm to the operator and/or expose him/her to electrical shock.
Also, some operations require to enter in the “maintenance/service” mode of the unit and, by this, to disable some (unit) safeties.
As by all on the above, any one of the operations listed in this TroubleShooting Guide must be executed by fully trained FSEs.
On the discovery RF180 system, when an error happens, the related message is displayed. The message is composed by a “code” and an explanation
“text”.
The code is composed by three fields, displayed as: “SS-DD-CCCCC”.
SS is the subject (the entity) that generates / reports the error.
SS = 00 ➔ Subject = DLL (reference: 5793730-1EN TSG - Digital)

SS = 01 ➔ Subject = Generator (reference: 5792128-1EN - Generator)
SS = 02 ➔ Subject = Tilting Table
SS = 03 ➔ Subject = Main Controller (reference: 5793730-1EN TSG - Digital)
SS = 04 ➔ Subject = Inside (reference: 5793730-1EN TSG - Digital)
SS = 99 ➔ Subject = “Unknown” (see next page)
DD is the Device (sub part of the above entity) that generates / reports the error.
CCCCC is the error code generated by the above Device.
As because of this is the troubleshooting guide of the table, on the following pages are considered / displayed only the error codes starting by “02”.
As by the description on the above page, on this guide are only considered (taken in analysis) the codes: “02-DD-CCCCC”.
(TSG Index ➔) Page 5

Error Code Error source Notes

SS DD CCCCC
02 00 ccccc Error is generated by (is coming from) "Column longitudinal motor driver”
02 01 ccccc Error is generated by (is coming from) "Table Elevation motor driver"
see appendix 06
02 02 ccccc Error is generated by (is coming from) "SFD longitudinal motor driver"
02 03 ccccc Error is generated by (is coming from) "Table Top longitudinal motor driver"
02 04 ccccc Error is generated by (is coming from) "Tri-phase" (Clisis Main) CPU card Page 8
02 05 ccccc Error is generated by (is coming from) "SFD" (table bucky) CPU card Page 62
02 06 ccccc Error is generated by (is coming from) "Collimator" CPU card Page 64
02 07 ccccc Error is generated by (is coming from) "Main Console" CPU card Page 69
02 08 ccccc Error is generated by (is coming from) "In-Room Console" (Remote Console) CPU card Page 119
02 20 ccccc Warning messages related to the “Tilting table” Page 170
02 50 ccccc Errors & Warnings related to the “Stitching” Page 189
02 52 ccccc Errors & Warnings related to the “Tomography” Page 191
02 53 ccccc Errors & Warnings related to the “TomoSynthesis” Page 192
Special codes (for Unknown Errors, Not codified Errors, and Errors not listed in the actual software release).
Error Code Error source

SS DD CCCCC
99 xx xxxxx Error is generated by an unknown subject / entity (not present in the list).
aa 99 xxxxx Error is generated by a subject / an entity (aa) but the related device is unknown / not present in the list.
aa bb 99999 Error is generated by an identified Device (bb) but the error is unknown / not present in the list.

When (one of) the table’s CPU card detect and error, the corresponding error code is displayed, together with a short “meaning” text message. These
information are also stored in the “Table error log file” to be accessible during the troubleshooting done by a field service engineer (FSE).
It is also important to be aware that, when the system software detects a fault/error, it could act “automatically” on the system to prevent further
“problems”, for example “disabling” power supplies (and so on). The direct consequence of this, is that “it” could detect other, auto-caused, error codes.
As by this, it is important that, during the unit troubleshooting, the FSE it takes care to identify, also by the time stamps, the real fault/error source.
❖ About the tables on the following pages:

o On the first column is stated the error code number as it is displayed, and stored on the system.
o The second column gives a short description of the error meaning (also, this is stored in the error log).
o On the third column it is reported the troubleshooting of the error - The possible error causes are listed as by their decreasing probability.
o On the next (fourth) column could be present additional info(s) about the error or its troubleshooting.
o On the last (fifth) column there are information about the system response / behavior as consequence of the listed error as well as some comments.
❖ Typographic conventions
In order to facilitate the use of this manual, different styles and types were used. the text identified by the following bullets indicates:
• Instructions to be executed, according to the test/measuring/troubleshooting sequence.
➢ Operation to be executed (branch / jump) depending on a measure / a test that it was made (immediately) before.
➔ “hyperlink” (inside the document) to the point/operation indicated in the text.
❖ Notes:
o The listed errors could be generated / displayed during the normal use of the unit (some only at the startup).
o Many of the error listed on the following are not generated (check disabled) while the unit is in maintenance / calibration mode.
o Some of the error listed on the following could be generated only in Debug mode (with a software debug tool connected to the CPU). If a “debug” related
error is displayed in normal or in maintenance mode, the related CPU card is probably defective and must be changed.
o On the following Error analysis, some lines and/or table cell related to particular errors are “grey filled”. This is done intentionally, to indicate
deprecated errors, future/planned errors, or errors related to OPTIONS that are not actually present on the Discovery unit.
o The electrical measurements done during the troubleshooting of the CAN line will be executed using a normal multimeter. By this, the values will be the
ones of "pure" DC resistances. Anyway, to remember us that we are in presence of a communication line, for those measures we will continue to use the
word “impedance” or, “line impedance” (I.E. we will measure the “active” / “real” part of the impedance or, the impedance with zero phase angle).
o For a better document navigation, some hyperlink are provided; Some of those are intuitive, the others are indicated by the symbol ➔
o At the bottom left side of the pages is present a hyperlink that give the possibility to Jump (back) to the “TSG Index” (to the Index page of this manual).

"T" CPU card (Clisis Main Card) related Errors
System
Error code Cause(s) Solution(s) Additional Info(s)
Response
• Check Driver’s CAN line. See appendix 05
• Check Elevation Driver Power supply during “init

phase”. To do this, please to take as reference the unit
drawings (166101, pages 4, 1 and 2).
• Switch OFF the unit.
In case of this error
• Switch On the unit wait till the starting of the “init
the Elevation and
phase” (contactor TRL2 and TRL3 goes “ON”) and, before
Tilting functions are
the error is displayed, measure presence of the 24 V
disabled (and the
Logic Power Supply on CN193 (X1) and of the Main
driver power supply is
Power supply on CN192 (X4).
switched OFF).
❖ In case the contactor TRL2 remains “OFF”, please to This error check it is done at
Elevation driver All the other motions
02 04 00000 check the fuse F13 and / or to verify that there are every “unit power ON”
not initialized. are also limited
no “active” safeties (like other errors or unit in
and/or disabled.
“over-travel” position…) that disables the driver
power. In positive case, troubleshoot these last
To resume the unit
issues.
functionalities is
❖ In case TRL2 goes “ON” but, on the driver, one (or
necessary a FSE
both) power is not present, please to check the
“visit”.
power supply wiring to the driver.
• If all the above test / values are correct, Change the

Elevation driver (see the related Job Card). Please to take
care that, after a drive change, the related motion is to re-
calibrate.

System
Response
• Check Column Longitudinal Driver Power supply

during “init phase”.
To do this, please to take as reference the unit drawings
(166099 page 1 and 166101 pages 1 and 2).
• Switch OFF the unit. In case of this error
• Switch On the unit wait till the starting of the “init the Column and SFD
phase” (contactor TRL2 and TRL3 goes “ON”) and, before scanning functions
the error is displayed, measure presence of the 24 V are disabled (and the
Logic Power Supply on CN353 (X1) and of the Main driver power supply is
Power supply on CN352 (X4). switched OFF).
Column This error check it is done at
❖ In case the contactor TRL3 remains “OFF”, please to All the other motions
02 04 00001 Longitudinal driver every “unit power ON”
check the fuse F12 and / or to verify that there are are also limited
not initialized.
no “active” safeties (like other errors or unit in and/or disabled.
power. In positive case, troubleshoot these last To resume the unit
issues. functionalities is
❖ In case TRL3 goes “ON” but, on the driver, one (or necessary a FSE
both) power is not present, please to check the “visit”.

Column Longitudinal driver (see the related Job Card).
Please to take care that, after a drive change, the related
motion is to re-calibrate.

System
Response
• Check SFD Longitudinal Driver Power supply during

“init phase”.
(166099 page 2 and 166101 pages 1 and 2).
• Switch On the unit wait till the starting of the “init the Column and SFD
phase” (contactor TRL2 and TRL3 goes “ON”) and, before scanning functions
the error is displayed, measure presence of the 24 V are disabled (and the
Logic Power Supply on CN363 (X1) and of the Main driver power supply is
Power supply on CN362 (X4). switched OFF).
SFD Longitudinal This error check it is done at
❖ In case the contactor TRL3 remains “OFF”, please to All the other motions
02 04 00002 driver not every “unit power ON”
check the fuse F12 and / or to verify that there are are also limited
initialized.
no “active” safeties (like other errors or unit in and/or disabled.
both) power is not present, please to check the “visit”.

SFD Longitudinal driver (see the related Job Card). Please
to take care that, after a drive change, the related motion is
to re-calibrate.

System
Response
EEProm CRC Error • Recalibrate (see service manual - code 5793727-1EN)

02 04 00003 Potentiometer data “Tilting motion” In case of this error
section “Elevation motion” the unit functions are
“Column Scanning motion” disabled.
“SFD Scanning motion” This check it is done at every
“Incidence 0°” “unit power ON” To resume the unit
“TBT Lateral motion” functionalities is
EEProm CRC Error necessary a FSE
02 04 00004 Digital trimmer data If, after the above calibration, the error is still present, “visit”.
section change the “T” CPU card. See “Note” on the following.
• Recalibrate (see service manual - code 5793727-1EN)

“Tilting motion”
the unit functions are
“Elevation motion”
disabled.
EEProm CRC Error “Column Scanning motion”
This check it is done at every
02 04 00005 Encoder data “SFD Scanning motion”
“unit power ON” To resume the unit
section “Incidence 0°”
functionalities is
necessary a FSE
If, after the above calibration, the error is still present,
“visit”.
change the “T” CPU card. See “Note” on the following.
Note: About changing the “T” CPU card, see the related Job Card. After changing the “T” CPU card (Clisis Main) it is necessary to load on the card the same
release of software it is already installed on the other CPUs, and to reconfigure & recalibrate its parameters, as described on the unit service manual (code
5793727-1EN).

System
Response
• This is also a warning that is generated if the operator the actual movement
abort (releasing the exposure commands) a Tomography it is automatically
or Stitching sequence during the unit motion. stopped.
Movement
Aborted • Check Drivers CAN line. See appendix 05 This error check it is done If this error code is
02 04 00006
(error and/or “runtime”. not caused by
warning) • Check Driver’s Power supply. operator (see the first
item on “Solution(s)”
If, after the above tests, the error is still present, change column), is necessary
the “T” CPU card. See “Note” on the following. a FSE
troubleshooting.
• Check Driver’s CAN line. See appendix 05 In case of this

warning, the CAN
Wrong driver This error check it is done
• Check Drivers Power supply. message is ignored.
02 04 00007 command “runtime”.
(warning)
If, after the above tests, the error is still present, change It is necessary a FSE
the “T” CPU card. See “Note” on the following. troubleshooting.
5793727-1EN).

System
Response
Node guarding
02 04 00008 Column scanning • Check Driver’s CAN line. See appendix 05
driver timeout In case of this error
• Check Driver (the “faulty one”) Power supply the actual movement
Node guarding This error check it is done it is automatically
02 04 00009 Elevation • Change the Driver (the “faulty one”) “runtime”. stopped.
driver timeout
If, after the above operations, the error is still present, It is necessary a FSE
Node guarding change the “T” CPU card. See “Note” on the following. troubleshooting.
02 04 00010 SFD Scanning
driver timeout

disabled.
02 04 00011 I2c bus error Change the “T” CPU card. See “Note” on the following.
“unit power ON”. To resume the unit
functionalities is
necessary a FSE
“visit”.
5793727-1EN).

System
Response
• Check CAN_GND line. See appendix 01

• Check CAN line impedance. Switch Off the unit and, on
the “T” CPU card, measure the impedance between JP1
and JP2 (without removing the jumpers). The measured
impedance must be about 60 Ohm (+/- 5 Ohm).
❖ In case the measured impedance is about 120 Ohm, the
CAN line is broken or, one of the two line terminators is
not mounted. ( see appendix 02 )
❖ In case the impedance between the pins of SW4 is more In case of this error
than 150 Ohm, the CAN line is broken or, the line is not the actual movement
“Live” CAN properly terminated. ( see appendix 02 ) it is automatically
02 04 00012 message ❖ In case the impedance between the pins of SW4 is less stopped.
Timeout than 55 Ohm, the CAN line is in short circuit or, a CPU
card is defective. ( see appendix 03 ) It is necessary a FSE
• Check CAN line insulation to ground. Switch Off the unit troubleshooting.
and check that the impedance between JP1 (or JP2)
(multimeter positive tip) and GND (metal Frame) is greater This error check it is done
than 1 Megaohm. “runtime”.
➢ In case the impedance to ground is lower of 1 Megaohm,
there is a problem on the cable insulation and/or on CPU
card(s). ( see appendix 04 )
• If all the above test / values are correct, change the “T”
CPU card. See “Note” on the following.
5793727-1EN).

System
Response
Programming
Error • Check Driver (the “faulty one”) Firmware release
02 04 00013
Column scanning
Driver • Check Driver’s CAN line. See appendix 05
the actual movement
Programming • Check Driver (the “faulty one”) Power supply
This err\or check it is done it is automatically
Error
02 04 00014 “runtime”. stopped.
SFD Scanning • Change the Driver (the “faulty one”) - see the related Job
driver Card.
It is necessary a FSE
Programming troubleshooting.
If, after the above operations, the error is still present,
Error change the “T” CPU card. See “Note” on the following.
02 04 00015
Elevation
Driver
• Check “T” CPU card Power supply (+5 V and +/-12V). In case of this error
➢ In case the measured voltages are correct, Change the disabled.
“T” CPU (Clisis
“T” CPU card. See “Note” on the following. This error check it is done Every motion it will be
02 04 00016 Main)
“runtime”. stopped.
reset error
➢ In case the measured voltages are NOT correct, Change
the “Clisis Interface” (see also service manual – code It is necessary a FSE
5793727-1EN). troubleshooting.
5793727-1EN).

System
Response
Column scanning
Encoder  Motion
mismatch error
02 04 00017
(wrong calibration of • Recalibrate (see service manual - code 5793727-1EN )
encoder In case of this error
“Column Scanning motion”
parameters) the unit functions are
“SFD Scanning motion”
This check it is done at every disabled.
“Incidence 0°”
“unit power ON”
SFD Scanning If, after the above operations, the error is still present,
troubleshooting.
Encoder  Motion change the “T” CPU card. See “Note” on the following.
mismatch error
02 04 00018
(wrong calibration of
encoder
parameters)
Elevation • Recalibrate (see service manual - code 5793727-1EN ) In case of this error
Encoder  Motion “Tilting motion” the unit functions are
mismatch error “Elevation motion” This error check it is done at disabled.
02 04 00019
(wrong calibration of every “unit power ON”.
encoder If, after the above operations, the error is still present, It is necessary a FSE
parameters) change the “T” CPU card. See “Note” on the following. troubleshooting.
5793727-1EN).

System
Response
The system “sense” that the contactor is feeding power to

the Tilting Driver is “OFF”.
• Check that the jumpers on SW2 of the “T” CPU card are
set as 1-2 and 3-4.
• Check the status of the contactor TRL2. the Elevation and
(Taking as reference the unit drawing 166101, pages 1, 2 Tilting functions are
and 3). disabled (and the
This error check it is done at
Tilting Driver ➢ In case TRL2 is “ON”, check the voltage on CN104 pin switched OFF).
02 04 00020 every “unit power ON” and
Power “On” Error 9 (of “T” CPU card), taking as GND reference the metal All the other motions
“runtime”.
frame. are also limited
and/or disabled.
➢ If the above voltage is about 0 Volt, change the “T”
CPU card. See “Note” on the following. It is necessary a FSE
➢ If the above voltage is 24 V (or higher), check for troubleshooting.
problems on TRL2 contacts and/or wiring.
➢ In case TRL2 is “OFF”, check the fuse F13 and / or verify

that there are no “active” safeties (like other errors or
unit in “over-travel” position…).
5793727-1EN).

System
Response
the Elevation and
Tilting Driver Tilting functions are
PTILT_BLQ signal disabled (and the
“active” This error check it is done at driver power supply is
As the “PTILT_BLQ” input (CN120, pin14) it was never used
every “unit power ON” and switched OFF).
02 04 00021 (only planned for future use) in case of this error change the
The system “sense” “runtime”. All the other motions
“T” CPU card. See “Note” on the following.
that the feedback are also limited
signal PTILT_BLQ is and/or disabled.
active
troubleshooting.
02 04 00022 Please to see next page
• With the unit “ON” Check the status of the led LD66 on In case of this error
the “T” CPU card. the Elevation and
Tilting Driver Tilting functions are
PTILT_RDY signal ➢ In case LD66 is ON, change the “T” CPU card. See disabled (and the
“OFF” “Note” on the following. This error check it is done at driver power supply is
every “unit power ON” and switched OFF).
02 04 00023
The system “sense” ➢ In case LD66 is OFF, check the connection of CN120 “runtime”. All the other motions
that the feedback and the related wiring till the Tilting Driver (Ref. drawing are also limited
signal PTILT_Ready 166101 page 3). and/or disabled.
is not active If all the above is Ok, change the “T” CPU card. See
“Note” on the following. It is necessary a FSE
troubleshooting.
5793727-1EN).

System
Response
Power ON the unit in Maintenance mode, command the
tilting motion and verify that LD72 (on the “T” CPU card) is
“ON” only during the motion.
• In case the behavior of LD72 it is correct, change the

• In case LD72 is always “ON”, switch Off SW4.
o If the led “goes OFF”, change the Tilting Driver (see the
related Job Card).
Tilting Driver the Elevation and
o If the led “remains ON”, disconnect CN120.
Driver “ON” signal Tilting functions are
➢ In case LD72 “remains ON”, change the “T” CPU
Error disabled (and the
card. See “Note” on the following.
This error check it is done at driver power supply is
➢ In case LD72 “goes OFF”, check the wiring from
There is a every “unit power ON” and switched OFF).
02 04 00022 CN120 and the Tilting Driver (Ref. drawing 166101
mismatch between “runtime”. All the other motions
page 3).
the “run” command are also limited
and the related and/or disabled.
• In case of NO MOTION, check if the Driver is powered
feedback from the
and its display is “ON”.
driver. It is necessary a FSE
o If there is the power but the driver’s display is “OFF”,
troubleshooting.
change the Tilting Driver (see the related Job Card).
o If there is driver’s display is “ON” but nothing changes if
is commanded, check the wiring from CN120 and the
Tilting Driver (Ref. drawing 166101 page 3).
If the wiring is OK, change the Tilting Driver (see the
related Job Card).
Finally, if all the above doesn’t solve the problem,
5793727-1EN).
System
Response
The system “sense” that both the end of travel are activated.
On the “T” CPU card, check the status of LD4, LD69 and LD70.
• In case LD4 is “ON” and both LD69 and LD72 are “OFF”,
check for a wiring problem CN137  CN803  FC37 &
FC38 (Ref. drawing 166101 page 4). In case of this error
Elevation the unit functions are
End of travel • In case LD4 is “ON” and any one of LD69, LD72 is “ON”, This check it is done at every disabled.
02 04 00024
Micro-switches Change the “T” CPU card. See “Note” on the following. “unit power ON”
error It is necessary a FSE
• In case LD4 is “OFF”, disconnect CN137. If LD4 goes troubleshooting.
“ON”, check for a wiring problem CN137  CN803 
FC37 & FC38 (Ref. drawing 166101 page 4).
• In case LD4 is remains “OFF”, disconnect also CN136. If

LD4 goes “ON”, check for a wiring problem CN136 
CN342  FC43 (Ref. drawing 166101 page 3).
5793727-1EN).

System
Response
On the “T” CPU card (Clisis Main), check the status of LD70.
Elevation
“LOW” end of
• In case LD70 is “OFF” and the unit elevation is not on
travel
the “LOW” EOT, check for a wiring problem CN137 
Micro-switch error In case of this error
• In case LD70 is “ON” and the unit elevation is not on
The system “sense” This check it is done at every disabled.
02 04 00025 the Lower position EOT, re-calibrate (see service manual
that the elevation “unit power ON”
- code 5793727-1EN )
“low” EOT is It is necessary a FSE
activated but, this is troubleshooting.
not corresponding
• In case all the above is correct, change the “T” CPU
to the calibration
“lower” position.
On the “T” CPU card (Clisis Main), check the status of LD69.
Elevation
“HIGH” end of
• In case LD69 is “OFF” and the unit elevation is not on
travel
the “HIGH” EOT, check for a wiring problem CN137 
Micro-switch error In case of this error
• In case LD69 is “ON” and the unit elevation is not on
The system “sense” This check it is done at every disabled.
02 04 00026 the Higher position, re-calibrate (see service manual -
that the elevation “unit power ON”
code 5793727-1EN )
“high” EOT is It is necessary a FSE
activated but, this is troubleshooting.
not corresponding
• In case all the above is correct, change the “T” CPU
to the calibration
“lower” position.
5793727-1EN).

System
Response
Power ON the unit in Maintenance mode, command the In case of this error
tilting motion and verify that LD35 on the Clisis Interface the Elevation and
card (Ref. drawing 96244 page 7) is “ON” only during the Tilting functions are
Tilting Brake
motion. disabled (and the
“ON” signal Error
• In case LD35 is always “ON” or, always “OFF”, check This error check it is done switched OFF).
02 04 00027 There is a mismatch
the wiring CN103 ➔ CN101 ➔Tilting motor brake (Ref. “runtime”. All the other motions
between the “On”
drawing 166101 pages 2 and 3) for a short circuit to ground. are also limited
command and the
• In case the above is correct, change the “Clisis and/or disabled.
related feedback
Interface” card” (see service manual - code 5793727-1EN).
If also this doesn’t solve the problem, change the “T” It is necessary a FSE
CPU card. See “Note” on the following. troubleshooting.

Elevation the unit functions are
This error code is an obsolete one
“Minimum This check it is done at every disabled.
02 04 00028
position” “unit power ON”
• In case this error is displayed, change the “T” CPU card.
Dip-switch error It is necessary a FSE
See “Note” on the following.
troubleshooting.
5793727-1EN).

System
Response
• Recalibrate (see service manual - code 5793727-1EN )

“Incidence 0°”
• If the above doesn’t solve the problem, check Column

scanning Potentiometer and related wiring.
In case of potentiometer changing and/or repairing of its
the Column and SFD
connections, recalibrate (see service manual - code
scanning functions
5793727-1EN):
are disabled (and the
Driver axis “SFD Scanning motion”
This check it is done at every switched OFF).
02 04 00029 distance “too big” “Incidence 0°”
“unit power ON” All the other motions
error
are also limited
• If the above doesn’t solve the problem, check SFD
and/or disabled.
Scanning Potentiometer and related wiring.
connections, recalibrate (see service manual - code
troubleshooting.
5793727-1EN):
“Incidence 0°”

5793727-1EN).

System
Response
• Check if other errors related to Column and/or SFD
the Column and SFD
scanning motion are displayed and troubleshoot those
scanning functions
errors.
Driver axis driver power supply is
Column scanning This check it is done at every switched OFF).
02 04 00030
SFD Scanning “unit power ON” All the other motions
• Check the Column Scanning and the SFD Scanning
off-line are also limited
Drivers Power supply
and/or disabled.
troubleshooting.
• Check if other errors related to Column and/or SFD

scanning motion are displayed and troubleshoot those
errors.
All drivers are off- This check it is done at every disabled.
02 04 00031
line. “unit power ON”
• Recalibrate the “T” CPU related parameters as described
on the service manual - code 5793727-1EN .
troubleshooting.
5793727-1EN).

System
Response
The system “sense” that the relay is feeding power to the

TableTop Driver is “OFF”.
• Check the status of the relay RL4.

(Taking as reference the unit drawing 166101, pages 3 and
2).
the Table Top motion
is disabled (and the
➢ In case RL4 is “ON”, check the voltage on CN104 pin 7
(of “T” CPU card), taking as GND reference the metal
This error check it is done at switched OFF).
TableTop Driver frame.
02 04 00032 every “unit power ON” and Other motions are
Power “On” Error
“runtime”. consequently limited
➢ If the above voltage is 24 V (or higher), change the “T”
and/or disabled.
➢ If the above voltage is about 0 V, check for problems
troubleshooting.
on RL4 contacts and/or wiring.
➢ In case RL4 is “OFF”, check the fuse F4 and / or verify

5793727-1EN).

System
Response
The system “sense” that the relay is feeding power to the

FFD Driver is “OFF”.
• Check the status of the relay RL1.

(Taking as reference the unit drawing 166101, page 3).
the Focal Distance
motion is disabled
➢ In case RL1 is “ON”, check the voltage on CN104 pin
(and the driver power
11 (of “T” CPU card), taking as GND reference the metal
This error check it is done at supply is switched
FFD Driver frame.
every “unit power ON” and OFF).
02 04 00033 Power “On” Error
“runtime”. Other motions are
➢ If the above voltage is 24 V (or higher), change the “T”
consequently limited
and/or disabled.
➢ If the above voltage is about 0 V, check for problems
on RL1 contacts and/or wiring.
troubleshooting.
➢ In case RL1 is “OFF”, check the fuse F10 and / or verify
5793727-1EN).

System
Response
The system “sense” that the contactor is feeding power to the

Column scanning and the SFD Scanning drivers is “OFF”.
• Check the status of the contactor TRL3.

(Taking as reference the unit drawing 166101, pages 1 and
the Column and SFD
2).
scanning functions
Column scanning are disabled (and the
➢ In case TRL3 is “ON”, check the voltage on CN104 pin
and This error check it is done at driver power supply is
5 (of “T” CPU card), taking as GND reference the metal
SFD Scanning every “unit power ON” and switched OFF).
02 04 00034 frame.
drivers “runtime”. All the other motions
Power “On” Error are also limited
➢ If the above voltage is 24 V (or higher change the “T”
and/or disabled.
➢ If the above voltage is about 0 Volt, check for
problems on TRL3 contacts and/or wiring.
troubleshooting.
➢ In case TRL3 is “OFF”, check the fuse F12 and / or verify
5793727-1EN).

System
Response
Column scanning
02 04 00035 Driver Firmware
not synchronized
• Check Driver (all the drivers) Firmware release and, in In case of this error
SFD Scanning case, upload it (see the service manual - code 5793727- the related driver /
02 04 00036 Driver Firmware 1EN). This check it is done at every motion is disabled.
not synchronized “unit power ON”
• Change the Driver (the “faulty one”) - see the related Job It is necessary a FSE
Card. troubleshooting.
Elevation
02 04 00037 Driver Firmware
not synchronized
Patient Loading
Sequence This check it is done In case of this error
• Check for errors related to the single drivers (error log)
02 04 00038 Terminated as “runtime”, during the the related motions
and troubleshoot those errors.
consequence of “patient loading sequence” are disabled.
Driver Fault

System
Response
Auto-positioning
Sequence This check it is done In case of this error
• Check for errors related to the single drivers (error log)
02 04 00039 Terminated as “runtime”, during the the related motions
and troubleshoot those errors.
consequence of “Auto-positioning sequence” are disabled.
Driver Fault
The system “sense” that the “X-Ray ON” feedback from the
generator is never goes “ON” during tomography.
• Check the X-Ray generator setup.

• On the Clisis Interface card Disconnect CN170 and make The unit continue to
a jumper between pin 15 and pin 30 of the card work (the exam must
This error check it is done
“X-ray ON” connector. end).
02 04 00040 only during the “tomography”
timeout Check the status of LD65 (Ref. drawing 96244 page 3).
procedure.
➢ If LD65 is “OFF”, change the “Clisis Interface” card” troubleshooting.
(see also service manual - code 5793727-1EN).
➢ If LD65 is “ON”, check the wiring from generator to
CN170 as well as check for generator output signal
problems.

System
Response
This problem could happen only on standard SFD (cassette)
units.
• Check the Table “accessories” configuration.

Considering is selected “Digital Table” tech.
• Check the status of LD59 on the Clisis Interface card

(Ref. drawing 96244 page 3).
o In case LD59 is “ON”, disconnect CN170.
only during the “exposure” In case of this error
➢ If LD59 is still “ON”, change the “Clisis
procedure. the exposure
Interface” card” (see also the service manual -
“Grid not ready” sequence is disabled.
02 04 00041 code 5793727-1EN).
timeout The system “never detects”
➢ If LD59 is now “OFF”, check the wiring from
the Grid oscillation sensor It is necessary a FSE
generator to CN170.
“activation” during exposure troubleshooting.
sequence.
o If LD60 is “OFF”, measure the voltage on pin 16 of
CN164 taking as GND reference the metal frame.
➢ If the voltage is about 0 Volt, change the “Clisis
code 5793727-1EN).
➢ If the voltage is about 24 Volt, check for wiring
problem between generator and CN170 as well
as check for generator output signal problems.

System
Response
This problem could happen only on standard SFD (cassette)
units.

Considering is selected (on the console) “Digital Table”

tech.

o In case LD59 is “ON”, disconnect CN170. In case of this error
only during the “exposure”
➢ If LD59 is still “ON”, change the “Clisis the exposure
procedure.
“ Cassette not Interface” card” (see also the service manual - sequence is disabled.
02 04 00042
ready ” timeout code 5793727-1EN ).
The system is not able to
➢ If LD59 is now “OFF”, check the wiring from It is necessary a FSE
position the Cassette tray
generator to CN170. troubleshooting.
during exposure sequence.
code 5793727-1EN).

System
Response
Generator
This is an old and no more used error code. the exposure
preparation This error check it is done
02 04 00043 In case this error is displayed, change the “T” CPU card. See sequence is disabled.
(software phase) “runtime”.
“Note” on the following. It is necessary a FSE
error
troubleshooting.
The software “disable” unnecessary motion during Tomography. This error check it is done the unit functions are
Motions “not
02 04 00044 In case this error is displayed, change the “T” CPU card. See only during the “tomography” disabled.
blocked” error
“Note” on the following. procedure. It is necessary a FSE
troubleshooting.
• Without command Exposure, Make preparation and

wait till the generator is “ready” than, check the status
of LD64 on the Clisis Interface card (Ref. drawing 96244
Generator “not
page 3).
ready” timeout In case of this error
the exposure
CN164 taking as GND reference the metal frame. This error check it is done
The system “wait” sequence is disabled.
02 04 00045 ➢ If the voltage is about 0 Volt, change the “Clisis only during the “exposure”
for the “Generator
Interface” card” (see also the service manual - procedure.
Ready” feedback It is necessary a FSE
code 5793727-1EN).
signal before to troubleshooting.
command Exposure.
as check for generator output signal and/or
setup problems.
5793727-1EN).

System
Response
This problem could happen only on standard SFD
(cassette) units.
Considering is selected “Digital Table” tech.

“ SFD BUSY ” In case of this error
code 5793727-1EN).
timeout the exposure
➢ If LD59 is now “OFF”, check the wiring from This error check it is done
sequence is disabled.
02 04 00046 generator to CN170. only during the “exposure”
The SFD is not ready
procedure.
for Exposure. It is necessary a FSE
troubleshooting.
code 5793727-1EN).
• Change the “SFD” CPU card. See “Note” on the following.
Note: About changing the “SFD” CPU card, see the related Job Card. After changing the “SFD” CPU card it is necessary to load on the card the same release of
software it is already installed on the other CPUs, to reconfigure its jumpers and to load its default parameters, as described on the unit service manual
(code 5793727-1EN).
System
Response
The system “sense” that the “X-Ray ON” feedback from the
generator is still active after the exposure command it is
set “OFF” (end of tomo angle).

The unit continue to
• Without X-Ray emission, Check the status of LD65 on
work (the exam must
the Clisis Interface card (Ref. drawing 96244 page 3). This error check it is done
end).
02 04 00047 “X-ray OFF” timeout only during the “tomography”
o In case LD65 is “ON”, disconnect CN170. procedure.
troubleshooting.
code 5793727-1EN).
➢ If LD65 is now “OFF”, check the wiring from
generator to CN170.
Collimator busy In case of this error

timeout • Check for collimator mechanical issue (problem on the exposure
shutters / filter motion). sequence is disabled.
02 04 00048 only during the “exposure”
The Collimator is not • Change the “Collimator” CPU card. See “Note” on the
procedure.
ready for Exposure. following. It is necessary a FSE
troubleshooting.
Note: About changing the “Collimator” CPU card, see the related Job Card. After changing the “Collimator” CPU card it is necessary to load on the card the same
release of software it is already installed on the other CPUs, and to reconfigure & recalibrate the Collimator CPU related parameters as described on the
unit service manual (code 5793727-1EN).

System
Response
Alignment error In case of this error

Column scanning As by tomography layer changing the system is not able to the tomography exam
to SFD Scanning adjust the Column  SFD relative positions. This error check it is done is aborted (before
02 04 00049 (timeout). only during the “tomography” exposure).
• Execute the same troubleshooting procedure.
Tomo Layer setting of error 02-04-00029 ➔ It is necessary a FSE
error troubleshooting.

(cassette) units.
the exposure
The system “detects” that the Grid oscillation motion doesn’t This error check it is done
“Grid STOP” sequence is disabled.
02 04 00050 stop after exposure sequence. only during the “exposure”
timeout
procedure.
In case this error is displayed, change the “T” CPU card.
troubleshooting.

the tomography exam
The system is not able to correctly position the Column 
This error check it is done is aborted (before
Tomography “not SFD before tomography (tomography load sequence).
02 04 00051 only during the “tomography” exposure).
ready” timeout
procedure.
• Execute the same troubleshooting
of error 02-04-00029 ➔
troubleshooting.
5793727-1EN).

System
Response

(cassette) units.
the tomography exam
Digital Tomo This error check it is done is aborted (before
The system “wait” for the “Generator Ready” feedback signal
02 04 00052 Generator “not only during “digital exposure).
before to start Tomography.
ready” timeout tomography” procedure.
troubleshooting.
of error 02-04-00045 ➔
The system is not able to correctly terminate the Patient

Loading sequence (motion limits? EOT? Motion safeties? …).
Patient Loading
Sequence • Check for problems that “stops” any one of the motion This check it is done In case of this error
02 04 00053 Terminated as related to the Patient Loading sequence. “runtime”, during the the related motions
consequence of “patient loading sequence” are disabled.
timeout • Check for errors related to the single drivers involved
in the Patient Loading sequence (error log) and
troubleshoot those errors.

System
Response

This check it is done
the operator can’t do
No tech selected by DLL (DLL Tech == “NULL”) “runtime”, and the error could
X-Ray emission exposure.
02 04 00054 be displayed immediately
disabled
Please select (manually) an Accessory or select a correct APR. after a “new Tech” or “new
APR” selection.
troubleshooting.
During the tilting motion, the tilting sensing potentiometer

(the analog voltage related to it) is not changing.
• Check the mechanical coupling of the tilting

potentiometer (service manual - code 5793727-1EN ).
• Recalibrate (see service manual - code 5793727-1EN ) In case of this error
“Tilting motion” the unit functions are
(no changing) Tilting “Elevation motion” This error check it is done disabled.
02 04 00055
potentiometer error • Check all the connection between the potentiometer “runtime”.
(PT1) and the “T” CPU card (connector CN121). To do this, It is necessary a FSE
please to take as reference the page 3 of the drawing code troubleshooting.
166101 (on the service manual - code 5793727-1EN), also
copied on the following page.

5793727-1EN).


System
Response
The “T” CPU has lost the CAN communication to/from the
Column Scanning driver and/or the SFD Scanning driver.
Column and/or SFD • Check Drivers CAN line. See appendix 05
This error check it is done disabled.
02 04 00056 scanning driver
“runtime”.
“CAN link lost” error • Check Driver’s Power supply.
troubleshooting.
If, after the above tests, the error is still present, change
the “T” CPU card. See “Note” on the following.
Table Top Longitudinal driver.
TBT Longitudinal • Check Drivers CAN line. See appendix 05
02 04 00057 driver
“runtime”.
troubleshooting.
5793727-1EN).

System
Response
Table Elevation driver.
Table Elevation • Check Drivers CAN line. See appendix 05
02 04 00058 driver
“runtime”.
troubleshooting.

the unit “consider”
that the value of
The “T” CPU doesn’t receive the CAN message informing about
FFD/SID is the
the value of the FFD/SID. This information is “a must” to avoid
FFD / SID CAN maximum one so,
collisions during Tilting, Elevation, Scanning, Incidence … This error check it is done
02 04 00059 message lost from “limits” the motions
“runtime”.
“T” CPU error according with this
“supposed” value.
of error 02-04-00012 ➔
troubleshooting.
5793727-1EN).

System
Response
• Recalibrate (see the service manual - code 5793727-1EN)

the Column and SFD
“Incidence 0°”
scanning functions
Column scanning • Check Column scanning Potentiometer and related
Encoder  wiring.
Potentiometer In case of potentiometer changing and/or repairing of its
mismatch error connections, recalibrate (service manual - code 5793727-
(wrong value for 1EN):
encoder) “Column Scanning motion”
and/or disabled.
“Incidence 0°”
troubleshooting.
5793727-1EN).

System
Response
• Recalibrate (see service manual - code 5793727-1EN) In case of this error

“Tilting motion” the Elevation and
“Elevation motion” Tilting functions are
disabled (and the
Elevation
• Check Elevation Potentiometer and related wiring. driver power supply is
Encoder 
In case of potentiometer changing and/or repairing of its This error check it is done at switched OFF).
Potentiometer
02 04 00061 connections, recalibrate (service manual - code 5793727- every “unit power ON” and
mismatch error
1EN): “runtime”. Other motions are
(wrong value for
“Tilting motion” consequently limited
encoder)
“Elevation motion” and/or disabled.
change the “T” CPU card. See “Note” on the following. troubleshooting.
5793727-1EN).

System
Response
• Recalibrate (see service manual - code 5793727-1EN )

the Column and SFD
“Incidence 0°”
scanning functions
SFD Scanning • Check SFD Scanning Potentiometer and related
Encoder  wiring.
Potentiometer In case of potentiometer changing and/or repairing of its
mismatch error connections, recalibrate (service manual - code 5793727-
(wrong value for 1EN):
encoder) “Column Scanning motion”
and/or disabled.
“Incidence 0°”
troubleshooting.
5793727-1EN).

System
Response
• Recalibrate (see service manual - code 5793727-1EN) In case of this error

TBT Longitudinal
“TBT Longitudinal motion” the unit functions are
Encoder  Motion This check it is done at every
disabled.
02 04 00063 mismatch error “unit power ON”
(wrong calibration of
change the “T” CPU card. See “Note” on the following. It is necessary a FSE
encoder parameters)
troubleshooting.

At the Power ON the “T” CPU checks some parameters inside
the Column and SFD
the driver. This error informs that the motor encoder resolution
scanning functions
value is not correct.
➢ Check the Firmware release of the Column scanning
Column scanning switched OFF).
Driver and, in case, upload it (see service manual - code This error check it is done at
02 04 00064 Wrong Encoder
5793727-1EN). every “unit power ON”.
Resolution Other motions are
➢ Reload, on the Column scanning Driver, the related
configuration file (see service manual - code 5793727-1EN).
and/or disabled.
Change the Driver (see the related Job Card).
troubleshooting.
5793727-1EN).

System
Response
At the Power ON the “T” CPU checks some parameters inside In case of this error
the driver. This error informs that the motor encoder resolution the Column and SFD
value is not correct. scanning functions
➢ Check the Firmware release of the SFD scanning Driver driver power supply is
SFD scanning and, in case, upload it (see service manual - code switched OFF).
02 04 00065 Wrong Encoder 5793727-1EN).
every “unit power ON”.
Resolution ➢ Reload, on the SFD scanning Driver, the related Other motions are
configuration file (see service manual - code 5793727- consequently limited
1EN). and/or disabled.
Change the Driver (see the related Job Card). troubleshooting.
the driver. This error informs that the motor encoder resolution the Elevation and
value is not correct. Tilting functions are
disabled (and the
➢ Check the Firmware release of the Table Elevation driver power supply is
Table Elevation Driver and, in case, upload it (see service manual - code switched OFF).
02 04 00066 Wrong Encoder 5793727-1EN).
Resolution ➢ Reload, on the Table Elevation Driver, the related Other motions are

System
Response
the driver. This error informs that the motor encoder resolution the TBT Longitudinal
value is not correct. function is disabled
(and the driver power
➢ Check the Firmware release of the TBT Longitudinal supply is switched
TBT Longitudinal Driver and, in case, upload it (see service manual - code OFF).
02 04 00067 Wrong Encoder 5793727-1EN).
Resolution ➢ Reload, on the TBT Longitudinal Driver, the related Other motions are
At the end of (any one) of the stitching positioning, the “T” CPU
checks the positioning error. If this error is too big, the Stitching This is a “not
Column scanning
sequence is aborted and an error code is generated. locking” error.
02 04 00068 Encoder Position
In this situation, the
Error
Recalibrate (see service manual - code 5793727-1EN). Stitching sequence is
“Column Scanning motion” This error check it is done aborted, the error
“SFD Scanning motion” “runtime”, during Stitching code is generated, but
“Incidence 0°” Sequence. no motions are set
“Off”.
SFD scanning
❖ In case of error 02-04-00068 (Column), execute the The operator could
02 04 00069 Encoder Position
troubleshooting of error 02-04-00064. ➔ (re-try to) start a new
Error
❖ In case of error 02-04-00069 (SFD), execute the Stitching sequence.
troubleshooting of error 02-04-00065. ➔

System
Response
At the power ON, the system “sense” that the input

“In-room Fluoroscopy” on the Clisis Interface card is
active.
• Check that the “in-room” Fluoroscopy foot-pedal is not

pressed / activated. In case of this error
the “ in-room ” X-Ray
• On the Clisis Interface card Check the status of LD12. commands are
disabled.
External (in-room)
“fluoro” This error check it is done at
02 04 00070 ➢ If LD12 is still “ON”, change the “Clisis If the problem is not
input active every “unit power ON”
Interface” card” (see also service manual - code caused by an
at Power ON
5793727-1EN). unintentionally
➢ If LD12 is now “OFF”, check the “in-room” “pressed” foot-pedal,
Fluoroscopy footpedal and its wiring to CN174. it is necessary a FSE
troubleshooting.
o In case LD12 is “OFF”, change the “Clisis Interface”
card” (see also service manual - code 5793727-1EN).
• If all on the above don’t solve the problem, change the

5793727-1EN).

System
Response

“In-room Preparation” on the Clisis Interface card is
active.
• Check that the “in-room” Preparation foot-pedal / hand-

switch is not pressed / activated. In case of this error
the “in-room” X-Ray
• On the Clisis Interface card Check the status of LD14. commands are
disabled.
External (in – room) o In case LD14 is “ON”, disconnect CN174.
“Preparation” ➢ If LD14 is still “ON”, change the “Clisis This error check it is done at If the problem is not
02 04 00071
input active Interface” card” (see also service manual - code every “unit power ON” caused by an
at Power ON 5793727-1EN). unintentionally
➢ If LD14 is now “OFF”, check the “in-room” “pressed” foot-
Preparation pushbutton and it’s wiring to pedal/hand-switch, it
CN174. is necessary a FSE
troubleshooting.
o In case LD12 is “OFF”, change the “Clisis Interface”
card” (see also service manual - code 5793727-1EN).

5793727-1EN).

System
Response
“In-room Exposure” on the Clisis Interface card is active.
• Check that the “in-room” Exposure foot-pedal / hand- In case of this error
switch is not pressed / activated. the “in-room” X-Ray
commands are
• On the Clisis Interface card Check the status of LD13. disabled.
External (in – room) o In case LD13 is “ON”, disconnect CN174.
“Exposure” ➢ If LD13 is still “ON”, change the “Clisis This error check it is done at If the problem is not
02 04 00072
input active Interface” card” (see also service manual - code every “unit power ON” caused by an
at Power ON 5793727-1EN). unintentionally
➢ If LD13 is now “OFF”, check the “in-room” “pressed” foot-
Exposure pushbutton and it’s wiring to CN174. pedal/hand-switch, it
o In case LD13 is “OFF”, change the “Clisis Interface” is necessary a FSE
card” (see also service manual - code 5793727-1EN). troubleshooting.


• Check Driver Firmware release and, in case, upload it the related driver /
TBT Longitudinal
(see service manual - code 5793727-1EN). This check it is done at every motion is disabled.
02 04 00073 Driver Firmware not
“unit power ON”
synchronized
• Change the Driver (see the related Job Card). It is necessary a FSE
troubleshooting.
5793727-1EN).

System
Response
• Check TBT Longitudinal Driver Power supply during

“init phase”.
(166101 page 2 and 166099 page 3).
• Switch On the unit wait till the starting of the “init the TBT Longitudinal
phase” (contactor TRL2 and TRL3 goes “ON”) and, functions are disabled
before the error is displayed, measure presence of the (and the driver power
24 V Logic Power Supply on CN373 (X1) and of the supply is switched
Main Power supply on CN372 (X4). OFF).
TBT Longitudinal This error check it is done at
❖ In case the contactor TRL3 remains “OFF”, please to Other motions will be
02 04 00074 driver not every “unit power ON”
check the fuse F12 and / or to verify that there also limited and/or
initialized.
are no “active” safeties (like other errors or unit in disabled.
both) power is not present, please to check the troubleshooting.

TBT Longitudinal driver (see the related Job Card).
Please to take care that after a drive change, the related
motion is to re-calibrate.

System
Response
• Check TBT Long Driver Power supply
• On the TBT Long driver, locate the “driver label”.
ONLY IN CASE the “Model No” Doesn’t include the string

“NCCC”, Reload the TBT Long Driver Firmware and its
Configurations. About this operation, please to see the
service manual – code 5793727-1EN – Chapter: “Firmware
Upgrade” “AKD Kollmorgen drivers Firmware Update”

the actual movement
Programming Error This error check it is done it is automatically
02 04 00075 TBT Longitudinal “runtime” as well as at the stopped.
Driver “unit Power ON”.
troubleshooting.
• Re-calibrate completely the TBT Long motion
About this operation, please to see the service manual - code
5793727-1EN – Chapter: “Adjustments”
“Movements Calibrations”.
• If all the above tests are correct, Change the TBT

Longitudinal driver (See the related Job Card).
Please to take care that after a drive change, the related motion
is to re-calibrate.

System
Response
• Check Driver’s CAN line. See appendix 05 the TBT Longitudinal
functions are disabled
• If the above test is correct, Change the TBT (and the driver is
Longitudinal driver switched OFF).
(See the related Job Card).
TBT Longitudinal This check it is done at every Other motions will be
02 04 00076 Please to take care that after a drive change, the related motion
driver “timeout” “unit Power ON” also limited and/or
is to re-calibrate.
disabled.
To resume the unit
• If, after all the above operations, the error is still
functionalities is
present, change the “T” CPU card.
See “Note” on the following. necessary a FSE
troubleshooting.

• Check Driver Power supply the actual movement
Node guarding This error check it is done it is automatically
02 04 00077 TBT Longitudinal • Change the Driver (see the related Job Card). “runtime”. stopped.
driver timeout
• If, after all the above operations, the error is still It is necessary a FSE
present, change the “T” CPU card. troubleshooting.
5793727-1EN).

System
Response
This is a “not
locking” error.
At the end of (any one) of the stitching positioning, the “T” CPU
In this situation, the
checks the positioning error. If this error is too big, the Stitching
Stitching sequence is
sequence is aborted and an error code is generated.
TBT Longitudinal This error check it is done aborted, the error
02 04 00078 Encoder Position “runtime”, during Stitching code is generated, but
• Recalibrate (see service manual - code 5793727-1EN)
Error Sequence. no motions are set
“TBT Longitudinal”
“Off”.
The operator could
Execute the troubleshooting of error 02-04-00067. ➔
(re-try to) start a new
Stitching sequence.

The system “sense” that the motions drivers are on the
Driver configuration unit are not the AKD ones. This error check it is done at
02 04 00080 disabled.
is not supported. every “unit power ON”
Note that table firmware ≥ 7.x support only AKD drivers.
troubleshooting.
5793727-1EN).

System
Response
the Column and SFD
• Check Driver’s CAN line. See appendix 05 scanning functions
• Change the Driver (the “faulty one”) - see the related Job driver power supply is
Column scanning
Card. This check it is done at every switched OFF).
02 04 00081 driver cannot enter
homing mode
If, after the above operations, the error is still present, are also limited
change the “T” CPU card. See “Note” on the following. and/or disabled.
troubleshooting.
the Column and SFD
scanning functions
• Change the Driver (the “faulty one”) - see the related Job
SFD Scanning switched OFF).
Card. This check it is done at every
02 04 00082 driver cannot enter All the other motions
“unit power ON”
homing mode are also limited
and/or disabled.
troubleshooting.
5793727-1EN).

System
Response
the Elevation and
• Check Driver’s CAN line. See appendix 05 disabled (and the
Elevation
• Change the Driver (see the related Job Card). This check it is done at every switched OFF).
“unit power ON” Other motions are
homing mode
If, after the above operations, the error is still present, consequently limited
troubleshooting.

Column scanning the Column and SFD
02 04 00084 driver cannot set • Check Driver’s CAN line. See appendix 05 scanning functions
reference point are disabled (and the
• Change the Driver (the “faulty one”) – see the related Job driver power supply is
SFD Scanning change the “T” CPU card. See “Note” on the following. and/or disabled.
02 04 00085 driver cannot set
reference point It is necessary a FSE
troubleshooting.
5793727-1EN).

System
Response
the Elevation and
Elevation
02 04 00086 driver cannot set
reference point
troubleshooting.

Column scanning the Column and SFD
02 04 00087 driver cannot enter • Check Driver’s CAN line. See appendix 05 scanning functions
in operative mode are disabled (and the
in operative mode It is necessary a FSE
troubleshooting.
5793727-1EN).

System
Response
the Elevation and
Elevation
in operative mode
troubleshooting.
This function it is needed to change the driver behavior from the Column and SFD
“sync with Column” or “Free” (Stitching mode). scanning functions
SFD Scanning are disabled (and the
driver cannot • Check Driver’s CAN line. See appendix 05 driver power supply is
change This check it is done at every switched OFF).
02 04 00090
“Gear Profile • Change the Driver (see the related Job Card). “unit power ON” All the other motions
modes” are also limited
(Digital #1 output) If, after the above operations, the error is still present, and/or disabled.
troubleshooting.
5793727-1EN).

System
Response
the Column and SFD
This function it is needed to change the driver behavior from
scanning functions
“sync with Column” or “Free” (Stitching mode).
SFD Scanning are disabled (and the
driver cannot driver power supply is
execute This check it is done at every switched OFF).
02 04 00091
“Gear Profile “unit power ON” All the other motions
• Change the Driver (see the related Job Card).
modes” are also limited
internal script and/or disabled.
troubleshooting.

the Column and SFD
Column scanning • Check Driver’s CAN line. See appendix 05 scanning functions
02 04 00092
driver “timeout” are disabled (and the
02 04 00093
driver “timeout”
troubleshooting.
5793727-1EN).

System
Response
the Elevation and
Tilting motions are
Elevation
02 04 00094 driver “timeout”
troubleshooting.
• Check Column scanning Potentiometer and related wiring. the Column and SFD
Column scanning In case of potentiometer changing and/or repairing of its
scanning driver power
“it moves”, but the connections, recalibrate (see service manual - code 5793727-
1EN): supply is switched
driver is disabled.
“Column Scanning motion” OFF ➔ Motor Brake
“SFD Scanning motion” This check it is done at every stops the motion).
02 04 00095 The system sense
“Incidence 0°” “unit power ON” All the other motions
that the
are also limited
potentiometer is
• If, after the above operations, the error is still and/or disabled.
changing without
any motion present, Change the Driver (see the related Job Card).
command.
• Change the “T” CPU card. See “Note” on the following. troubleshooting.
• As Last, Change the “motor”
5793727-1EN).

System
Response
• Check SFD scanning Potentiometer and related wiring.

the Column and SFD
SFD Scanning connections, recalibrate (see service manual - code
scanning driver power
“move” also 5793727-1EN):
supply is switched
with driver disabled
OFF ➔ Motor Brake
This check it is done at every stops the motion).
02 04 00096 The system sense “SFD Scanning motion”
that the “Incidence 0°”
are also limited
potentiometer is
and/or disabled.
changing without • If, after the above operations, the error is still
any motion present, Change the Driver (see the related Job Card).
command.
troubleshooting.
• Change the “T” CPU card. See “Note” on the following.
5793727-1EN).

System
Response
• Check Elevation Potentiometer and related wiring. In case of this error

In case of potentiometer changing and/or repairing of its the Elevation and
Elevation
connections, recalibrate (see service manual - code Tilting driver power
“move” also
5793727-1EN): supply is switched
with driver disabled
OFF➔ Motor Brake
“Tilting motion” This check it is done at every stops the motion).
02 04 00097 The system sense
“Elevation motion” “unit power ON” Other motions are
that the
potentiometer is
• If, after the above operations, the error is still and/or disabled.
changing without
present, Change the Driver (see the related Job Card).
any motion
command.
• Change the “T” CPU card. See “Note” on the following. troubleshooting.
5793727-1EN).

"S" CPU card (SFD CPU Card) related Errors
System
Response

Reset CPU from disabled.
02 05 00000 spot film device If a motion (any one) it
board • Check Grounding connection (cable) of the SFD assembly. was running, that
motion is stopped.
• Measure the Power supply on CN401 of the SFD CPU
card (drawing code 96241). Positive on pin 2, negative on In case of salutary
pin 3. fault, to resume the
“runtime”
➢ If the above Voltages is less than 27 Volt DC (not unit functionality it is
regulated), check for mains problem and/or power sufficient a power
connection of the SFD. cycle.
In case the fault is
Watch Dog Timeout • Change the “SFD” CPU card. See “Note” on the following. permanent, to resume
02 05 00002 on the spot film the unit
device CPU functionalities is
necessary a FSE
“visit”.
02 05 00001 Please to see next page
(code 5793727-1EN).

System
Response
disabled.
Only for
troubleshooting
• If a pushbutton it was unintentionally pressed during purposes, this check
the Power ON sequence, please recycle the power. could be disabled by
Push button the FSE by acting on
“active” the Console CPU dip-
• Replace SFD Keyboard, Keyboard Adapter card and This error check it is done at
02 05 00001 on SFD switch setting (see the
Keyboard Cable (all it is connected at CN414 every “unit power ON”.
during start – up service manual - code
forward). 5793727-1EN).
sequence.
Please to take care
• Change the “SFD” CPU card. See “Note” on the following. that the above
operation is a safety
bypass and, it is
responsibility of the
FSE to re-enable this
safety before to
leave the site.
• Reconfigure SFD CPU card and, load its default parameters
Spot film device (see service manual - code 5793727-1EN). In case of this error
02 05 00003 serial eeprom the unit functions
CRC error • If the problem is still present, Change the “SFD” CPU are disabled.
(code 5793727-1EN).

"Collimator" CPU card (generated) Errors (TSG Index ➔)
System
Response
At Power ON the Collimator CPU is not able to initialize the
“X axis” (patient lateral).
In Maintenance mode: In case of this error,

the “X-axis” motion is
X axis • Check the X-axis for a mechanical problem. This error check it is done at disabled.
02 06 00000
shutter error (Reference, drawing 166097) every “unit power ON”
• Check the X-axis optical switch End of travel (FC X) It is necessary a FSE
and it wiring till CN2. troubleshooting.
• Check the X-axis motor (MX) and it wiring till CN1.
• If all the above tests are correct, change the
Collimator CPU card. See “Note” on the following.
“Y axis” (patient longitudinal).
In Maintenance mode: In case of this error,

the “Y-axis” motion is
Y axis • Check the Y-axis for a mechanical problem. This error check it is done at disabled.
02 06 00001
shutter error (Reference, drawing 166097) every “unit power ON”
• Check the Y-axis optical switch End of travel (FC Y) It is necessary a FSE
and it wiring till CN10. troubleshooting.
• Check the Y-axis motor (MY) and it wiring till CN9.

System
Response

“I axis” (Collimator Iris).
In Maintenance mode:
In case of this error,
the “I-axis” motion is
• Check the I-axis for a mechanical problem.
Iris This error check it is done at disabled.
02 06 00002 (Reference, drawing 166097)
shutter error every “unit power ON”
• Check the I-axis optical switch End of travel (FC I) and
it wiring till CN11.
troubleshooting.
• Check the I-axis motor (MI) and it wiring till CN12.


• Reconfigure and Recalibrate the Collimator CPU (see
the collimator is set
Collimator service manual - code 5793727-1EN ).
This error check it is done at “Offline”.
02 06 00003 serial eeprom
CRC error • If the problem is not solved, change the Collimator
troubleshooting.

System
Response
• Check Grounding connection (cable) of the Collimator.

Reset CPU from
02 06 00004
Collimator board. • Measure the Power supply on CN16 of the Collimator
CPU card.
This check it is done the collimator is set
➢ If the above Voltage is less than 27 Volt DC (not
“runtime” “Offline”.
regulated), check for mains problem and/or power
connection of the Collimator.
Watch Dog Timeout It is necessary a FSE
02 06 00005 on the Collimator troubleshooting.
• If the problem is not solved, change the Collimator
CPU. CPU card. See “Note” on the following.

The software it check that, at the power ON the touch-
Touch-panel Active the touch-panel is
panel is not active / touched.
(Keyboard active) This error check it is done at disabled.
02 06 00006
at collimator start- every “unit power ON”.
In case of this error change the complete Collimator CPU
up It is necessary a FSE
troubleshooting.

System
Response
The Collimator CPU is not able to correctly positioning the

motorized filter #1.
Mainly, it tries to “run” the motor, but the filter (mechanical)
does not reach the End of travel position (optical switch).
This is a “motion timeout” error.
• Check the filter #1 assembly for a mechanical the collimator is set
Motorized filter #1 problem. “Offline”.
02 06 00007 “runtime”, at every position
positioning error
changing of the filter #1
> Taking as reference the drawing code 166097 < It is necessary a FSE
• Check the Filter #1 End of travel “IN” optical switches troubleshooting.
(FC_FL1_IN) and its wiring till CN5.
• Check the Filter #1 End of travel “OUT” optical
switches (FC_FL1_OUT) and its wiring till CN4.
• Check the Filter #1 motor (DC2) and it wiring till CN6.
If all the above tests are correct, change the Collimator


System
Response
The Collimator CPU is not able to correctly positioning the

motorized filter #2.
Mainly it tries to “run” the motor, but the filter (mechanical)
does not reach the End of travel position (optical switch).
This is a “motion timeout” error.
• Check the filter #2 assembly for a mechanical the collimator is set
Motorized filter #2 problem. “Offline”.
02 06 00008 “runtime”, at every position
positioning error
changing of the filter #2
> Taking as reference the drawing code 166097 < It is necessary a FSE
• Check the Filter #2 End of travel “IN” optical switches troubleshooting.
(FC_FL2_IN) and its wiring till CN8.
• Check the Filter #2 End of travel “OUT” optical
switches (FC_FL2_OUT) and its wiring till CN7.
• Check the Filter #2 motor (DC1) and it wiring till CN3.
If all the above tests are correct, change the Collimator


"Main Console" CPU card (generated) Errors

System
Response
• Recalibrate the “zero” offset of the joysticks (see service

manual - code 5793727-1EN).
• Replace “Console Control card” and/or the related
“ARM CPU module”.
Calibration disabled.
After this operation, it is necessary to reconfigure &
parameters This check it is done at every
02 07 00000 recalibrate the Console related parameters (see service
(memory) CRC error “unit power ON” To resume the unit
(Joystick data section) functionalities is
If the ARM CPU module it was also changed, before the
necessary a FSE
above recalibration, it is necessary to load on it the same
“visit”.
release of firmware it is already installed on the other CPUs
(see service manual - code 5793727-1EN).
• Reconfigure & recalibrate the Console related parameter

• Replace “Console Control card” and/or the related
“ARM CPU module”.
disabled.
Configuration After this operation, it is necessary to reconfigure &
02 07 00001 parameters recalibrate the Console related parameters (see service
“unit power ON” To resume the unit
(memory) CRC error manual - code 5793727-1EN).
functionalities is
necessary a FSE
“visit”.

In relation to the measuring points mentioned on the troubleshooting of the following 15 error codes,
please to see the following (Console Control/Interface card) component layout.
̴ ̴ ̴
(Errors 02 07 00010 02 07 00015, 02 07 00020 02 07 00025, 02 07 00034 02 07 00036).

The following drawing it reports the signals / connections of the three analog joystick.
(connectors CN1039, CN1040 and CN1041)
Joystick connector - model: JST PDHR-16VS (16 pin 2.0mm pitch, double-Row)
Pin #1
● to not use / connect ● ● ● ● to not use / connect (+24 VDC)●
● to not use / connect (GND)● ● ● ● to not use / connect ●
GND (5 V return) for Handle circuit ● ● ● to not use / connect (GND)●
+ 5 Volt (VCC) for Handle circuit ● ● Handle (output) signal
+ 5 Volt (VCC) for Joystick Hall circuit ● ● GND (5 V return) for Joystick Hall circuit
Sakae resistive joystick Y+ ● ● Sakae resistive joystick X+
Joystick Y axis (output) voltage ● ● Joystick X axis (output) voltage
Sakae resistive joystick Y- ● ● Sakae resistive joystick X-
Connector view from wire side

System
Response
• Check the connections Console Control card  Joystick#0
(CN 1039 pin 11, pin 13 and pin 15 to Joystick #0 – “X”
axis – see connector layout as on the above page 71).
• Check the voltage on TP29 (on Console Control card – see

the layout on the above page 70); as reference (ground)
use the Fast-on connector CN1017. In case of this error
This voltage, with the joystick in central (rest) position the corresponding
must be about 1.65 V (+/- 66 mV). Moving the Joystick #0 Joystick is disabled.
on the “X” axis, the voltage must change (in a linear If the joystick
behavior) inside the range 0.07 V (min) and 3.23 V (Max). This error check it is done at controlled motion it
every “unit power ON” as well was running, that
Joystick A/D ➢ If (during the above test) the voltage reach a value as “runtime”. motion is stopped.
channel #0 ≥ 3.234 Volt, change the Joystick and recalibrate its This error means that the A/D
02 07 00010
is at +3.3 Volt “zero” (see service manual - code 5793727-1EN). input voltage is greater than All the motions not
(Joystick #0 fault) the voltage it can reach with related to this error
➢ In case (during the above test) the voltage “remains the Joystick lever to the are correctly working.
always” inside the two above limits or, maximum position.
in case the problem is still present after a Joystick To resume the full
replacement, it is necessary to change the “Console unit functionalities, is
Control” card and/or the related “ARM CPU” module. necessary a FSE
After this operation, it is necessary to reconfigure & “visit”.
recalibrate the Console related parameters (see service
above recalibration, it is necessary to load on it the
same release of firmware it is already installed on the
other CPUs (see service manual - code 5793727-1EN).

System
Response
(CN 1039 pin 12, pin 14 and pin 16 to Joystick #0 – “Y”

on the “Y” axis, the voltage must change (in a linear If the joystick
02 07 00011

System
Response

02 07 00012

System
Response

02 07 00013

System
Response

02 07 00014

System
Response

02 07 00015

System
Response

channel #0 ≤ 0.067 Volt, change the Joystick and recalibrate its This error means that the A/D
02 07 00020
is at 0 Volt “zero” (see service manual - code 5793727-1EN). input voltage is lower than All the motions not
always” inside the two above limits or, minimum position.

System
Response

02 07 00021

System
Response

02 07 00022

System
Response

02 07 00023

System
Response

02 07 00024

System
Response

02 07 00025

System
Response
(CN 1039 pin 8, pin 7 and pin 6 to Joystick #0 “Handle” –
see connector layout as on the above page 71).
• Using as reference (ground) the Fast-on connector CN1017,

Check the voltage on TP32 (on Console Control card, see
the layout on the above page 70).
As by the handle’s “sensing status”, the voltage could In case of this error
have only the following values (considering VCC = 3.3 the corresponding
Volt): Joystick is disabled.
3.3 Volt (+0 / -66 mV ) = no sensor activated If the joystick
2.178 Volt (+/- 66 mV) = “H” sensor This error check it is done at controlled motion it
1.650 Volt (+/- 66 mV) = “L” sensor every “unit power ON” as well was running, that
Joystick#0 Handle
1.109 Volt (+/- 66 mV) = “H” + “L” sensors as “runtime”. motion is stopped.
A/D channel
This error means that the A/D
02 07 00034 is at “0” Volt
➢ If the voltage reaches a value ≤ 0.250 Volt, change the input voltage is lower than All the motions not
(Joystick #0 sensing
Joystick and recalibrate its “zero” (see service manual - the minimum voltage that the related to this error
handle fault)
code 5793727-1EN). handle internal circuit can are correctly working.
generate.
➢ In case the above test voltages are correct or, To resume the full
in case the problem is still present after a Joystick unit functionalities, is
replacement, it is necessary to change the “Console necessary a FSE
Control” card and/or the related “ARM CPU” module. “visit”.

System
Response

Joystick#1 Handle
A/D channel
02 07 00035 is at “0” Volt
handle fault)
generate.

System
Response

Joystick#2 Handle
A/D channel
02 07 00036 is at “0” Volt
handle fault)
generate.

System
Response
“Preparation” active • Check that the Console Integrated “Exposure push-

on Console button” is not pressed / not activated.
during start – up • Check that the Optional Console “Exposure hand-switch”
sequence. is not pressed / not activated. In case of this error
At the power ON, • In case the Optional Console “Exposure hand-switch” is disabled.
02 07 00037
the system “sense” present, disconnect it from the connector CN1002 (on the
that the console back-side) and recycle the power. Only for
“Preparation” ➢ In case the error is no more present, Change the troubleshooting
command on the complete Optional “Exposure hand-switch”. purposes, this check
Console Control is could be disabled by
active. • Disconnect, on the “Console Control” card the cable the FSE by acting on
arriving on the connector CN1025 and recycle the the Console CPU dip-
power. switch setting (see
➢ In case the error is no more present, Change the service manual - code
“Exposure” active complete “Exposure push-button assembly” and its 5793727-1EN).
on Console connection cable. Please to take care
during start – up ➢ In case the error is still present, it is necessary to that the above
sequence. change the “Console Control” card and/or the related operation is a safety
“ARM CPU” module. bypass and, it is
02 07 00038 At the power ON, After this operation, it is necessary to reconfigure & responsibility of the
the system “sense” recalibrate the Console related parameters (see service FSE to re-enable this
that the “Exposure” manual - code 5793727-1EN). safety before to
command on the If the ARM CPU module it was also changed, before the leave the site.
Console Control is above recalibration, it is necessary to load on it the
active. same release of firmware it is already installed on the

System
Response

At the power ON, the system “sense” that the
“Fluoroscopy” input on the Console Control is active.
disabled.
• Check that the “fluoroscopy Foot-pedal” is not pressed
Only for
/ not activated.
troubleshooting
purposes, this check
• Disconnect the connector CN1001 (on the console
could be disabled by
back-side) and recycle the power.
“Fluoroscopy” the FSE by acting on
➢ In case the error is no more present, Change the
active the Console CPU dip-
complete Fluoroscopy foot-pedal (with its connection). This error check it is done at
02 07 00039 on Console switch setting (see
➢ In case the error is still present, it is necessary to every “unit power ON”.
during start – up service manual - code
change the “Console Control” card and/or the related
sequence. 5793727-1EN).
“ARM CPU” module.
Please to take care
that the above
recalibrate the Console related parameters (see
operation is a safety
service manual - code 5793727-1EN).
bypass and, it is
responsibility of the
FSE to re-enable this
safety before to
leave the site.

System
Response
The console CPU is not able to communicate with the

(capacitive) Touch-button control card (mounted under
the glass-upper part) of the console.
• Check that the connection between CN1024 on the
“Console Control” card and J1 on the capacitive touch-
disabled.
button control card (Better 4CST1017604).
If a motion (any one) it
was running, that
• If no other errors are present, change the capacitive
motion is stopped.
touch-button control card (Better 4CST1017604) and its
extension (Better 4CST2017604).
Link error between In case of salutary
Console control and fault, to resume the
02 07 00040 • In case the error is still present, change the “Console “runtime”
Touch-button unit functionality it is
Control” card and/or the related “ARM CPU” module.
control sufficient a power
cycle.
In case the fault is
permanent, to resume
the unit
functionalities is
release of firmware it is already installed on the other
necessary a FSE
CPUs (see service manual - code 5793727-1EN).
“visit”.
• Finally, if the error is again present, change the complete
“capacitive touch-button” plate (the glass upper
surface of the console).

System
Response
• If a pushbutton it was unintentionally “touched”

during the Power ON sequence, please recycle the power.
• Check that no objects (that can activate the capacitive

push-buttons) are present on the upper surface of the
console.
Push button In case of this error
• Switch Off the unit, Disconnect, on the capacitive
“active” the unit functions are
touch-button control card (Better 4CST1017604), the flat This error check it is done at
02 07 00041 on Console disabled.
connectors J7A1 and J7B1. Switch On the unit and check every “unit power ON”.
during start – up
again if the error is present / displayed.
sequence. In case the fault is
➢ In case the error is not present, change the complete
“capacitive touch-button” plate (the glass upper permanent, to resume
surface of the console). the unit
➢ In case the error is still present, change the functionalities is
capacitive touch-button control card (Better necessary a FSE
4CST1017604) and its extension (Better “visit”.
4CST2017604).
Touch-button
• Change the capacitive touch-button control card
control card This error check it is done at
02 07 00043 (Better 4CST1017604) and its extension (Better
firmware version every “unit power ON”.
4CST2017604).
error

In relation to the measuring points mentioned on the troubleshooting of the following 6 (six) error codes,
̴
(errors 02 07 00044 02 07 00049).

Pin #1

System
Response
• If a joystick it was unintentionally “moved” during the

Power On sequence, please recycle the power.
• If there are objects that “push/touch” the joystick handle

(that “set” the handle “out” from the rest position), remove
those objects and recycle the power.
• Check that that the joystick lever/handle could be moved

freely and that it comes back to the central, rest position.
➢ In case of (mechanical) issue, change the Joystick and
the corresponding
recalibrate its “zero” (see service manual - code This error check it is done at
Joystick is disabled.
5793727-1EN). every “unit power ON” as well
as “runtime”.
All the motions not
• Check the Console Control card  Joystick#0
Console related to this error
connections This error means that, during
Joystick #0 are correctly working.
02 07 00044 (CN 1039 pin 11, pin 13 and pin 15 to Joystick #0 – “X” the Power ON sequence, the
X axis “active”
axis – see connector layout as on the above page 92). A/D input voltage is not
(Joystick #0 fault) In case of a real fault
corresponding to the one
(see solution column),
• Check the voltage on TP29 (on Console Control card – see expected for the “rest
to resume the full unit
the layout on the above page 91); as reference (ground) position” of the Joystick
functionalities it is
use the Fast-on connector CN1017. handle.
necessary a FSE
This voltage, with the joystick in central (rest) position
“visit”.
must be about 1.65 V (+/- 66 mV).


This error check it is done at the corresponding
every “unit power ON” as well Joystick is disabled.
as “runtime”.
Console
➢ If the above voltage is not correct, change the Joystick All the motions not
Joystick #0
02 07 00044 and recalibrate its “zero” (see service manual - code This error means that, during related to this error
X axis “active”
5793727-1EN). the Power ON sequence, the are correctly working.
(Joystick #0 fault)
A/D input voltage is not
➢ If the above voltage is correct, recalibrate the “zero” of corresponding to the one In case of a real fault
the Joystick (see service manual - code 5793727-1EN) expected for the “rest (see solution column),
and check again. position” of the Joystick to resume the full unit
handle. functionalities it is
❖ In case the problem / error is still present it is necessary a FSE
necessary to change the “Console Control” card “visit”.
and/or the related “ARM CPU” module.
After this operation, it is necessary to reconfigure
& recalibrate the Console related parameters (see
If the ARM CPU module it was also changed, before
the above recalibration, it is necessary to load on it
the same release of firmware it is already installed
on the other CPUs (see service manual - code
5793727-1EN).

System
Response

Power ON sequence, please recycle the power.


➢ In case of (mechanical) issue, change the Joystick and In case of this error
recalibrate its “zero” (see service manual - code the corresponding
5793727-1EN). Joystick is disabled.
every “unit power ON” as well
as “runtime”.
• Check the Console Control card  Joystick#0 All the motions not
Console connections related to this error
This error means that, during
Joystick #0 (CN 1039 pin 12, pin 14 and pin 16 to Joystick #0 – “Y” are correctly working.
02 07 00045 the Power ON sequence, the
Y axis “active” axis – see connector layout as on the above page 92).
• Check the voltage on TP31 (on Console Control card – see (see solution column),
expected for the “rest
the layout on the above page 91); as reference (ground) to resume the full unit
position” of the Joystick
use the Fast-on connector CN1017. functionalities it is
handle.
This voltage, with the joystick in central (rest) position necessary a FSE
must be about 1.65 V (+/- 66 mV). “visit”.


as “runtime”.
Console
Joystick #0
Y axis “active”
(Joystick #0 fault)
5793727-1EN).

System
Response



as “runtime”.
• Check the Console Control card  Joystick#0 connections All the motions not
Console (CN 1040 pin 11, pin 13 and pin 15 to Joystick #1 – “X” related to this error
Joystick #1 axis – see connector layout as on the above page 92). are correctly working.
X axis “active”
(Joystick #1 fault) • Check the voltage on TP27 (on Console Control card – see In case of a real fault
the layout on the above page 91); as reference (ground) (see solution column),
use the Fast-on connector CN1017. to resume the full unit
This voltage, with the joystick in central (rest) position functionalities it is
handle.
must be about 1.65 V (+/- 66 mV). necessary a FSE
“visit”.


as “runtime”.
Console
Joystick #1
X axis “active”
(Joystick #1 fault)
5793727-1EN).

System
Response



as “runtime”.
Console (CN 1040 pin 12, pin 14 and pin 16 to Joystick #1 – “Y” related to this error
Y axis “active”
handle.
“visit”.


as “runtime”.
Console
Joystick #1
Y axis “active”
(Joystick #1 fault)
5793727-1EN).

System
Response



as “runtime”.
Console (CN 1041 pin 11, pin 13 and pin 15 to Joystick #2 – “X” related to this error
X axis “active”
handle.
“visit”.


as “runtime”.
Console
Joystick #2
X axis “active”
(Joystick #2 fault)
5793727-1EN).

System
Response



as “runtime”.
Console (CN 1041 pin 12, pin 14 and pin 16 to Joystick #2 – “Y” related to this error
Y axis “active”
handle.
“visit”.


as “runtime”.
Console
Joystick #2
Y axis “active”
(Joystick #2 fault)
5793727-1EN).

System
Response
• Reload on the “T” CPU card the same release of
software it is already installed on the other CPUs and,
eventually, reconfigure & recalibrate the “T” CPU
disabled.
related parameters as described on the service manual - This error check it is done at
“T” CPU (Clisis Main)
02 07 00050 code 5793727-1EN every “unit power ON”.
not responding To resume the unit
functionalities is
• If the problem is still present,
necessary a FSE
execute the same troubleshooting of the (following)
“visit”.
error 02 07 00061. ➔
Wrong firmware disabled.
software it is already installed on the other CPUs and, This error check it is done at
version loaded on
02 07 00051 eventually, reconfigure & recalibrate the “T” CPU every “unit power ON”.
the “T” CPU (Clisis To resume the unit
related parameters as described on the service manual -
Main) functionalities is
code 5793727-1EN
necessary a FSE
“visit”.
• Reload on the Collimator CPU card the same release of
eventually, reconfigure & recalibrate the Collimator
disabled.
CPU related parameters as described on the service This error check it is done at
“Collimator” CPU
02 07 00052 manual - code 5793727-1EN. every “unit power ON”.
functionalities is
necessary a FSE
“visit”.
error 02 07 00062. ➔

System
Response
version loaded on
02 07 00053 eventually, reconfigure & recalibrate the Collimator every “unit power ON”.
the “Collimator” To resume the unit
CPU related parameters as described on the service
CPU functionalities is
manual - code 5793727-1EN.
necessary a FSE
“visit”.
• Reload on the SFD CPU card the same release of

eventually, reconfigure its switches/jumpers and load
disabled.
its default parameters as described on the service This error check it is done at
“SFD” CPU
02 07 00054 manual - code 5793727-1EN. every “unit power ON”.
functionalities is
necessary a FSE
“visit”.
error 02 07 00063. ➔

version loaded on
02 07 00055 eventually, reconfigure its switches/jumpers and load every “unit power ON”.
the To resume the unit
its default parameters as described on the service manual
“SFD” CPU functionalities is
- code 5793727-1EN.
necessary a FSE
“visit”.

System
Response
• Reload on all the CPU cards the same release of In case of this error
software and, eventually, reconfigure & recalibrate the the unit functions are
Console CPU related parameters as described on the disabled.
Firmware versions service manual - code 5793727-1EN.
02 07 00056 every “unit power ON”.
not synchronized. To resume the unit
• If the problem is still present, functionalities is
execute the same troubleshooting of the (following) necessary a FSE
error 02 07 00060. ➔ “visit”.

Wrong firmware • Reload on the Remote console CPU card (on the Arm
disabled.
version loaded on CPU) the same release of software it is already installed This error check it is done at
02 07 00057 the on the other CPUs and, eventually, reconfigure and every “unit power ON”.
To resume the unit
“In-room” Console recalibrate it as described on the service manual - code
functionalities is
CPU 5793727-1EN.
necessary a FSE
“visit”.

In relation to the measuring points mentioned on the troubleshooting of the following 5 (five) error codes,
̴
(errors 02 07 00060 02 07 00064).
Can_H
Can_L
Can_GND

System
Response
• Check that SW4 (on Console Control card – see the

layout on the above page 108) is mounted.

layout on the above page 108) is mounted on position
1-2, or it is completely removed (not present).
• Check CAN_GND line. See appendix 01.
• Check CAN line impedance.

Switch Off the unit and measure the impedance between
the pin 9 (Can_H) and pin 10 (CAN_L) of CN1036 (on
Console Control card – see the layout on the above page
disabled.
108). The measured impedance must be about 60
Ohm (60 Ohm +/- 10 Ohm).
“Console” CPU CAN This error check it is done at was running, that
02 07 00060 controller is in every “unit power ON” as well motion is stopped.
❖ In case the measured impedance is about 120 Ohm
“offline” condition. as “runtime”.
(110 ÷ 130 Ohm), the CAN line is broken or, the
To resume the unit
“Collimator side” terminator is not mounted (see
functionalities is
appendix 02).
necessary a FSE
❖ In case the measured impedance is less than 45 Ohm,
“visit”.
the CAN line is in “short circuit” or, a CPU card is
defective. ( see appendix 03 )

• Check CAN line insulation to ground.

Switch Off the unit and measure, on Console Control card In case of this error
(see the layout on the above page 108): the unit functions are
disabled.
a) The impedance between the pin 9 (Can_H) and pin 8 If a motion (any one) it
“Console” CPU CAN (CAN_GND) of CN1036. This error check it is done at was running, that
02 07 00060 controller is in b) The impedance between the pin 10 (Can_L) and pin every “unit power ON” as well motion is stopped.
“offline” condition. 8 (CAN_GND) of CN1036. as “runtime”.
To resume the unit
The normal impedance value, in both cases, it is greater functionalities is
than 1 Megaohm. necessary a FSE
“visit”.
➢ In case the impedance is lower of 1 Megaohm, there is
a (CAN line) problem on the cable (insulation) and/or
on CPU card(s). ( see appendix 04 )
❖ In case all the above test / values are correct, it is

necessary to change the “Console Control” card and/or the
related “ARM CPU” module.

System
Response


Ohm (60 Ohm +/- 10 Ohm). In case of this error
❖ In case the measured impedance is about 120 Ohm disabled.
(110 ÷ 130 Ohm), the CAN line is broken or, the If a motion (any one) it
CAN timeout “Collimator side” terminator is not mounted (see This error check it is done at was running, that
02 07 00061 “Console” CPU to appendix 02). every “unit power ON” as well motion is stopped.
“T” CPU (Clisis Main). ❖ In case the measured impedance is less than 45 Ohm, as “runtime”.
the CAN line is in “short circuit” or, a CPU card is To resume the unit
defective. ( see appendix 03 ) functionalities is
necessary a FSE
“visit”.


disabled.
• Check CAN line insulation to ground. If a motion (any one) it
CAN timeout Switch Off the unit and measure, on Console Control card This error check it is done at was running, that
02 07 00061 “Console” CPU to (see the layout on the above page 108): every “unit power ON” as well motion is stopped.
“T” CPU (Clisis Main). as “runtime”.
a) The impedance between the pin 9 (Can_H) and pin 8 To resume the unit
(CAN_GND) of CN1036. functionalities is
b) The impedance between the pin 10 (Can_L) and pin necessary a FSE
8 (CAN_GND) of CN1036. “visit”.
The normal impedance value, in both cases, it is greater

than 1 Megaohm.


necessary to change the “T” CPU card. See “Note” on the
following.
5793727-1EN).

System
Response


“Collimator” CPU ❖ In case the measured impedance is less than 45 Ohm, as “runtime”.
necessary a FSE
“visit”.


disabled.
“Collimator” CPU as “runtime”.

than 1 Megaohm.


necessary to change the “Collimator” CPU card. See “Note”
on the following.

System
Response


“SFD” CPU ❖ In case the measured impedance is less than 45 Ohm, as “runtime”.
necessary a FSE
“visit”.


disabled.
“SFD” CPU as “runtime”.

than 1 Megaohm.


necessary to change the “SFD” CPU card. See “Note” on
the following.
(code 5793727-1EN).

System
Response
If this error is displayed (and the option is not present),

please to consider to reload the complete unit firmware,
configure and calibrate the system and, last, go to execute the
troubleshooting of error 02 07 00060.
CAN timeout • Check that SW4 (on Main Console Control card – see the disabled.
layout on the above page 108) is mounted. If a motion (any one) it
“Main Console” CPU This error check it is done at
was running, that
02 07 00064 to every “unit power ON” as well
“in-room console” • Check completely the CAN line. as “runtime”.
motion is stopped.
CPU
• Go to appendix 01. To resume the unit
functionalities is
• Go to appendix 02. necessary a FSE
“visit”.
• Go to appendix 03.
• Go to appendix 04.

System
Response
At the power ON, the Console (ARM) CPU check the

consistency of the data stored in the EEprom (calibration)
memory.
In case of error, the CPU it loads some default values and
the error code is generated.
• If this is a new installation of the “Console CPU” card

(Console Control/Interface and/or ARM CPU), please to
re-calibrate the Console parameters ad described in
the service manual - code 5793727-1EN.
disabled.
EEprom Init above recalibration, it is necessary to load on it the same This error check it is done at
02 07 00070 (load default) release of firmware it is already installed on the other every “unit power ON”.
To resume the full
“Console” CPU CPUs (see service manual - code 5793727-1EN).
unit functionalities is
necessary a FSE
❖ If this error is displayed on an “already running” unit,
“visit”.
please to consider to change the “Console Control” card
CPUs (see service manual - code 5793727-1EN)

"In-Room (remote) Console" CPU card (generated) Errors

System
Response
On the “in-room” console

• Recalibrate the “zero” offset of the joysticks (see service
manual - code 5793727-1EN). In case of this error
• Replace “Console Control card” and/or the related the unit functions are
“in-room” console
“ARM CPU module”. disabled.
Calibration
After this operation, it is necessary to reconfigure & This check it is done at every
02 08 00000 parameters
recalibrate the Console related parameters (see service “unit power ON” To resume the unit
(memory) CRC error
manual - code 5793727-1EN). functionalities is
(Joystick data section)
If the ARM CPU module it was already changed, before the necessary a FSE
above recalibration, it is necessary to load on it the same “visit”.

• Reconfigure & recalibrate the Console related parameter
(see service manual - code 5793727-1EN). In case of this error
• Replace “Console Control card” and/or the related the unit functions are
“in-room” console “ARM CPU module”. disabled.
Configuration After this operation, it is necessary to reconfigure & This check it is done at every
02 08 00001
parameters recalibrate the Console related parameters (see service “unit power ON” To resume the unit
(memory) CRC error manual - code 5793727-1EN). functionalities is
If the ARM CPU module it was already changed, before the necessary a FSE
above recalibration, it is necessary to load on it the same “visit”.

In relation to the measuring points mentioned on the troubleshooting of the following 15 error codes,
̴ ̴ ̴
(errors 02 08 00010 02 08 00015, 02 08 00020 02 08 00025, 02 08 00034 02 08 00036).

Pin #1

System
Response

use the Fast-on connector CN1017.
the corresponding
must be about 1.65 V (+/- 66 mV). Moving the Joystick #0
If the joystick
on the “X” axis, the voltage must change (in a linear
This error check it is done at controlled motion it
behavior) inside the range 0.07 V (min) and 3.23 V (Max).
as “runtime”. motion is stopped.
Joystick A/D ➢ If (during the above test) the voltage reach a value
02 08 00010 channel #0 ≥ 3.234 Volt, change the Joystick and recalibrate its
input voltage is greater than All the motions not
is at +3.3 Volt “zero” (see service manual - code 5793727-1EN).
the voltage it can reach with related to this error
(Joystick #0 fault)
the Joystick lever to the are correctly working.
➢ In case (during the above test) the voltage “remains
maximum position.
always” inside the two above limits or,
To resume the full
in case the problem is still present after a Joystick
unit functionalities, is
replacement, it is necessary to change the “Console
necessary a FSE
“visit”.

System
Response

the corresponding
If the joystick
on the “Y” axis, the voltage must change (in a linear
(Joystick #0 fault)
maximum position.
To resume the full
necessary a FSE
“visit”.

System
Response

the corresponding
If the joystick
(Joystick #1 fault)
maximum position.
To resume the full
necessary a FSE
“visit”.

System
Response

the corresponding
If the joystick
(Joystick #1 fault)
maximum position.
To resume the full
necessary a FSE
“visit”.

System
Response

the corresponding
If the joystick
(Joystick #2 fault)
maximum position.
To resume the full
necessary a FSE
“visit”.

System
Response

the corresponding
If the joystick
(Joystick #2 fault)
maximum position.
To resume the full
necessary a FSE
“visit”.

System
Response

the corresponding
If the joystick
02 08 00020 channel #0 ≤ 0.067 Volt, change the Joystick and recalibrate its
input voltage is lower than All the motions not
is at 0 Volt “zero” (see service manual - code 5793727-1EN).
(Joystick #0 fault)
minimum position.
To resume the full
necessary a FSE
“visit”.

System
Response

the corresponding
If the joystick
(Joystick #0 fault)
minimum position.
To resume the full
necessary a FSE
“visit”.

System
Response

the corresponding
If the joystick
(Joystick #1 fault)
minimum position.
To resume the full
necessary a FSE
“visit”.

System
Response

the corresponding
If the joystick
(Joystick #1 fault)
minimum position.
To resume the full
necessary a FSE
“visit”.

System
Response

the corresponding
If the joystick
(Joystick #2 fault)
minimum position.
To resume the full
necessary a FSE
“visit”.

System
Response

the corresponding
If the joystick
(Joystick #2 fault)
minimum position.
To resume the full
necessary a FSE
“visit”.
manual - code 5793727-1EN). If the ARM CPU module it
was also changed, before the above recalibration, it is
necessary to load on it the same release of firmware it
is already installed on the other CPUs (see service

System
Response

As by the handle’s “sensing status”, the voltage could
the corresponding
have only the following values (considering VCC = 3.3
Volt):
If the joystick
3.3 Volt (+0 / -66 mV ) = no sensor activated
2.178 Volt (+/- 66 mV) = “H” sensor
“in-room” console every “unit power ON” as well was running, that
1.650 Volt (+/- 66 mV) = “L” sensor
Joystick#0 Handle as “runtime”. motion is stopped.
1.109 Volt (+/- 66 mV) = “H” + “L” sensors
A/D channel This error means that the A/D
02 08 00034
is at “0” Volt input voltage is lower than All the motions not
➢ If the voltage reaches a value ≤ 0.250 Volt, change the
(Joystick #0 sensing the minimum voltage that the related to this error
Joystick and recalibrate its “zero” (see service manual -
handle fault) handle internal circuit can are correctly working.
code 5793727-1EN).
generate.
To resume the full
➢ If the above test voltages are correct or, if the problem
is still present after a Joystick replacement, it is
necessary a FSE
necessary to change the “Console Control” card and/or
“visit”.
the related “ARM CPU” module.

System
Response

the corresponding
Volt):
If the joystick
2.178 Volt (+/- 66 mV) = “H” sensor
1.650 Volt (+/- 66 mV) = “L” sensor
02 08 00035
code 5793727-1EN).
generate.
To resume the full
necessary a FSE
“visit”.

System
Response

the corresponding
Volt):
If the joystick
2.178 Volt (+/- 66 mV) = “H” sensor
1.650 Volt (+/- 66 mV) = “L” sensor
02 08 00036
code 5793727-1EN).
generate.
To resume the full
necessary a FSE
“visit”.

System
Response
“Preparation” active • Check that the Console Integrated “Exposure push-
on “in-room” Console button” is not pressed / not activated.
during start – up • Check that the Optional Console “Exposure hand-switch”
sequence. is not pressed / not activated. In case of this error
02 08 00037 At the power ON, • In case the Optional Console “Exposure hand-switch” is disabled.
the system “sense” present, disconnect it from the connector CN1002 (on the
that the console back-side) and recycle the power. Only for
“Preparation” ➢ In case the error is no more present, Change the troubleshooting
command on the complete Optional “Exposure hand-switch”. purposes, this check
Console Control is could be disabled by
active. • Disconnect, on the “Console Control” card the cable the FSE by acting on
arriving on the connector CN1025 and recycle the This error check it is done at the Console CPU dip-
switch setting (see
power. every “unit power ON”.
service manual - code
➢ In case the error is no more present, Change the 5793727-1EN).
“in-room” console complete “Exposure push-button assembly” and its
“Exposure” active Please to take care
connection cable. that the above
on “in-room” Console ➢ In case the error is still present, it is necessary to
during start – up operation is a safety
change the “Console Control” card and/or the related bypass and, it is
sequence. “ARM CPU” module. responsibility of the
02 08 00038 After this operation, it is necessary to reconfigure & FSE to re-enable this
At the power ON, recalibrate the Console related parameters (see service
the system “sense” safety before to
manual - code 5793727-1EN). leave the site.
that the “Exposure” If the ARM CPU module it was also changed, before the
command on the above recalibration, it is necessary to load on it the
Console Control is same release of firmware it is already installed on the
active. other CPUs (see service manual - code 5793727-1EN).

System
Response
At the power ON, the system “sense” that the In case of this error
“Fluoroscopy” input on the “in-room” Console Control is the unit functions are
active. disabled.
• Check that the “fluoroscopy Foot-pedal” is not pressed Only for

/ not activated. troubleshooting
purposes, this check
• Disconnect the connector CN1001 (on the console could be disabled by
back-side) and recycle the power. the FSE by acting on
“Fluoroscopy”
➢ In case the error is no more present, Change the the Console CPU dip-
active This error check it is done at
02 08 00039 complete Fluoroscopy foot-pedal (with its connection). switch setting (see
on “in-room” Console every “unit power ON”.
➢ In case the error is still present, it is necessary to service manual - code
during start – up 5793727-1EN).
change the “Console Control” card and/or the related
sequence. Please to take care
“ARM CPU” module.
After this operation, it is necessary to reconfigure & that the above
recalibrate the Console related parameters (see operation is a safety
service manual - code 5793727-1EN). bypass and, it is
If the ARM CPU module it was also changed, before the responsibility of the
above recalibration, it is necessary to load on it the FSE to re-enable this
same release of firmware it is already installed on the safety before to
other CPUs (see service manual - code 5793727-1EN). leave the site.

System
Response
The “in-room” console CPU is not able to communicate

with the (capacitive) Touch-button control card (mounted
under the glass-upper part) of the console.
• Check that the connection between CN1024 on the the unit functions are
“Console Control” card and J1 on the capacitive touch- disabled.
button control card (Better 4CST1017604). If a motion (any one) it
was running, that
• If no other errors are present, change the capacitive motion is stopped.
touch-button control card (Better 4CST1017604) and its
“in-room” console extension (Better 4CST2017604). In case of salutary
Link error between This check it is done fault, to resume the
02 08 00040 Console control and • In case the error is still present, change the “Console “runtime” unit functionality it is
Touch-button Control” card and/or the related “ARM CPU” module. sufficient a power
control After this operation, it is necessary to reconfigure & cycle.
manual - code 5793727-1EN). In case the fault is
If the ARM CPU module it was also changed, before the permanent, to resume
above recalibration, it is necessary to load on it the same the unit
release of firmware it is already installed on the other functionalities is
CPUs (see service manual - code 5793727-1EN). necessary a FSE
“visit”.
• Finally, if the error is again present, change the complete
“capacitive touch-button” plate (the glass upper
surface of the console).

System
Response
• If a pushbutton it was unintentionally “touched”

during the Power ON sequence, please recycle the power.
• Check that no objects (that can activate the capacitive

push-buttons) are present on the upper surface of the
console.
Push button In case of this error
• Switch Off the unit, Disconnect, on the capacitive
“active” This error check it is done at the unit functions are
02 08 00041 touch-button control card (Better 4CST1017604), the flat
on “in-room” Console every “unit power ON”. disabled.
connectors J7A1 and J7B1. Switch On the unit and check
during start – up
again if the error is present / displayed.
sequence. In case the fault is
➢ In case the error is not present, change the complete
“capacitive touch-button” plate (the glass upper permanent, to resume
surface of the console). the unit
➢ In case the error is still present, change the functionalities is
capacitive touch-button control card (Better necessary a FSE
4CST1017604) and its extension (Better “visit”.
4CST2017604).

Touch-button
• Change the capacitive touch-button control card This error check it is done at
02 08 00043 control card
(Better 4CST1017604) and its extension (Better every “unit power ON”.
firmware version
4CST2017604).
error

In relation to the measuring points mentioned on the troubleshooting of the following 6 (six) error codes,
̴
(errors 02 08 00044 02 08 00049).

Pin #1

System
Response

power ON sequence, please recycle the power.


the corresponding
➢ In case of (mechanical) issue, change the Joystick and This error check it is done at
recalibrate its “zero” (see service manual - code every “unit power ON” as well
5793727-1EN). as “runtime”.
All the motions not
“in-room” console related to this error
• Check the Console Control card  Joystick#0 This error means that, during
02 08 00044 connections the Power ON sequence, the
X axis “active”
(CN 1039 pin 11, pin 13 and pin 15 to Joystick #0 – “X” A/D input voltage is not
axis – see connector layout as on the above page 142). corresponding to the one
• Check the voltage on TP29 (on Console Control card – see position” of the Joystick
the layout on the above page 141); as reference (ground) handle.
necessary a FSE
“visit”.


as “runtime”.
Joystick #0
X axis “active”
(Joystick #0 fault)
5793727-1EN).

System
Response



➢ In case of (mechanical) issue, change the Joystick and the corresponding
recalibrate its “zero” (see service manual - code Joystick is disabled.
5793727-1EN).
as “runtime”.
All the motions not
“in-room” console • Check the Console Control card  Joystick#0 connections related to this error
Joystick #0 (CN 1039 pin 12, pin 14 and pin 16 to Joystick #0 – “Y” are correctly working.
Y axis “active” axis – see connector layout as on the above page 142).
• Check the voltage on TP31 (on Console Control card – see (see solution column),
the layout on the above page 141); as reference (ground) to resume the full unit
use the Fast-on connector CN1017. functionalities it is
handle.
This voltage, with the joystick in central (rest) position necessary a FSE
must be about 1.65 V (+/- 66 mV). “visit”.


as “runtime”.
Joystick #0
Y axis “active”
(Joystick #0 fault)
5793727-1EN).

System
Response



the corresponding
All the motions not
• Check the Console Control card  Joystick#0 connections This error means that, during
X axis “active”
necessary a FSE
“visit”.


as “runtime”.
Joystick #1
X axis “active”
(Joystick #1 fault)
5793727-1EN).

System
Response



the corresponding
All the motions not
02 08 00047 (CN 1040 pin 12, pin 14 and pin 16 to Joystick #1 – “Y” the Power ON sequence, the
Y axis “active”
necessary a FSE
“visit”.


as “runtime”.
Joystick #1
Y axis “active”
(Joystick #1 fault)
5793727-1EN).

System
Response



the corresponding
All the motions not
X axis “active”
necessary a FSE
“visit”.


as “runtime”.
Joystick #2
X axis “active”
(Joystick #2 fault)
If the ARM CPU module it was already changed,
before the above recalibration, it is necessary to
load on it the same release of firmware it is already
installed on the other CPUs (see service manual -
code 5793727-1EN).

System
Response



the corresponding
All the motions not
02 08 00049 (CN 1041 pin 12, pin 14 and pin 16 to Joystick #2 – “Y” the Power ON sequence, the
Y axis “active”
necessary a FSE
“visit”.


as “runtime”.
Joystick #2
Y axis “active”
(Joystick #2 fault)
5793727-1EN).

System
Response
eventually, reconfigure & recalibrate the “T” CPU
disabled.
“in-room” console related parameters as described on the service manual - This error check it is done at
02 08 00050 “T” CPU (Clisis Main) code 5793727-1EN. every “unit power ON”.
To resume the unit
not responding
functionalities is
necessary a FSE
“visit”.
error 02 08 00061. ➔
“in-room” console • Reload on the “T” CPU card the same release of
disabled.
Wrong firmware software it is already installed on the other CPUs and, This error check it is done at
02 08 00051 version loaded on eventually, reconfigure & recalibrate the “T” CPU every “unit power ON”.
To resume the unit
the “T” CPU (Clisis related parameters as described on the service manual -
functionalities is
Main) code 5793727-1EN.
necessary a FSE
“visit”.
eventually, reconfigure & recalibrate the Collimator
disabled.
“in-room” console CPU related parameters as described on the service This error check it is done at
02 08 00052 “Collimator” CPU manual - code 5793727-1EN. every “unit power ON”.
To resume the unit
not responding
functionalities is
necessary a FSE
“visit”.
error 02 08 00062. ➔

System
Response
“in-room” console • Reload on the Collimator CPU card the same release of
disabled.
02 08 00053 version loaded on eventually, reconfigure & recalibrate the Collimator every “unit power ON”.
To resume the unit
the “Collimator” CPU related parameters as described on the service
functionalities is
CPU manual - code 5793727-1EN.
necessary a FSE
“visit”.

eventually, reconfigure its switches/jumpers and load
disabled.
“in-room” console its default parameters as described on the service manual This error check it is done at
02 08 00054 “SFD” CPU - code 5793727-1EN. every “unit power ON”.
To resume the unit
not responding
functionalities is
necessary a FSE
“visit”.
error 02 08 00063. ➔

“in-room” console • Reload on the SFD CPU card the same release of
disabled.
02 08 00055 version loaded on eventually, reconfigure its switches/jumpers and load every “unit power ON”.
To resume the unit
the its default parameters as described on the service manual
functionalities is
“SFD” CPU - code 5793727-1EN.
necessary a FSE
“visit”.

System
Response
• Reload on all the CPU cards the same release of

eventually, reconfigure & recalibrate the Console CPU
disabled.
“in-room” console related parameter as described on the service manual - This error check it is done at
02 08 00056 Firmware versions code 5793727-1EN. every “unit power ON”.
To resume the unit
not synchronized.
functionalities is
necessary a FSE
“visit”.
error 02 08 00060. ➔
The “Main Keyboard” CPU is a “planned” Option.

If this error is displayed (and the option is not present),
“in-room” console please to consider to reload the complete unit firmware,
disabled.
Wrong firmware configure and calibrate the system and, last, change the This error check it is done at
02 08 00057 version loaded on (standard) Console CPU card. every “unit power ON”.
To resume the unit
the
functionalities is
“Main Console” CPU • Reload on the Remote console CPU card the same
necessary a FSE
release of software it is already installed on the other
“visit”.
CPUs and, eventually, reconfigure it.

In relation to the measuring points mentioned on the troubleshooting of the following 5 (five) error codes,
̴
(errors 02 08 00060 02 08 00064).
Can_H
Can_L
Can_GND

System
Response


layout on the above page 158) is mounted on position
1-2, or it is completely removed (not present).

Switch Off the unit and measure the impedance between In case of this error
the pin 9 (Can_H) and pin 10 (CAN_L) of CN1036 (on the unit functions are
Console Control card – see the layout on the above page disabled.
108). The measured impedance must be about 60 If a motion (any one) it
Ohm (60 Ohm +/- 10 Ohm). This error check it is done at was running, that
CPU CAN controller
02 08 00060 every “unit power ON” as well motion is stopped.
is in “offline”
❖ In case the measured impedance is about 120 Ohm as “runtime”.
condition.
(110 ÷ 130 Ohm), the CAN line is broken or, the To resume the unit
“Collimator side” terminator is not mounted (see functionalities is
appendix 02). necessary a FSE
❖ In case the measured impedance is less than 45 Ohm, “visit”.


Switch Off the unit and measure, on Console Control card In case of this error
(see the layout on the above page 158): the unit functions are
disabled.
a) The impedance between the pin 9 (Can_H) and pin 8 If a motion (any one) it
(CAN_GND) of CN1036. This error check it is done at was running, that
CPU CAN controller
02 08 00060 b) The impedance between the pin 10 (Can_L) and pin every “unit power ON” as well motion is stopped.
is in “offline”
8 (CAN_GND) of CN1036. as “runtime”.
condition.
To resume the unit
The normal impedance value, in both cases, it is greater functionalities is
than 1 Megaohm. necessary a FSE
“visit”.

necessary to change the “Console Control” card and/or the
related “ARM CPU” module.

System
Response
• Check that SW4 (on “in-room” Console Control card –

see the layout on the above page 158) is mounted.

Ohm (60 Ohm +/- 10 Ohm).
disabled.
CAN timeout (110 ÷ 130 Ohm), the CAN line is broken or, the
This error check it is done at was running, that
“in-room” console “Collimator side” terminator is not mounted (see
CPU to appendix 02).
as “runtime”.
“T” CPU (Clisis Main). ❖ In case the measured impedance is less than 45 Ohm,
To resume the unit
functionalities is
necessary a FSE
“visit”.


disabled.
CAN timeout
Switch Off the unit and measure, on Console Control card This error check it is done at was running, that
02 08 00061 (see the layout on the above page 158): every “unit power ON” as well motion is stopped.
CPU to
as “runtime”.
“T” CPU (Clisis Main).

than 1 Megaohm.


necessary to change the “T” CPU card. See “Note” on the
following.
5793727-1EN).

System
Response


Ohm (60 Ohm +/- 10 Ohm).
disabled.
as “runtime”.
“Collimator” CPU ❖ In case the measured impedance is less than 45 Ohm,
To resume the unit
functionalities is
necessary a FSE
“visit”.


disabled.
CAN timeout
CPU to
as “runtime”.

than 1 Megaohm.


necessary to change the “Collimator” CPU card. See “Note”
on the following.

System
Response


Ohm (60 Ohm +/- 10 Ohm).
disabled.
as “runtime”.
“SFD” CPU ❖ In case the measured impedance is less than 45 Ohm,
To resume the unit
functionalities is
necessary a FSE
“visit”.


disabled.
CAN timeout
CPU to
as “runtime”.
“SFD” CPU

than 1 Megaohm.


necessary to change the “SFD” CPU card. See “Note” on
the following.
(code 5793727-1EN).

System
Response
If this error is displayed, please to consider to reload the

complete unit firmware, configure and calibrate the system
and, last, go to execute the troubleshooting of error 02 08
00060. ➔
• Check that SW4 (on “in-room” Console Control card – see

the layout on the above page 158) is mounted.

Switch Off the unit and measure the impedance between In case of this error
the pin 9 (Can_H) and pin 10 (CAN_L) of CN1036 (on the unit functions are
Console Control card – see the layout on the above page disabled.
108). The measured impedance must be about 60 Ohm If a motion (any one) it
CAN timeout
(60 Ohm +/- 10 Ohm). This error check it is done at was running, that
CPU to
❖ In case the measured impedance is about 120 Ohm as “runtime”.
“ Main Console ”
(110 ÷ 130 Ohm), the CAN line is broken or, the To resume the unit
CPU
“Collimator side” terminator is not mounted (see functionalities is
appendix 02). necessary a FSE
❖ In case the measured impedance is less than 45 Ohm, “visit”.


disabled.
CAN timeout If a motion (any one) it
“in-room” console This error check it is done at was running, that
Switch Off the unit and measure, on Console Control card
02 08 00064 CPU to every “unit power ON” as well motion is stopped.
(see the layout on the above page 158):
“ Main Console ” as “runtime”.
CPU To resume the unit
a) The impedance between the pin 9 (Can_H) and pin 8
functionalities is
(CAN_GND) of CN1036.
necessary a FSE
b) The impedance between the pin 10 (Can_L) and pin 8
“visit”.
(CAN_GND) of CN1036.

than 1 Megaohm.
➢ In case the impedance is lower of 1 Megaohm, there is a

(CAN line) problem on the cable (insulation) and/or on
CPU card(s). ( see appendix 04 )

necessary to change the “Remote Keyboard” CPU card.

System
Response
At the power ON, the “in-room” Console (ARM) CPU check

the consistency of the data stored in the EEprom
(calibration) memory.
In case of error, the CPU it loads some default values and
the error code is generated.
• If this is a new installation of the “in-room” Console

CPU card (“in-room” Console Control/Interface and/or
ARM CPU), please to re-calibrate the Console
parameters ad described on the service manual - code In case of this error
5793727-1EN. the unit functions are
EEprom Init If the ARM CPU module it was also changed, before the disabled.
(load default) above recalibration, it is necessary to load on it the same
02 08 00070 every “unit power ON”.
“in-room” console release of firmware it is already installed on the other To resume the full
CPU CPUs (see service manual - code 5793727-1EN). unit functionalities is
necessary a FSE
❖ If this error is displayed on an “already running” unit, “visit”.
please to consider to change the “in-room” Console
Control card and/or the related “ARM CPU” module.

"Warning messages". These messages are “automatically reset” when the cause of the warning is removed/cleared.
System
Response
As by FSE command, on the “T” CPU EEprom are now

This warning check it is done
loaded the “default calibration parameters”
at every “unit power ON”.
The above operation could be done:
Please to take care in
following this warning the
• By a dip-switch located on the ”T” CPU card
parameters are not the
• By a direct command, while in maintenance mode.
correct calibration ones, but To resume the full
“T” CPU (Clisis Main)
only some “default” that unit functionalities is
02 20 00000 Default parameters At this proposal, see the service manual - code 5793727-1EN.
enable the FSE to “really” necessary a FSE
LOADED.
calibrate the unit. calibration.
Please to take care that after the above operation the
complete “T” CPU (parameters) calibration must be done.
“Running” the unit with (only)
At this proposal, see the service manual - code 5793727-1EN.
the default parameters,
without a real calibration,
❖ If this warning is displayed, without reasons, on an
could bring to some “not
“already running” unit, please to consider to execute
desired” behaviors.
the troubleshooting of the error 02 04 00016. ➔

System
Response
This “service” setup, it was designed to check the proper X-

Ray sequence ONLY when the unit is in production (without
generator connected). While the unit is installed, the
“generator simulation” must be set as “OFF”.
To resume the full
“X-Ray Generator” The setting is made by a dip-switch located on the ”T” CPU card
This warning check it is done unit functionality is
02 20 00001 feedback signals (Clisis Main card). At this proposal, see the service manual -
at every “unit power ON”. necessary a FSE
simulation code 5793727-1EN
“intervention”.
❖ If this warning is displayed, without reasons (and with
the above mentioned switch “OFF”), on an “already
running” unit, please to consider to execute the
troubleshooting of the error 02 04 00016. ➔

System
Response
As by FSE command, on the “Collimator” CPU Eeprom are This warning check it is done
now loaded the “default calibration parameters” at every “unit power ON”.
The above operation could be done only by a direct command, Please to take care in
while in maintenance mode. following this warning the
parameters are not the
At this proposal, see the service manual - code 5793727-1EN. correct calibration ones, but To resume the full
only some “default” that unit functionalities is
02 20 00002 Default parameters
Please to take care that after the above operation the enable the FSE to “really” necessary a FSE
LOADED.
complete “Collimator” CPU (parameters) calibration must be calibrate the unit. calibration.
done.
At this proposal, see the service manual - code 5793727-1EN. “Running” the unit with (only)
the default parameters,
❖ If this warning is displayed, without reasons, on an without a real calibration,
“already running” unit, please to consider to execute could bring to some “not
the troubleshooting of the error 02 06 00004. ➔ desired” behaviors.

System
Response
As by FSE command, on the “SFD” CPU EEprom are now

loaded the “default calibration parameters”
The above operation could be done:
• By a dip-switch located on the ”SFD” CPU card

• By a direct command, while in maintenance mode.
To resume the full
“SFD” CPU
This warning check it is done unit functionality is
02 20 00003 Default parameters At this proposal, see the service manual - code 5793727-1EN.
at every “unit power ON”. necessary a FSE
LOADED.
“intervention”.
Please to take care that, as no further calibrations are needed,
after an initial setup, no more operation are to be done by the
operator / FSE.
❖ If this warning is displayed, without reasons, on an

“already running” unit, please to consider to execute

System
Response
The operator “request” a Fluoroscopy but the X-Ray tube X-Ray are not emitted
is not aligned on the center of the SFD/Detector. and the present
warning is displayed.
Please to re-center/re-align the X-Ray tube on the
Requested
receptor (SFD center / Detector center) before to “ask A FSE “intervention” is
Fluoroscopy This warning check it is done
02 20 00007 again” for a Fluoroscopy. necessary if this
X-Ray tube “runtime”.
This message is an auto-reset message ➔ The message warning is generated
“not aligned on SFD”
disappear when the fluoroscopy command is released. with the X-Ray tube
already aligned on the
❖ If this warning is displayed also when the X-Ray tube receptor (SFD center /
is centered, a FSE calling / intervention is needed. Detector center).
The unit is executing (as by operator request) the “Patient

Loading (motion) sequence”.
During this phase the other motions are disabled.
This warning it is cleared when the sequence is
terminated or, if the operator aborts the patient loading
function. During “Patient
Patient Loading This warning check it is done Loading (motion)
02 20 00008
sequence in “Run” ❖ If this warning is displayed and the sequence couldn’t “runtime”. sequence” the other
be terminated, is necessary (by a FSE) to check which motions are disabled.
is the motion that “lock” it.
❖ If this warning is displayed, without reasons (and

without that the function is selected), please to execute

System
Response
The unit terminated all the motion needed to arrive in the

“Patient Loading position”.
While in “Patient Loading position”, for safety reasons
(operator …. are around the unit), all the main motions are While in “Patient
Patient Loading disabled. Loading position” all
02 20 00009 Position reached To re-enable the unit working, the operator must use / the main motions are
“runtime”.
All motions “OFF” touch the related button (see service and/or user manual). disabled.
❖ If this warning is displayed, without reasons (and

without that the function is selected), please to execute
The foot safety sensor mounted on the table-top right

support arm is “Active”.
The “foot safety” sensor, while activated, it disables the
tilting / elevation motions toward the floor.
If the sensor is
This safety is implemented to protect the operator and/or
Foot safety activated, the only
patient foot to be “catch” between the table-top edge and This warning check it is done
02 20 00010 (tabletop edge) possibility is to tilt the
the floor. “runtime”.
“Active” table toward the
If the sensor is activated, the only possibility is to tilt the
horizontal position.
table toward the horizontal position.
❖ If this warning is displayed without reasons, a FSE

calling / intervention is needed.

System
Response
The Compressor paddle/cone is “pressing” on the patient.
For safety reasons, all the motions that are in relation to

If the sensor is
the PatientCompressor relative positions are disabled.
activated, the only
Compressor safety To re-enable the unit working, the operator must retract This warning check it is done
02 20 00011 possibility is to
“Active” the compressor (have to move away the compressor from the “runtime”.
“retract” the
patient).
compressor.
The Ceiling Suspension (CTM) unit is not in parking

position.
The “CTM parking” input (Clisis Interface card CN 172, pin

9 – 10) is “sensed” activated (input open). This safety it is
implemented to “limit” the CTM – Tilting table collisions. If this input is
CTM
This warning check it is done activated, all the main
02 20 00012 (Ceiling Suspension)
If the “CTM parking” input is “activated”, the main “runtime”. motions of the tilting
“in field”
motions of the tilting table are disabled. table are disabled. .
To re-enable the unit full motions, the operator must
move the CTM on its parking position.


System
Response
The Film Changer Unit (PUCK) is a very old accessory that

is no more used in X-Ray rooms.
Anyway, as by compatibility issues with old systems, the
A FSE “intervention” is
PUCK related input on the Clisis Interface card is already
This warning check it is done necessary if this
02 20 00013 (Film Changer unit) present (and is checked).
“runtime”. warning is generated
“Not in Parking”
on a Discovery system
❖ If this warning is displayed on a Discovery systems,
(without reasons) a FSE calling / intervention is
needed.
The Compressor paddle/cone is “Not in parking position”.
For safety reasons, all the speeds of the motions that are
If the compressor is
in relation to the PatientCompressor relative positions
not parked, some
Compressor are slow down. Also the incidence angle motion is limited.
This warning check it is done motions are limited as
02 20 00014 “in field”
“runtime”. well as some other
(Not in parking) To re-enable the normal unit working, the operator must
are running at slow
retract the compressor till the parking position.
speed.

System
Response
X-Ray tube is not aligned on the center of the

SFD/Detector.
This is a warning, informing the operator that he/she can

Exposure on the SFD
do only X-Ray on a Cassette/ External detector, in Direct
X-Ray tube This warning is a “runtime” internal detector as
02 20 00015 mode.
“not aligned on SFD” one. well as Fluoroscopy
The exposure on the SFD assembly (internal detector) is
are disabled if this
disabled as well as the Fluoroscopy.
warning is displayed.
❖ If this warning is displayed also when the X-Ray tube
is centered, a FSE calling / intervention is needed.
In case the external

The unit is provided with some inputs (on the Clisis
sensor is activated,
Interface card) for external “near collision” sensing devices.
the firmware
limits/stop the
In case the external sensor is activated, the firmware
movements that can
limits/stop the movements that can cause the collision
cause the collision.
The external (obviously, only the motion direction toward the collision
“Right Wall” point is limited). This warning check it is done
02 20 00016 Some led on the
collision sensor “runtime”.
control desk indicate
is activated. Some led on the control desk indicate the “available”
the “available”
motions / the motions that the operator can do to exit
motions / the motions
from this warning situation.
that the operator can
do to exit from this
warning situation.

System
Response
The external
“Left Wall” In case the external
02 20 00017 The unit is provided with some inputs (on the Clisis
collision sensor sensor is activated,
Interface card) for external “near collision” sensing devices.
is activated. the firmware
limits/stop the
In case the external sensor is activated, the firmware
movements that can
cause the collision.
(obviously, only the motion direction toward the collision
point is limited). This warning check it is done
Some led on the
“runtime”.
Some led on the control desk indicate the “available”
the “available”
The external do to exit from this
“Ceiling” ❖ If this warning is displayed without reasons, a FSE
02 20 00018 warning situation.
collision sensor calling / intervention is needed.
is activated.

System
Response
“Right Wall”
02 20 00019 Anti-collision limit
(firmware limit)
The firmware of the unit is designed to avoid collision
In case the “firmware
with the room walls and the room ceiling.
calculated position”
reports a collision
In case the “calculated positions” of the different unit
risk, the movement
parts/edges is “too near” to the ceiling and/or the room’s
that could cause the
walls (the room’s limits are set by the FSE during
risk are
installation), the firmware limits/stop the movements
limited/stopped.
“Left Wall” that can cause the collision (obviously, only the motion
02 20 00020 Anti-collision limit direction toward the collision point is limited).
“runtime”. Some led on the
(firmware limit)
the “available”
❖ If this warning is displayed without “visible” reasons,
warning situation.
a FSE calling / intervention is needed.
“Ceiling”
(firmware limit)

System
Response
The unit is provided with a micro-switch that detects that

the Tomo-Bar has reached its maximum extension (due to
FFD and Incidence related positions).
In case of activation of this limit, it will be impossible to
further increase the Focal Distance (SID) and/or to
Tomo-Bar
increase the incidence angle.
(out) Limit
02 20 00022 In case of activation
microswitch
Some led on the control desk indicate the “available” of this limit, it will be
is activated
motions / the motions that the operator can do to exit impossible to further
from this warning situation. increase the Focal
Distance (SID) and/or
❖ If this warning is displayed without reasons, a FSE to increase the
calling / intervention is needed. incidence angle.
“runtime”.
Some led on the
The firmware of the unit is designed to limit the Tomo-Bar control desk indicate
maximum extension. the “available”
In case this limit is reached, it will be impossible to further motions / the motions
increase the Focal Distance (SID) and/or to increase the that the operator can
incidence angle. do to exit from this
Tomo-Bar warning situation.
02 20 00023 (out) Limit
(firmware limit)


System
Response
The operator “selected” a Tomography technique but the This warning check it is done Tomography could
Column and/or the SFD/Detector are outside the area that “runtime”, if Tomography is not be executed if this
allows the full Tomography sweep. selected. warning is displayed.
Please to “move” the Column and/or the SFD/Detector A FSE “intervention” is Some led on the
“Out of Tomo area”
inside the tomography area. necessary if this warning is control desk indicate
02 20 00024 Working area limit
Some led on the control desk indicate the “available” generated without the the “available”
(firmware limit)
motions / the motions that the operator can do to re-enter selection of the Tomography motions / the motions
in the tomography area. tech, or if, with Tomography that the operator can
selected, the Column and the do to re-enter in the
❖ If this warning is displayed without reasons, a FSE SFD / Detector are inside the tomography area.
calling / intervention is needed. normal Tomography area.
In case the “firmware

The firmware of the unit is designed to avoid collision
calculated position”
with the room floor.
reports a collision
risk, the movement
In case the “calculated positions” of the different unit
that could cause the
parts/edges is “too near” to the floor, the firmware
risk are
“Floor” limited/stopped.
(obviously, only the motion direction toward the collision This warning check it is done
point is limited). “runtime”.
(firmware limit) Some led on the
the “available”
❖ If this warning is displayed without “visible” reasons,
a FSE calling / intervention is needed.
warning situation.

System
Response
The ”operator catch” safety sensor(s) mounted on the

table main beam and/or the light-beam sensor, mounted
on the table -top right support arm, is/are “Active”.
The above sensor(s) are provided to prevent that the operator, If the sensor is
while on the unit (back) side of the table- top, it will be “catch” activated, the only
between the TBT edge and the main scanning beam or, that possibility is to move
“operator safety” (s)he will be “catch” between the table-top support arm and the TBT (lateral
02 20 00026 (operator “catch”) the SFD/detector assembly side. motion) far from the
“runtime”.
sensor(s) “Active” If the sensor is activated, the only possible motion is to table main scanning
move the TBT laterally in the direction “out” (to move far beam ➔ to increase
from the main scanning beam) ➔ to increase the area the area where is
where is located the operator. located the operator.


System
Response
The operator selected a Tomography or a Stitching exam, but

the FFD/SID is not correct to do that. This warning check it is done
“runtime”, if Tomography or
It is requested to the operator to adjust the FFD/SID distance. This Stitching is selected.
“wrong FFD/SID” Tomography and/or
operation could be done by the operator using the corresponding
for Tomography Stitching could not be
02 20 00027 commands or, in alternative, by pressing the “Preparation” button (in A FSE “intervention” is
and/or Stitching executed if this
this last case, the FFD/SID adjusting is done automatically by the necessary if this warning is
(firmware limit) warning is displayed.
firmware). generated without the
selection of the Tomography
❖ If this warning is displayed without reasons, a FSE calling / and/or Stitching tech.
intervention is needed.
The “T” CPU doesn’t receive the CAN message informing it

Warning: about the Collimator status.
This error check it is done It is necessary a FSE
02 20 00028 CAN message lost
“runtime”. troubleshooting.
from Collimator CPU • Execute the same troubleshooting
of error 02-04-00012 ➔
The “T” CPU doesn’t receive, from the SFD CPU, the CAN
For safety related
message informing about the status of the “operator Catch”
issue, in case of this
sensors. This information is “a must” to avoid that, eventually,
“Operator catch” problem, the unit “ask
an operator is Catch between the TBT edge and the main
CAN message lost This error check it is done to move” the TBT
02 20 00029 scanning beam or, that (s)he is “catch” between the table-top
(coming from SFD “runtime”. completely OUT.
support arm and the SFD/detector assembly side.
CPU).
troubleshooting.
of error 02-04-00012 ➔

System
Response
SW14 on the “T” CPU card is used to bypass unit safeties. The operator can
Normally all the position of this Dip Switch must be “OFF”. continue to use the
Warning: unit, but she/he must
Position # 7 of The unit “detected” that the position #7 of SW14 is “ON”. pay attention during
02 20 00030 DipSwitch SW14 Please to check the problem and to set the switch “OFF”. the motions (safety
“runtime”.
on the “T” CPU card bypassed).
is “ON” ❖ If this warning is displayed without reasons, it is
necessary to change the “T” CPU card. See “Note” on It is necessary a FSE
the following. troubleshooting.
“runtime”.
5793727-1EN).

System
Response
“runtime”.
“runtime”.
5793727-1EN).

System
Response
“runtime”.
“runtime”.
5793727-1EN).

System
Response
“runtime”.
5793727-1EN).

Errors & Warning “Stitching”
System
Response
DLL tries to “activate” the “Stitching” function, but the

Table refuses that command.
➢ Please to check if another technique (Tomography/ This error check it is done

“Stitching”
02 50 00000 Tomosynthesis) is still enabled when the Stitching “runtime”, when the Stitching
Activation Failed
procedure is selected. tech/procedure is selected.
A FSE “intervention” is
➢ Please to check the link / communication between
necessary.
the Table and the digital unit.
➢ Ask for producer support and/or suggestions.
This is probably a
firmware related fault.
This error informs that the Scanning drivers found a fault In case of this error it
that forces the abort of the stitching sequence. is suggested to re-
“Stitching” cycle the Table power
02 50 00001 “runtime”, during Stitching
Aborted from Table ➢ Please to troubleshoot the drivers error codes that supply.
tech/procedure.
are generated together with this error In case also this
➢ Ask for producer support and/or suggestions. operation doesn’t
solve the issue, please
to contact / inform the
unit producer.
DLL “ask” the table for “Stitching” feasibility, but the
Table doesn’t reply.
No response for This error check it is done
02 50 00002 stitching feasibility “runtime”, during Stitching
request tech/procedure.

System
Response
This error informs that the Scanning drivers are not able
to correctly position the Column and/or the SFD during a
Table positioning stitching sequence.
failed
tech/procedure.
➢ Please to troubleshoot the drivers error codes that
are generated together with this error
DLL “ask” the table to move to the “next position”, but the A FSE “intervention” is
Table doesn’t reply. necessary.
No response for This error check it is done
02 50 00004 table position “runtime”, during Stitching This is probably a
command tech/procedure. firmware related fault.
In case of this error it
is suggested to re-
cycle the Table power
DLL “ask” the table to “exit from Stitching”, but the Table supply.
doesn’t execute the command). In case also this
“Stitching” operation doesn’t
De-activation Failed ➢ Please to check the link / communication between solve the issue, please
tech/procedure.
the Table and the digital unit. to contact / inform the
➢ Ask for producer support and/or suggestions. unit producer.
02 50 00006
The Table informs the DLL that is not possible to do the
“Stitching” as by the actual Column / SFD positions or as This “warning” check it is
Stitching not
02 50 00007 by the risk of collision with the Ceiling. done “runtime”, during
feasible
Stitching tech/procedure.
➢ Please to position properly Column and SFD.
02 50 00008

Errors & Warning “Tomography”
System
Response
DLL tries to “activate” the “Tomography” function, but the

Table refuses that command.
➢ Please to check if another technique (Stitching /
“Tomography” “runtime”, when the
02 52 00000 Tomosynthesis) is still enabled when the Stitching A FSE “intervention” is
Activation Failed Tomography tech/procedure
procedure is selected. necessary.
is selected.
the Table and the digital unit. This is probably a
➢ Ask for producer support and/or suggestions. firmware related fault.

is suggested to re-
DLL “ask” the table to “exit from Tomography”, but the
Table doesn’t execute the command).
This error check it is done supply.
“Tomography”
02 52 00001 “runtime”, during Tomography In case also this
De-activation Failed ➢ Please to check the link / communication between
tech/procedure. operation doesn’t
unit producer.
The table “exit from Tomography” without any command. This error check it is done
Table out of
02 52 00002 “runtime”, during Tomography
Tomography
➢ Ask for producer support and/or suggestions. tech/procedure.

Errors & Warning “TomoSynthesis”
System
Response
DLL tries to “activate” the “TomoSynthesis” function, but

the Table refuses that command.
➢ Please to check if another technique (Stitching /
“TomoSynthesis” “runtime”, when the
02 53 00000 Tomography) is still enabled when the Stitching A FSE “intervention” is
Activation Failed TomoSynthesis
procedure is selected. necessary.
tech/procedure is selected.
the Table and the digital unit. This is probably a
➢ Ask for producer support and/or suggestions. firmware related fault.

is suggested to re-
DLL “ask” the table to “exit from TomoSynthesis”, but the
Table doesn’t execute the command). This error check it is done
supply.
“TomoSynthesis” “runtime”, during
02 53 00001 In case also this
De-activation Failed ➢ Please to check the link / communication between TomoSynthesis
operation doesn’t
the Table and the digital unit. tech/procedure.
unit producer.
The table “exit from TomoSynthesis” without any
command.
Table out of “runtime”, during
02 53 00002
TomoSynthesis TomoSynthesis
tech/procedure.

Appendix 01 – CAN_GND line problem (“cut” or in short circuit to GND)

To troubleshoot the CAN line, please to take as reference the following connection diagram.

The CAN line on the Discovery unit is grounded only on the “T” CPU card (Clisis Main card).
In case of the system is provided of the “in-room” control desk, the test must be executed in two steps:
I. Test without the “in-room” control desk

II. Test of the “in-room” control desk and its related wirings
❖ Step I. Test without the “in-room” control desk
With the unit “OFF”
• On the “T” CPU card (Clisis Main), locate the jumper SW4.
• Disconnect CN125 and CN128.
• In case of system provided of the “in-room” control desk, disconnect CN134.
• With a multimeter, measure the impedance between GND (metal plate) and pin 2
of SW2.
➢ If the measured impedance is about infinite (greater than 1 Megaohm),

check that on the Clisis Interface Board, the connector CN144 (Faston) is
properly connected to ground.
In positive case, Change the “T” CPU card (Clisis Main).

After this operation, please to verify the correct setup of the card jumpers, as displayed on the service manual (code 5793727-1EN).
By this changing, to resume the unit working, it will be necessary to load on the CPU card the same software release loaded on the other unit’s
CPUs and, also, to re-calibrate all the parameters related to the functions are controlled by it.
Related instructions are provided before the end of this procedure.
Restart this procedure (Appendix 01) from the beginning.
• In case of system provided of the “in-room” control desk, Re-connect CN134.
• Re-connect CN125, CN128 and, jump to the point A). ➔

A) Console branch test:
• Open the main Console and, on the “Console Control/Interface card”, locate the
connector CN1036 (see the image on the right).
• With a multimeter, measure the impedance between GND node of the

console (metal plate, on the internal back side of the console) and the pin #8 Can_H
(Can_GND) of the connector CN1036 (see the image on the right). Can_L
➢ If the measured impedance is about infinite (greater than 1Megaohm),

jump to the point A1 (on next page) ➔.
Can_GND
• The measured impedance is about zero (less than 10 Ohm).

On the “T” CPU card (Clisis Main), Disconnect CN128.
• Measure (again) the impedance between GND node of the

console (metal plate, on the internal back side of the console) and
the pin #8 (Can_GND) of the connector CN1036 (see the image on
the right).
➢ If the measured impedance is about infinite (greater than 1Megaohm), jump to the point B) - Collimator branch test ➔.
• Re-connect CN128 and, on the back side of the control desk, Disconnect CN1005.

• Measure (again) the impedance between the pin #8 (Can_GND) of the connector CN1036 and the GND node of the console (metal plate, on the
internal back side of the console).
➢ If the measured impedance is about infinite (greater than 1 Megaohm), change the cable connecting CN1005  CN128 (console cable).
After this operation, re-connect all the disconnected cables and jump back to the point A) ➔
➢ If the measured impedance is about zero (less than 10 Ohm), change the “Console Control/Interface” card.
If together this card it was changed also the (ARM) CPU card module, to resume the unit working it will be necessary to load on it the same
software release loaded on the other unit’s CPUs. Anyway, by the Console Control/Interface card changing it will be also necessary to re-calibrate
all the parameters related to the functions are controlled by it. Related instructions are provided before the end of this procedure.
Jump back to the point A) ➔.
A1) CAN GND line is “cut” on the console branch.
• On the “T” CPU card (Clisis Main), disconnect CN128
• Measure the impedance between GND (metal plate) and pin 16 of the card connector CN128.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), Change the “T” CPU card (Clisis Main).
Executed all on the above, restart this procedure (Appendix 01) from the beginning.
• Re-connect CN128.
• On the back side of the main control desk, Disconnect CN1005.

• Measure the impedance between the pin 16 of the cable connector CN1005 and the GND node of the console (metal plate, on the bottom-left,
inside the console).
➢ If the measured impedance is about infinite (greater than 1 Megaohm), change the cable connecting CN1005  CN128 (console cable).
After this operation, re-connect all the disconnected cables and jump back to the point A) ➔.
all the parameters related to the functions are controlled by it.
Jump back to the point A) ➔.
B) Collimator Branch:
• Disconnect (on the back side of the Collimator head) the cable connector CN601.
• With a multimeter, measure the impedance between pin 10 and pin 15 of the cable connector CN601.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), jump to the point B1 ➔.
• The measured impedance is about zero (less than 10 Ohm), on the “T” CPU card (Clisis Main), Disconnect CN125.
• Measure (again) the impedance between pin 10 and pin 15 of the cable connector CN601.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), jump to the point B2) - Collimator test ➔.
• On the SFD CPU card, Disconnect CN412.

➢ If the measured impedance is about infinite (greater than 1 Megaohm), change the cable connecting CN412#1  CN125.
After this operation, re-connect all the disconnected cables and jump back to the point B) ➔.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), Chance the “SFD” CPU card.
CPUs and, in case, to re-calibrate all the parameters related to the functions are controlled by it.
Executed all on the above, jump back to the point B) ➔.
• Re-connect CN411
• On the Tube Stand Control card, Disconnect CN509.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), change the cable connecting CN411  CN509.
• Re-connect CN509 (on Tube Stand Control card).

• Measure the impedance between pin 10 and pin 15 of CN510 (on Tube Stand Control card).
➢ If the measured impedance is about infinite (greater than 1 Megaohm), change the cable connecting CN410  CN601 (Collimator Cable).
➢ If the measured impedance is about zero (less than 10 Ohm), change the “Tube Stand Control” card.
Executed the above, jump back to the point B) ➔.
B1) CAN GND line is “cut” on the collimator branch.
• On the “T” CPU card (Clisis Main), disconnect CN125.
Jump back to the point B ➔.
• Re-connect CN125 (on “T” CPU card).
• Measure the impedance between GND node of the SFD (metal plate, inside the SFD assembly) and the pin 3 of the cable connector CN412.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), change the cable connecting CN125  CN412 (UTP cable).

• Measure the impedance between GND node of the SFD (metal plate, inside the SFD assembly) and the pin 3 or CN411 (card connector).
➢ If the measured impedance is about infinite (greater than 1 Megaohm), Chance the “SFD” CPU card.
CPUs and, in case, to re-calibrate all the parameters related to the functions are controlled by it.
Jump back to the point B) ➔.
• Measure the impedance between GND (metal plate on the column, near the Tube Stand Control card) and pin 3 of the cable connector CN509.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), change the cable connecting CN411  CN509 (UTP cable).
• Measure the impedance between GND (metal plate on the column, near the Tube Stand Control card) and pin 15 of CN510 (card connector).
➢ If the measured impedance is about infinite (greater than 1 Megaohm), change the “Tube Stand Control” card.
Executed the above, re-connect all the disconnected cables and jump back to the point B) ➔.
➢ If the measured impedance is about zero (less than 10 Ohm), change the cable connecting CN510  CN601 (Collimator Cable).

B2) Collimator CAN GND test.
• Re-connect CN125 and CN601
• Open the collimator head to access the Collimator CPU card.
• On the Collimator CPU, Measure the impedance between the Anode of D11 (or pin 5
of U21) and GND (Faston connector).
➢ If the measured impedance is about infinite (greater than 1 Megaohm), jump to

the point B3). ➔
• On the “T” CPU card (Clisis Main), Disconnect CN125.
• Measure (again) the impedance between the Anode of D11 and GND (Faston connector).
➢ If the measured impedance is about infinite (greater than 1 Megaohm), jump to

the point C) ➔
• Re-connect CN125 (on the “T” CPU card).
• On the Collimator CPU card, Disconnect CN16 and measure the impedance between GND (Faston
connector) and pin 14 of the cable connector CN16.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), change the cable
connecting CN16  CN601 (inside collimator head).
➢ If the measured impedance is about zero (less than 10 Ohm), Change the Collimator CPU card.
Re-connect all the disconnected cables and jump back to the point B) ➔.

B3) Collimator internal CAN GND test
• On the Collimator CPU card, Disconnect CN16
• On the Collimator CPU card, Measure the impedance between the Anode of D11 (or pin
5 of U21) and pin 14 of CN16.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), jump to the
point B4). ➔
• On the Collimator CPU card, Measure the impedance between pin 5 of CN16 and GND
(Faston connector).
➢ If the measured impedance is about infinite (greater than 1 Megaohm), jump to the
point B4). ➔
• Change the cable connecting CN16  CN601 (inside collimator head).

After this operation, re-connect all the disconnected cables and jump back to the
point B) ➔.
B4) Change the Collimator CPU card.

After this operation, please to verify the correct setup of the card jumpers, as displayed on the
service manual (code 5793727-1EN).
Executed all on the above, re-connect all the disconnected cables and jump back to the point B) ➔.
❖ Step II. Test of the “in-room” control desk and its related wirings
C) “in-room” Console branch test:
➢ If the system is not provided of the “in-room” console, jump to the point D) ➔.

• Open the “in-room” Console and, on its “Console Control/Interface card”, locate
the connector CN1036 (see the image on the right).
• With a multimeter, measure the impedance between GND node of the console
(metal plate, on the internal back side of the console) and the pin #8 (Can_GND)
of the connector CN1036 (see the image on the right). Can_H
Can_L
➢ If the measured impedance is about infinite (greater than 1 Megaohm),
jump to the point C1 ➔. (on next page)
• On the “T” CPU card (Clisis Main), Disconnect CN134. Can_GND
• Measure (again) the impedance between GND node of the

console (metal plate, on the internal back side of the console) and
the pin #8 (Can_GND) of the connector CN1036 (see the image
on the right).
➢ If the measured impedance is about infinite (greater than

1 Megaohm), re-connect CN134 and jump to the point D) ➔.
• Re-connect CN134 and, on the back side of the “in-room” control desk, Disconnect CN1005.
• Measure (again) the impedance between GND node of the console (metal plate, on the internal back side of the console) and the pin #8 (Can_GND)
of the connector CN1036.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), change the cable connecting CN1005  CN134 (“in-room console”
cable). After this operation, re-connect all the disconnected cables and jump back to the point C) ➔
Jump back to the point C) ➔.

C1) CAN GND line is “cut” on the “in-room” console branch.
• On the “T” CPU card (Clisis Main), disconnect CN134.
Restart this procedure (Appendix 01) from the beginning.
• On the back side of the control desk, Disconnect CN1005.
• Measure the impedance between GND node of the console (metal plate, on the bottom-left, inside the console) and the pin 16 of the cable
connector CN1005.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), change the cable connecting CN1005  CN134 (“in-room” console
cable). After this operation, re-connect all the disconnected cables and jump back to the point C) ➔.
Jump back to the point C) ➔.

D) All the (CAN GND) test are passed.
• Check that all cables are properly connected and verify that the jumper setting on the different cards is exactly the one displayed on the
CAN connection diagram on the beginning of this appendix.
Before to exit from this Procedure/Appendix and, by this, to Check if the unit is properly working are to consider the actions we made on the
previous steps.
In particular, we have to consider if we have changed one (or more) CPU cards. In affirmative case, before to restoring the correct unit
functionality we must load on those CPU cards a software of the same release/version as the one is installed on the unit before our
“maintenance” (the one was on the CPU card that we changed) as well as we must re-calibrate the parameters related to the table’s functions
controlled by that CPU.
• Verify that all the cables and connectors are properly re-connected.
➢ If the “T” CPU card (Clisis Main) it was changed.
• According to the unit Service manual (code 5793727-1EN), Load on the “T” CPU the same release/version as the one is (was originally)
installed on the unit before.
• According to the figure on the unit Service manual (code 5793727-1EN), Verify the correct Jumper setting.
• According to the unit Service manual (code 5793727-1EN), Re-configure the “options” of the functions controlled by the “T” CPU card and
Re-calibrate all the parameters related to those functions.
➢ If the “Collimator” CPU card it was changed.
• According to the unit Service manual (code 5793727-1EN), Load on the “Collimator” CPU the same release/version as the one is (was
originally) installed on the unit before.
• According to the unit Service manual (code 5793727-1EN), Re-configure and re-calibrate the parameters related to the functions
controlled by the Collimator CPU card.

➢ If the “SFD” CPU card it was changed.
• According to the unit Service manual (code 5793727-1EN), Load on the “SFD” CPU the same release/version as the one is (was originally)
• According to the unit Service manual (code 5793727-1EN), Load (on it) its default parameters.
➢ If, inside the main control desk, the “Console Control/Interface” card and/or the “ARM” CPU card it was changed.
➢ If, it was changed (also) the “ARM” CPU card, according to the unit Service manual (code 5793727-1EN), Load on the “ARM” CPU the same
release/version as the one is (was originally) installed on the unit before.
• According to the figures on the unit Service manual (code 5793727-1EN), Verify the correct Jumper setting.
• According to the unit Service manual (code 5793727-1EN), Re-calibrate the parameters related to the functions controlled by the “main”
Console.
➢ If, inside the “in-room” control desk (if provided with the system), the “Console Control/Interface” card and/or the “ARM” CPU card it was
changed.
• According to the unit Service manual (code 5793727-1EN), Re-calibrate the parameters related to the functions controlled by the “in-
room” Console.
• Exit this procedure/Appendix and check for the unit proper working.

Appendix 02 – Broken (or not properly terminated) Can line


Preliminary:
The nominal value of the CAN line impedance, measured between the CAN H and the CAN L lines, is 60 Ohm (or 180 Ohm, if measured on an
“intermediary” CPU terminator jumper).
In case of, considering the component tolerance and the measuring tool error, the measured impedance (with the unit “OFF”) is bigger of 70 Ohm
(or bigger than 190 Ohm, if measured between the two pin of an “intermediary” CPU terminator jumper) we are in presence of one of the
following cases:
o The CAN line is, somewhere, interrupted.
o The CAN line is not properly terminated on one or both sides.
❖ To troubleshoot the above situation it is necessary to do some tests and measuring on the physical line. At this proposal, please to take as
reference the connection diagram of the previous page.
❖ Also if is not a must, a short UTP (not crossed) patch cable could be helpful to do some of the tests listed on the following points.


Please to locate the two jumpers JP1 and JP2 on the Clisis Main card (“T” CPU card). Both of these
two jumpers are “closed” (jumpers are mounted).
Measure the impedance between JP1 and JP2 (without removing the jumpers).
➢ In case the measured value is 120 Ohm (+/- 10 Ohm), the line is somewhere
“cut” or, one of the two terminators is not mounted.
Go to point “A”. ➔
➢ In case the measured value is greater than 1 Megaohm (about infinite), the line is completely
not terminated or, it is “cut” on two (or more) points.
This case could be considered as a double (or multiple) “A.” problem.

As by the above, to troubleshoot this case, is necessary to iterate the “A.
troubleshooting” untill the measured impedance between the Jumpers
JP1 and JP2 (on the “T” CPU card), with the jumpers mounted, is 60 Ohm
(+/- 10 Ohm). Go to point “A”. ➔
➢ In case the measured value is 60 Ohm (+/- 10 Ohm), the line impedance it is
correct. It is only to verify that the “inserted” terminations are the correct ones.
Go to point “B”. ➔

A. The measured value between JP1 and JP2 is 120 Ohm (+/- 10 Ohm).
1. Remove the Jumpers JP1 and JP2 and Measure the impedance between
pin 2 of JP1 and pin 2 of JP2.
➢ If the measured impedance is about 120 Ohm (+/- 10 Ohm), the CAN line connection:
“T”  “main Console”  “Console Control/Interface card”  Console side
Terminator is correct.
Jump to point “2”. ➔
• On the “T” CPU card (Clisis Main card), Locate the Jumpers SW3.
➢ If the jumpers are not correctly mounted, set the correct configuration (displayed) and jump back to the point “1”. ➔
➢ If the jumpers are correctly mounted, AND the measured impedance is less than 100 Ohm there is a problem on:
Connection “T”  “Console”, and/or on the “Console Control/Interface card”, and/or on the “T” CPU card.
Jump to point “1a”. ➔
➢ If the jumpers are correctly mounted, AND the measured impedance is high, or about infinite (greater than 1 Megaohm) there
is a problem on the CAN line connection: “T”  “Console”  “Console Control/Interface card”  Console side Terminator.
Jump to point “1b”. ➔
1a. The measured impedance is less than 100 Ohm, there is a problem on:
Connection “T”  “Console”, and/or “Console Control/Interface card”, and/or “T” CPU card.
• Measure again the impedance between pin 2 of JP1 and pin 2 of JP2.
➢ If the measured impedance is not about infinite (is not greater than 1 Megaohm), Change the “T” CPU card (Clisis Main).
By this changing, to resume the unit working, it will be necessary to load on the CPU card the same software release loaded on the other
unit’s CPUs and, also, to re-calibrate all the parameters related to the functions are controlled by it.
Jump back to the point “1”. ➔
• Re-connect CN128 and, on the back side of the control desk, Disconnect CN1005.
• Open the Console and, on the “Console Control/Interface card”, locate the connector CN1036 (see the image on the right).
• With a multimeter, measure the impedance between Pin # 10

(Can_L) and the pin #9 (Can_H) of the connector CN1036 (see
the image on the right).
➢ If the measured impedance is about 120 Ohm (+/- 10 Ohm),

change the cable connecting CN1005  CN128 (console
cable).
Can_H
After this operation, re-connect all the disconnected cables
and jump back to the point “1”. ➔
➢ If the measured impedance is less than 100 Ohm change

the “Console Control/Interface” card. Can_L
After this operation, please to verify the correct setup of Can_GND
the card jumpers, as displayed on the service manual
(code 5793727-1EN).
If together this card it was changed also the (ARM) CPU card
module, to resume the unit working it will be necessary to
load on it the same software release loaded on the other
unit’s CPUs. Anyway, by the Console Control/Interface card
changing it will be also necessary to re-calibrate all the
parameters related to the functions are controlled by it.

1b. The measured impedance is about infinite (greater than 1 Megaohm) there is a problem on the CAN line connection:
“T”  “Console”  “Console Control/Interface card”  Console side Terminator.
• Check that the (main) Console side Terminator jumper SW4 (on the Console Control/Interface card) it is mounted (inserted).
➢ If the above Jumper it not mounted, please insert and jump back to the point “1”. ➔
• Disconnect CN1005 (on the console back side) and Measure the impedance
between pin 6 and pin 7 of CN1005 (console side).
➢ If the measured impedance is about infinite, change the “Console

Control/Interface” card.
After this operation, please to verify the correct setup of
the card jumpers, as displayed on the service manual (code Can_H
5793727-1EN).
If together this card it was changed also the (ARM) CPU card
module, to resume the unit working it will be necessary to
load on it the same software release loaded on the other
unit’s CPUs. Anyway, by the Console Control/Interface card Can_L
changing it will be also necessary to re-calibrate all the

Can_GND
• Disconnect CN128 (on the “T” CPU card), re-connect CN1005 (on the Console
back side) and measure the impedance between pin 6 and pin 7 of the cable
connector CN128 (on the cable, not on the card).
➢ If the measured impedance is about infinite, the cable CN128  CN1005 (console cable) is faulty so, change it, re-connect it on both
connectors and, jump back to the point “1”. ➔

2. On the “T” CPU card, Measure the impedance between pin 1 of JP1 and pin 1 of JP2.
➢ If the measured impedance is about 120 Ohm (+/- 10 Ohm), the CAN line connection
“T”  “SFD”  “Collimator”  Collimator side Terminator (on Collimator CPU), is
correct so, Remount JP1 and JP2 (on the “T” CPU card) and restart this procedure
(Appendix 02) from the beginning. ➔
➢ If the measured impedance is less than 100 Ohm there is a problem on:
Connection “T”  “SFD”  “Collimator”  Collimator side Terminator (on
Collimator CPU), and/or on the “T” CPU card, and/or on the “SFD” CPU card, and/or on
the “Column side” CPU card, and/or on the “Collimator” CPU card.
Jump to point “2a”. ➔
➢ If the measured impedance is about infinite (greater than 1 Megaohm) there is a problem
on the CAN line connection “T”  “SFD”  “Collimator”  Collimator side Terminator (on Collimator CPU).
Jump to point “2c”. ➔
2a. The measured impedance is less than 100 Ohm there is a problem on:
Connection “T”  “SFD”  “Collimator”  Collimator side Terminator (on Collimator CPU), and/or on the “T” CPU card, and/or on the “SFD”
CPU card, and/or on the “Column side” CPU card, and/or on the “Collimator” CPU card.
➢ If the measured impedance is about 60 Ohm (+/- 10 Ohm), please to check if a jumper is mounted on SW4 of the “SFD” CPU card.
In positive case, remove that jumper and go back to the point “2”. ➔
• Go to the collimator and Disconnect the cable from CN601 (on Collimator head back side connector).
• On the “T” CPU card, Measure again the impedance between pin 1 of JP1 and pin 1 of JP2.
➢ If the measured impedance is about infinite (greater than 1 Megaohm) the problem is inside the collimator so, reconnect the cable on
CN601 and jump to point “2b”. ➔

• Reconnect the cable on CN601 (Collimator head back side connector) and disconnect the cable from CN510
(on “Tube stand Control card”, located on the Column right side).
➢ If the measured impedance is about infinite (greater than 1 Megaohm), change the cable connecting
CN510  CN601 (collimator cable), reconnect it on both connectors and, jump back to the point “2”. ➔
• Reconnect the cable on CN510 and disconnect the cable from CN509.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), change Tube Stand Control card.
Reconnect all the connectors and, jump back to the point “2”. ➔
• Reconnect the cable on CN509 and disconnect the cable from CN411 of the “SFD” CPU card.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), change the
cable connecting CN509  CN411, reconnect it on both connectors and, jump
back to the point “2”. ➔
• Reconnect the cable on CN411 and disconnect the cable from CN412.

➢ If the measured impedance is about infinite (greater than 1 Megaohm), chance the “SFD” CPU card.
After this operation, please to verify the correct setup of the card jumpers, as displayed on the service manual (code 5793727-
1EN).
unit’s CPUs and, in case, to re-calibrate all the parameters related to the functions are controlled by it.
• Reconnect the cable on CN412 and disconnect the cable from CN125 of the “T” CPU card.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), chance the cable connecting CN509  CN411, reconnect it on
both connectors and, jump back to the point “2”. ➔
• Change the “T” CPU card (Clisis Main).

By this changing, to resume the unit working, it will be necessary to load on the CPU card the same
software release loaded on the other unit’s CPUs and, also, to re-calibrate all the parameters related to
the functions are controlled by it.
2b. The problem is inside the collimator.
• Open the collimator head and Disconnect the cable from CN16 (Collimator CPU).

➢ If the measured impedance is about infinite (greater than 1 Megaohm), chance the Collimator CPU card.
1EN).
Re-connect all the disconnected cables and jump back to the point “2” ➔
• Change the collimator internal cable connecting CN601 CN16, reconnect it on both connectors and, jump back to the point “2”. ➔
2c. If the measured impedance is about infinite (greater than 1 Megaohm) there is a problem on the
CAN line connection “T”  “SFD”  “Collimator”  Collimator side Terminator (on Collimator
CPU).
• Check the correct setup of SW1.3, SW1.4, SW1.5 and SW1.6 of the “T” CPU card
(Clisis Main card).
➢ If the jumpers are not correctly mounted, set the correct configuration and jump back to the
point 2. ➔
• Check, on the “T” CPU card (Clisis Main), the continuity from CN125 pin 1 and JP1 pin 1 as
well as the one between CN125 pin 2 and JP2 pin 1.
➢ In case one (or both) of the last two tests are not correct, Change the “T” CPU card (Clisis Main).
After this operation, please to verify the correct setup of the card jumpers, as displayed
on the service manual (code 5793727-1EN).
By this changing, to resume the unit working, it will be necessary to load on the CPU card the
same software release loaded on the other unit’s CPUs and, also, to re-calibrate all the
Restart now this procedure (Appendix 02) from the beginning. ➔

• Go to the SFD and, on the SFD CPU card measure the impedance between the
two pins of SW4.
➢ If the measured impedance is about infinite (greater than 1 Megaohm) there

is a problem on the CAN connection “SFD”  “Collimator”  Collimator
side Terminator (on Collimator CPU). Jump to the point “2d”. ➔
The measured impedance is 180 Ohm (+/- 10 Ohm). The fault is in the connection between the “T” CPU card (from CN125) and the SFD CPU card
(SW4 terminator).
• On the SFD CPU card, swap the two cables (RJ45) connected to CN412 and CN411 and measure again the impedance between the two
pins of SW4.
➢ If the measured impedance is about infinite (greater than 1 Megaohm) chance the “SFD” CPU card.
1EN).
➢ If the measured impedance is already 180 Ohm (+/- 10 Ohm), chance the cable connecting CN125 (“T” CPU)  CN412 (SFD CPU) and,
jump back to the point “2”. ➔

2d. There is a problem on the CAN connection “SFD”  “Collimator”  Collimator side Terminator (on Collimator CPU).
• On the SFD CPU card, swap the two cables (RJ45) connected to CN412 and CN411
and measure again the impedance between the two pins of SW4.
➢ If the measured impedance is about 180 Ohm (+/- 10 Ohm), chance the “SFD” CPU
card.
After this operation, please to verify the correct setup of the card jumpers, as
displayed on the service manual (code 5793727-1EN).
By this changing, to resume the unit working, it will be necessary to load on the CPU
card the same software release loaded on the other unit’s CPUs and, in case, to re-
calibrate all the parameters related to the functions are controlled by it.
• On the SFD CPU card, re-connect, on the correct connectors, the two RJ45 cables swapped as by the
previous test.
• Go to the collimator and check that the Collimator side Terminator jumper JMP2 (on Collimator CPU
card) it is mounted (inserted).
➢ If the jumper is not correctly mounted, set it and jump back to the point 2. ➔
• Disconnect the cable from CN16 (Collimator CPU) and measure the impedance between pin 13
and pin 15 of the card connector.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), Change the Collimator CPU
card, reconnect the cables and re-mount JP1 and JP2 on the “T” CPU card.
Re-connect all the disconnected cables and jump back to the point “2” ➔
• Reconnect the cable on CN16 (Collimator CPU) disconnect the cable from CN601 (on Collimator head back-side) and measure the
impedance between pin 7 and pin 8 of CN601 (on Collimator head back side connector).
➢ If the measured impedance is about infinite (greater than 1 Megaohm), change the CN16  CN601 cable (internal connection of the
collimator head).
Change the (internal) cable, reconnect it on both connectors and, jump back to the point 2. ➔
• Reconnect the cable on CN601 (Collimator head back side connector) disconnect the cable from CN601 (on
Collimator head back-side) and disconnect the cable from CN510 (on “Tube stand Control card”, located on the
Column right side).
• Measure, on the cable connector CN510 (on the cable coming from collimator), the impedance between
pin 7 and pin 8.
CN510  CN601 (collimator cable), reconnect it on both connectors and, jump back to the point 2. ➔
• Disconnect CN509 (on “Tube stand Control card”) and measure, on the “Tube stand Control card”:
Continuity between pin 1 of CN509 and pin 8 of CN510.
Continuity between pin 2 of CN509 and pin 7 of CN510.
➢ If one (or both) of the last two tests are not correct, Chance the “Tube Stand Control” card.
Reconnect all the connectors and, jump back to the point 2. ➔
➢ If both of the last two tests are correct, re-connect CN510, change the cable connecting CN510 
CN601 (collimator cable), reconnect it on both connectors and, jump back to the point 2. ➔

B. The measured value between JP1 and JP2 is 60 Ohm (+/- 10 Ohm).
The above value is the “correct one” about the impedance of the main path of the
unit (table) CAN line.
As this test is not considering the branch related to the “in-room” control desk,
other test procedures (that are on the following) will be needed to test that branch.
On this condition is only to verify that the jumper setting on the different cards is exactly
the one displayed on the CAN connection diagram of the beginning of this appendix.
In any case, a complete jumper setup configuration is also displayed on the figures/images on the unit service manual (code 5793727-1EN).
• Verify that the jumper setting on the different cards is exactly the one displayed on the CAN connection diagram of the beginning of this
appendix (a complete jumper setup configuration is also displayed on the figures of the unit service manual - code 5793727-1EN).
➢ If the Jumper setting it was not correct, set it correctly and restart this procedure (Appendix 02) from the beginning. ➔
➢ If the Jumper setting it was correct, jump to the point “C”. ➔
C. The unit CAN line “main path” impedance is correct; the test must continue with the “in-room” control desk branch, if present.
➢ If the System is not provided of the “in-room” console, jump to the point “D”. ➔
As because of the “in-room” console CAN branch it is enabled (connected) to the “main” CAN line only if the unit is powered, the following test
must be executed with the unit “ON”. Please to take care to don’t touch LIVE parts and to avoid to command unit motions.
As because of some bypass have to done on the following steps, some (new) errors will be generated and stored in the error log. Clearly those
error are not to be considered for the troubleshooting (ignore those errors).

WARNING
Some, few, of the test listed on the following part of this Troubleshooting require that the unit is Powered “ON”.
By this, the operator must take care to don’t touch “LIVE” parts and to avoid to command unit motions.
As by all on the above, any one of the operations listed on the following must be executed by fully trained FSEs.
1. To reduce to the minimum the risk for the operator/FSE, disable all the un-necessary powers as
listed on the following.
All the indicated Breaker & Fuses are located on the lower part of the unit main/power cabinet, as
visible on the two figures on the right.
To easily access to those Fuses & Breakers, it may be helpful to tilt (in horizontal) the plate
supporting both the Clisis Main (“T”) CPU and the Clisis Interface cards.
• Switch “OFF” the Breaker SW3 (Column scanning, SFD scanning and TBT longitudinal drivers main
power supply).
• Switch “OFF” the Breaker SW4 (Tilting and Elevation drivers main power supply).
• Disconnect, by “fully opening” its fuse holder, the Fuse F4 (TBT Lateral driver power supply).
• Disconnect, by “fully opening” their fuse holders, the Fuses F5 and F6 (SFD power supply).
• Disconnect, by “fully opening” its fuse holder, the Fuse F9 (Collimator power supply).
• Disconnect, by “fully opening” its fuse holder, the Fuse F10 (SID/FFD driver power supply).
• Disconnect, by “fully opening” its fuse holder, the Fuse F11 (“in-room” console power supply).
• Disconnect, by “fully opening” its fuse holder, the Fuse F12 (Column scanning, SFD scanning and
TBT longitudinal drivers Logic / 24 Volt power supply).
• Disconnect, by “fully opening” its fuse holder, the Fuse F13 (Tilting and Elevation drivers Logic / 24 Volt power supply).

2. On the “T” CPU card, remove the Jumpers JP1 and JP2.
• Measure the impedance between pin 1 of JP1 and pin 1 of JP2.
➢ If the measured impedance is not about 120 Ohm (+/- 10 Ohm),

Re-mount the jumpers on JP1 and JP2 and,
restart this procedure (Appendix 02) from the beginning. ➔
• In case, CN134 it was disconnected, Reconnect it.
• Disconnect the connector CN127 (generator ON/OFF commands).
• By means of the related pushbutton on the main control desk,

Power “ON” the unit.
• Check the status of the LED LD19.
➢ If LD19 is “ON”, jump to point “2a”. ➔

Power “OFF” the unit.
• Disconnect the connector CN134.

• On the cable connector CN134, measure the resistance between pin 12 and pin 13.
➢ If the resistance is not less than 10 Ohm, change the “in-room” console cable (the one connecting CN134 on the “T” CPU card to
the CN1005, on the back side of the “in-room” console) and, jump back to point “2”. ➔

After this operation, please to verify the correct setup of the card jumpers, as displayed on the unit service manual (code
5793727-1EN).
2a. By means of the related pushbutton on the main control desk, Power “OFF” the unit.
➢ If the resistance is not less than 10 Ohm, change the “in-room” console cable (the one connecting CN134 on the “T” CPU card to the
CN1005, on the back side of the “in-room” console) and, jump back to point “2”. ➔
• Re-connect the connector CN134 on the “T” CPU (Clisis Main) card.
• Access the “in-room” control desk, “open it” and locate, inside it, the
“Console Control/Interface” card.
• Check that the (in-room) Console CAN Terminator jumper SW4 (on Can_H
the Console Control/Interface card) is NOT mounted (not inserted).
➢ If the above Jumper it was mounted, please remove it and

continue with the procedure (probably the CAN line problem it was
a consequence of that jumper, anyway it is better to check that other Can_L
Can_GND
issues are not present).
• On the “Console Control/Interface” card, locate the connector CN1036

(see the image on the right).

2b. With a multimeter, measure the impedance between

Pin # 10 (Can_L) and the pin #9 (Can_H) of the connector
CN1036 (see the image on the right). Doing this test please to
“use” the “positive tip” of the multimeter on pin 9 (Can H).
Can_H
1 Megaohm), jump to point “2c”. ➔
• Disconnect the connector CN134 from the “T” CPU (Clisis Main)
card. Can_L
Can_GND
• Measure (again) the impedance between Pin # 10 (Can_L) and

the pin #9 (Can_H) of the connector CN1036 (see the image on
the right). Doing this test please to “use” the “positive tip” of the
multimeter on pin 9 (Can H).

1 Megaohm), Change the “T” CPU card (Clisis Main).
5793727-1EN).
• Disconnect, from the back-side of the “in-room” console the connector CN1005.
• Measure (again) the impedance between Pin # 10 (Can_L) and the pin #9 (Can_H) of the connector CN1036 (see the image on the
right). Doing this test please to “use” the “positive tip” of the multimeter on pin 9 (Can H).
➢ If the measured impedance is about infinite (greater than 1 Megaohm), Change the “in-room” console cable (the one connecting CN134
on the “T” CPU card to the CN1005, on the back side of the “in-room” console) and, jump back to point “2b”. ➔

• On the “in-room” console, Change the “Console Control/Interface” card.

5793727-1EN).
software release loaded on the other unit’s CPUs. Anyway, by the Console Control/Interface card changing it will be also necessary to re-
Jump back to point “2a”. ➔
2c. In case of are disconnected, Re-connect CN134 (on the “T” CPU card) as well as the connector CN1005 of the “in-room” console.
• “Go back” to the “T” CPU card (Clisis Main).


➢ If the above measured impedance is about 120 Ohm (+/- 10 Ohm), jump to point “2d”. ➔

5793727-1EN).

2d. Go back to the “Console Control/Interface” card that is inside the “in-room” control desk.
• By means of the related pushbutton on the main

control desk, Power “ON” the unit.
• With a multimeter, measure the impedance between

Pin # 10 (Can_L) and the pin #9 (Can_H) of the
connector CN1036.
Can_H
• By means of the related pushbutton on the main control
desk, Power “OFF” the unit.
➢ If the above measured impedance is about 120 Ohm (+/- 10

Can_L
Ohm), jump to point “3”. ➔ Can_GND
• Mount a Jumper on SW4 of the Console Control/Interface card.
• On the back side of the “in-room” Console, Disconnect CN1005.
• On the card connector, Measure the impedance between pin 6

and pin 7 of CN1005.
➢ If the measured impedance is about infinite, change the “Console Control/Interface” card.
5793727-1EN).
If together this card it was changed also the (ARM) CPU card module, to resume the unit working it will be necessary to load on it the
same software release loaded on the other unit’s CPUs. Anyway, by the Console Control/Interface card changing it will be also
necessary to re-calibrate all the parameters related to the functions are controlled by it.
• Remove the Jumper from SW4 of the Console Control/Interface card.
• Change the “in-room” console cable (the one connecting CN134 on the “T” CPU card to the CN1005, on the back side of the “in-room”
console) and, jump back to point “2a”. ➔
3. Resume the unit’s original power Breaker and Fuses status.
• In case the unit is (already) in “ON” status, By means of the related pushbutton on the main
control desk, Power “OFF” the unit.
• In case is disconnected, (on the “T” CPU card) Re-connect the connector CN127 (generator ON/OFF
commands).
• Switch “ON” the Breaker SW3 (Column scanning, SFD scanning and TBT longitudinal drivers main
power supply).
• Switch “ON” the Breaker SW4 (Tilting and Elevation drivers main power supply).
• Re-connect, by “fully closing” its fuse holder, the Fuse F4 (TBT Lateral driver power supply).
• Re-connect, by “fully closing” their fuse holders, the Fuses F5 and F6 (SFD power supply).
• Re-connect, by “fully closing” its fuse holder, the Fuse F9 (Collimator power supply).
• Re-connect, by “fully closing” its fuse holder, the Fuse F10 (SID/FFD driver power supply).
• Re-connect, by “fully closing” its fuse holder, the Fuse F11 (“in-room” console power supply).
• Re-connect, by “fully closing” its fuse holder, the Fuse F12 (Column scanning, SFD scanning and TBT longitudinal drivers Logic / 24 Volt power
supply).
• Re-connect, by “fully closing” its fuse holder, the Fuse F13 (Tilting and Elevation drivers Logic / 24 Volt power supply).

D. Procedure / Appendix #2 final steps.
previous steps.

Console.
changed.
room” Console.
• Exit this procedure/Appendix and check for the unit proper working.

Appendix 03 – CAN line in short circuit (or not correctly terminated)


Preliminary:
The nominal value of the CAN line impedance, measured between the CAN H and the CAN L lines, is 60 Ohm (or 180 Ohm, if measured on an
“intermediary” CPU terminator jumper).
In case of, considering the component tolerance and the measuring tool error, the measured impedance (with the unit “OFF”) is lower of 50 Ohm
(or lower than 170 Ohm, if measured between the two pin of an “intermediary” CPU terminator jumper) we are in presence of one of the
following cases:
• The CAN line is wrongly terminated (more than two terminations are “inserted” on the line).
• The CAN line is, somewhere, in short circuit (cable problem).
• The CAN Driver or some other components on one (or more) CPU cards is faulty.
❖ To troubleshoot this situation it is necessary to do some tests and measuring on the physical line. At this proposal, please to take as reference the
connection diagram of the previous page.
❖ Also if is not a must, a short UTP (not crossed) patch cable could be helpful to do some of the required tests.
NOTE: To troubleshoot the above cases, it will be necessary to remove the jumpers from JP1 and JP2. Please to take care to reinsert
these jumpers while any one of the above three troubleshooting procedures is completely ended (after a card changing and so on).


Please to locate the two jumpers JP1 and JP2 on the Clisis Main card (“T” CPU card).
Both of these two jumpers are “closed” (jumpers are mounted).
Measure the impedance between JP1 and JP2 (without removing the jumpers).
➢ In case the measured value is lower than 50 Ohm (considering components

tolerance), we are in presence of a fault on the main part of the CAN line (the line is,
somewhere, in short circuit or, a CAN Driver or some other components on one or
more CPU cards are faulty).
Go to point “A”. ➔
➢ In case the measured value is 60 Ohm (+/- 10 Ohm), the line impedance it is
correct. It is only to verify that the “inserted” terminations are the correct ones.
A. The measured value between JP1 and JP2 lower than 50 Ohm.
1. Remove the Jumpers JP1 and JP2 and Measure the impedance between pin 2 of JP1 and
pin 2 of JP2.
“T”  “main Console”  “Console Control/Interface card”  Console side
Terminator (on the Console Control/Interface card) is probably correct.
Check that the jumper configuration on the Console Control/Interface card of the
main Console is exactly the one displayed on the CAN connection diagram (see on the
beginning of this appendix) and, jump to point “2”. ➔

❖ The measured impedance is less than 100 Ohm there is a problem on the connection “T”  “Console” and/or on the “T” CPU card and/or on the
“Console Control/Interface card”.
• Measure again the impedance between pin 2 of JP1 and pin 2 of JP2.
➢ If the measured impedance is not about infinite (greater than 1 Megaohm), Change the “T” CPU card (Clisis Main).
After this operation, please to verify the correct setup of the card jumpers, as displayed on the unit service manual (code 5793727-1EN).
• Re-connect CN128 and, on the back side of the control

desk, Disconnect CN1005.
Can_H
• Open the main Console and, on the “Console Control/Interface card”,

locate the connector CN1036 (see the image on the right).
• With a multimeter, measure the impedance between Can_L

Can_GND
Pin # 10 (Can_L) and the pin #9 (Can_H) of the connector CN1036 (see
the image on the right).
➢ If the measured impedance is less than 100 Ohm change the

After this operation, please to verify the correct setup of the card
jumpers, as displayed on the unit service manual (code 5793727-
1EN).
calibrate all the parameters related to the functions are controlled by it. Related instructions are provided before the end of this procedure.
• Change the cable connecting CN1005  CN128 (main console cable).
• Re-connect all the disconnected cables and jump back to the point “1”. ➔
2. On the “T” CPU card, Measure the impedance between pin 1 of JP1 and pin 1 of JP2.
“T”  “SFD”  “Collimator”  Collimator side Terminator (on Collimator CPU), is
probably correct.
Remount JP1 and JP2 and, jump to point “B”. ➔
❖ The measured impedance is less than 100 Ohm there is a problem on the connection “T”
 “SFD”  “Collimator”  Collimator side Terminator (on Collimator CPU) and/or on the “T” CPU card, on the “SFD” CPU card, on the “Tube
stand control” card and/or on the “Collimator” CPU card.
➢ If the above measured impedance is about 60 Ohm (+/- 10 Ohm), please to check if a jumper is mounted on SW4 of the “SFD” CPU card.
➢ If there is a jumper mounted on SW4 of the “SFD” CPU card, remove it and go back to the point “2”. ➔
• Go to the collimator and Disconnect the cable from CN601 (Collimator back side connector).
• Go back to the “T” CPU card and, Measure again the impedance between pin 1 of JP1 and pin 1 of JP2.
➢ If the measured impedance is about infinite (greater than 1 Megaohm) the problem is inside the collimator so,
reconnect the cable on CN601 and jump to point “2a”. ➔
• Reconnect the cable on CN601 (Collimator back side connector).

• Go to the “Tube stand Control card” (located on the Column right side), and disconnect the cable from CN510.
• Go back to the “T” CPU card and Measure again the impedance between pin 1 of JP1 and pin 1 of JP2.
CN510  CN601 (collimator cable), reconnect it on both connectors and,
• On the “Tube stand Control card”, Reconnect the cable on CN510 and disconnect the cable from CN509.
• Go back to the “T” CPU card and Measure again the impedance between pin 1 of JP1 and pin 1 of JP2.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), change Tube Stand Control card.
Reconnect all the connectors and, jump back to the point “2”. ➔
• Reconnect the cable on CN509.
• Go to the “SFD” CPU card, and disconnect the cable from CN411.
• Go back to the “T” CPU card and Measure again the impedance between pin 1 of JP1 and
pin 1 of JP2.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), change the
cable connecting CN509  CN411, reconnect it on both connectors and,
• Disconnect the cable from CN412.

➢ If the measured impedance is about infinite (greater than 1 Megaohm), chance the “SFD” CPU card.
• Disconnect the cable from CN125 of the “T” CPU card.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), chance the cable connecting CN509  CN411, reconnect it on
both connectors and, jump back to the point “2”. ➔


2a. The problem is inside the collimator.
➢ If the measured impedance is about infinite (greater than 1 Megaohm), chance the Collimator CPU
card.
After this operation, please to verify the correct setup of the card jumpers, as displayed on
the unit service manual (code 5793727-1EN).
By this changing, to resume the unit working, it will be necessary to load on the CPU card the same
software release loaded on the other unit’s CPUs and, also, to re-calibrate all the parameters
related to the functions are controlled by it.
Jump back to the point “2” ➔
• Change the collimator internal cable connecting CN601 CN16, reconnect it on both connectors and, jump back to the point “2”. ➔
B. The measured value between JP1 and JP2 is 60 Ohm (+/- 10 Ohm).
The above value is the “correct one” about the impedance of the main path of the
unit (table) CAN line.
As this test is not considering the branch related to the “in-room” control desk,
other test procedures (that are on the following) will be needed to test that branch.
On this condition is only to verify that the jumper setting on the different cards is exactly
the one displayed on the CAN connection diagram of the beginning of this appendix.
In any case, a complete jumper setup configuration is also displayed on the figures/images of the unit service manual (code 5793727-1EN).

appendix (a complete jumper setup configuration is also displayed on the figures/images of the unit service manual - code 5793727-1EN).
C. The unit CAN line “main path” impedance is correct; the test must continue with the “in-room” control desk branch, if present.
WARNING

power supply).

2. On the “T” CPU card, remove the Jumpers JP1 and JP2.
➢ If the measured impedance is less than 100 Ohm,

Re-mount the jumpers on JP1 and JP2 and,
restart this procedure (Appendix 03) from the beginning. ➔
• In case, CN134 it was disconnected, Reconnect it.

➢ If LD19 is “ON”, jump to point “2a”. ➔


➢ If the resistance is not less than 10 Ohm, change the “in-room” console cable (the one connecting CN134 on the “T” CPU card to
the CN1005, on the back side of the “in-room” console) and, jump back to point “2”. ➔

5793727-1EN).
2a. By means of the related pushbutton on the main control desk, Power “OFF” the unit.
• Re-connect the connector CN134 on the “T” CPU (Clisis Main) card.
• Access the “in-room” control desk, “open it” and locate, inside it, the
• Check that the (in-room) Console CAN Terminator jumper SW4 (on the Can_H
Console Control/Interface card) is NOT mounted (not inserted).
➢ If the above Jumper it was mounted, please remove it and

continue with the procedure (probably the CAN line problem it was
a consequence of that jumper; anyway it is better to check that other Can_L
Can_GND
issues are not present).
• On the “Console Control/Interface” card, locate the connector CN1036

(see the image on the right).

2b. With a multimeter, measure the impedance between

Pin # 10 (Can_L) and the pin #9 (Can_H) of the connector
CN1036 (see the image on the right). Doing this test please to
“use” the “positive tip” of the multimeter on pin 9 (Can H).
Can_H
1 Megaohm), jump to point “2c”. ➔
• Disconnect the connector CN134 from the “T” CPU (Clisis Main)
card. Can_L
Can_GND
• Measure (again) the impedance between Pin # 10 (Can_L) and

the pin #9 (Can_H) of the connector CN1036 (see the image on
the right). Doing this test please to “use” the “positive tip” of the
multimeter on pin 9 (Can H).

1 Megaohm), Change the “T” CPU card (Clisis Main).
5793727-1EN).
• Measure (again) the impedance between Pin # 10 (Can_L) and the pin #9 (Can_H) of the connector CN1036 (see the image on the
right). Doing this test please to “use” the “positive tip” of the multimeter on pin 9 (Can H).
➢ If the measured impedance is about infinite (greater than 1 Megaohm), Change the “in-room” console cable (the one connecting CN134
on the “T” CPU card to the CN1005, on the back side of the “in-room” console) and, jump back to point “2b”. ➔

• On the “in-room” console, Change the “Console Control/Interface” card.

5793727-1EN).
2c. In case of are disconnected, Re-connect CN134 (on the “T” CPU card) as well as the connector CN1005 of the “in-room” console.
• “Go back” to the “T” CPU card (Clisis Main).


➢ If the above measured impedance is less than 100 Ohm, Change the “T” CPU card (Clisis Main).
5793727-1EN).

commands).
power supply).
supply).

previous steps.

Console.
changed.
room” Console.
Exit this procedure/Appendix and check for the unit proper working.

Appendix 04 – CAN line insulation (to GND) problem


NOTE: As for the sake of this analysis it is important to consider that the multimeter used to do the measuring is an “invasive object”. The voltage
that it use to measure the resistance/impedance can “cause” a leakage current that it flowing through the TVS protection components (transzorb,
transil) that are present on the CAN lines (components mounted from CAN-H, CAN-L and CAN GND lines).
As by all on the above, an impedance that would be normally over 500 KOhm it could be indicated, by the multimeter, in the range 60 – 65 KOhm. This
value it is so used on the following procedure to identify CAN line – to GND insulation issues.
*** In case the measured CAN line impedance, measured between GND and CAN H (or CAN L) lines, is lower than 60 KOhm, we are facing one or both
of the following situation(s):
• One or more cards is / are defective.

• One or more cable(s) is / are defective.
❖ As the problem could be generated by more than one fault, it will be necessary to re-iterate the procedure till the insulation problem it is solved.
❖ As the standard impedance between CAN H and CAN L lines is about 60 Ohm, and this value is really lower than 60 KOhm, the troubleshooting is
done measuring only on one of the two signal lines.
NOTE: During the troubleshooting, it will be necessary to remove the jumpers from JP1 and JP2. Please to take care to reinsert these
jumpers while the troubleshooting procedure is completely ended, after a card changing and so on.
Also, some connectors are to disconnect during the tests, please to take care to re-connect all the cables at the end of the
troubleshooting procedures.
❖ To troubleshoot this situation it is necessary to do some tests and measuring on the physical line. At this proposal, please to take as reference the
connection diagram of the previous page.
❖ Also if is not a must, a short UTP (not crossed) patch cable could be helpful to do some of the required tests.
I. Test without the “in-room” control desk.
II. Test of the “in-room” control desk and its related wirings.


A. Check of the main part of the Table CAN line.
• Locate the two jumpers JP1 and JP2 on the Clisis Main card (“T” CPU card).
Both of these two jumpers are “closed” (jumpers are mounted).
• Without removing the jumpers, Measure the impedance between JP1

and GND (Metal frame) as well as the impedance between JP2 and
GND. Doing this test please to “use” the “positive/red tip” of the
multimeter to measure the CAN line (the “negative/black tip” must be
connected to the ground/metal frame).
➢ If both the measured impedance are more than 60 KOhm,

• Measure (again) the impedance between JP1 and GND (Metal frame) as well as
the impedance between JP2 and GND. Doing this test please to “use” the
“positive/red tip” of the multimeter to measure the CAN line (the “negative/black tip”
must be connected to the ground/metal frame).
➢ If any one of the measured impedances is lower than 60 KOhm, Change the “T” CPU card (Clisis Main).
Re-connect CN125 and CN128, and Jump back to the point “A”. ➔

• Re-connect CN128, leaving CN125 disconnected.
• Measure the impedance between JP1 and GND (Metal frame) as well as the impedance between JP2 and GND. Doing this test please to “use” the
“positive/red tip” of the multimeter to measure the CAN line (the “negative/black tip” must be connected to the ground/metal frame).
➢ If any one of the measured impedances is lower than 60 KOhm, there is a problem on the CAN line Connection:
“T” CPU  “main Console”  “Console Control/Interface card”.
Jump to the point “1”. ➔
• Disconnect CN128.
• Measure the impedance between JP1 and GND (Metal frame) as well as the impedance between JP2 and GND. Doing this test please to “use” the
“positive/red tip” of the multimeter to measure the CAN line (the “negative/black tip” must be connected to the ground/metal frame).
➢ If one of the measured impedances is lower than 60 KOhm, there is a problem on the CAN line Connection:
“T”  “SFD”  “Collimator”.
Jump to the point “2”. ➔
• Jump back to the point “A”. ➔

1. “Main Console branch” issue.
• Verify that CN125 (on the “T” CPU card) is disconnected.
• On the “Main Console” back side, Disconnect CN1005.
• Open the Console and, on the “Console Control/Interface card”,

Can_H
• With a multimeter, on the connector CN1036 (see the image on

the right) measure the impedance between Pin # 9 (Can_H) and
Pin #8 (Can_GND) as well as the impedance between Pin # 10 Can_L
(Can_L) and Pin #8 (Can_GND).
Doing this test please to “use” the “positive/red tip” of the
Can_GN
multimeter on the “Can H” / “Can L” pin, while the “negative/black D
tip” must be connected to the “Can_GND” pin.
➢ If both the measured impedances are more than 60 KOhm,

change the cable CN128  CN1005 (main console cable).
After this operation, re-connect all the disconnected
cables, re-connect CN125 and, finally, Jump back to the
point “A”. ➔
➢ If any one of the measured impedance is lower than 60 KOhm, change the “Console Control/Interface” card.
Re-connect CN1005, re-connect CN125, and Jump back to the point “A”. ➔

2. “SFD - Collimator branch” issue.
• Verify that CN128 (on the “T” CPU card) is disconnected.
• Disconnect, on the back side of the Collimator, the connector CN601.
• On the “T” CPU card Measure (again) the impedance between JP1 and GND (Metal frame) as well as the
impedance between JP2 and GND. Doing this test please to “use” the “positive/red tip” of the multimeter to
measure the CAN line (the “negative/black tip” must be connected to the ground/metal frame).
➢ If both the measured impedances are more than 60 KOhm, the problem is “inside” the collimator.
Jump to the point “2a”. ➔
• Re-connect CN601 (on the back side of the Collimator).
• On Tube Stand Control card, Disconnect CN510.
• Measure (again) the impedance between JP1 and GND (Metal frame) as well as the impedance between
JP2 and GND. Doing this test please to “use” the “positive/red tip” of the multimeter to measure the CAN line
(the “negative/black tip” must be connected to the ground/metal frame).
➢ If both the measured impedances are more than 60 KOhm, change the cable connecting
CN510  CN601 (Collimator Cable). After this operation, re-connect all the disconnected cables,
re-connect CN128 and, Jump back to the point “A”. ➔
• Disconnect CN509 (also on Tube Stand Control card).

• Measure (again) the impedance between JP1 and GND (Metal frame) as well as the impedance between JP2 and GND. Doing this test please
to “use” the “positive/red tip” of the multimeter to measure the CAN line (the “negative/black tip” must be connected to the ground/metal frame).
➢ If the measured impedance is more than 60 KOhm, change the “Tube Stand Control” card.
Executed all on the above, re-connect all the disconnected cables, re-connect CN128 and, Jump back to the point “A”. ➔
• On the SFD CPU card, Disconnect CN411,
• Measure (again) the impedance between JP1 and GND (Metal frame) as well as the
impedance between JP2 and GND. Doing this test please to “use” the “positive/red tip” of
the multimeter to measure the CAN line (the “negative/black tip” must be connected to the
ground/metal frame).
➢ If both the measured impedances are more than 60 KOhm, change the cable
connecting CN411  CN509.
After this operation, re-connect all the disconnected cables, re-connect CN128 and,
Jump back to the point “A”. ➔
• Re-connect CN411 and, Disconnect CN412.
• Measure (again) the impedance between JP1 and GND (Metal frame) as well as the impedance between JP2 and GND. Doing this test please
to “use” the “positive/red tip” of the multimeter to measure the CAN line (the “negative/black tip” must be connected to the ground/metal frame).
➢ If both the measured impedances are more than 60 KOhm, Change the “SFD” CPU card.
unit’s CPUs and, in case, to re-calibrate all the parameters related to the functions are controlled by it. Related instructions are provided
before the end of this procedure.
➢ If any one of the measured impedances is lower than 60 KOhm, Change the cable CN412  CN125.
After this, re-connect all the disconnected cables, re-connect CN128 and, Jump back to the point “A”. ➔
2a. The problem is inside the collimator.
• Re-connect CN601 (on the collimator back side).
• On the “T”CPU card, measure (again) the impedance between JP1 and GND (Metal frame) as well
as the impedance between JP2 and GND. Doing this test please to “use” the “positive/red tip” of the
multimeter to measure the CAN line (the “negative/black tip” must be connected to the ground/metal
frame).
➢ If both the measured impedances are more than 60 KOhm, chance the Collimator CPU card.
After this operation, please to verify the correct setup of the card jumpers, as displayed on
the unit service manual (code 5793727-1EN).
• Change the collimator internal cable connecting CN601 CN16 and, re-connect it on both connectors.
• Re-connect CN128 (on the “T” CPU card).
• Jump back to the point “A”. ➔

B. Both the Can H to GND and Can L to GND impedances more than 60 KOhm.
The main path of the unit (table) CAN line has no insulation problems.
As this test is not considering the branch related to the “in-room” control desk, other test procedures (that are on the following) will be needed
to test that branch.
On this condition is only to verify that the jumper setting on the different cards is exactly the one displayed on the CAN connection diagram of
the beginning of this appendix.
In any case, a complete jumper setup configuration is also displayed on the figures of the unit service manual (code 5793727-1EN).
appendix (a complete jumper setup configuration is also indicated on the figures of the unit service manual - code 5793727-1EN).
C. The main path of the unit CAN line has no insulation problems; the test must continue with the “in-room” control desk branch, if present.

WARNING
power supply).

2. Go to the “T (Clisis main) CPU card
• Remove the Jumpers JP1 and JP2.
• Measure the impedance between pin 1 of JP1 and GND (Metal frame)
as well as the impedance between pin 1 of JP2 and GND.
Doing this test please to “use” the “positive/red tip” of the multimeter to
measure the CAN line (the “negative/black tip” must be connected
to the ground/metal frame).
➢ If any one of the measured impedances is lower 60 KOhm,

Re-insert (remount) JP1 and JP2, and
• In case CN134 it was disconnected, Reconnect it.

• By means of the related pushbutton on the main control desk, Power “OFF” the unit.
➢ If, when the unit was “ON” the LD19 it was “ON”, jump to point “3”. ➔


3. In_Room console CAN insulation tests
• Open the “In-Room” Console and, on the “Console Control/Interface card”,

• With a multimeter, on the connector CN1036 (see the image on Can_H
the right) measure the impedance between Pin # 9 (Can_H)

and Pin #8 (Can_GND) as well as the impedance between Pin
# 10 (Can_L) and Pin #8 (Can_GND).
Doing this test please to “use” the “positive/red tip” of the Can_L
multimeter on the “Can H” / “Can L” pin, while the

“negative/black tip” must be connected to the “Can_GND” pin. Can_GND
➢ If both the measured impedances are more than 60 KOhm, jump to

point “4”. ➔

• On the “T” CPU card (Clisis main), Disconnect the connector CN134.
• Go back to the “In-room” console and, on CN1036,

measure (again) the impedance between Pin # 9
(Can_H) and Pin #8 (Can_GND) as well as the
impedance between Pin # 10 (Can_L) and Pin #8
(Can_GND).
Doing this test please to “use” the “positive/red tip” of
the multimeter on the “Can H” / “Can L” pin, while the Can_H
“negative/black tip” must be connected to the
“Can_GND” pin.
➢ If both the measured impedances are more than

Can_L
60 KOhm, Change the “T” CPU card (Clisis Main).
After this operation, please to verify the correct
setup of the card jumpers, as displayed on the Can_GND
By this changing, to resume the unit working, it
will be necessary to load on the CPU card the
same software release loaded on the other unit’s
CPUs and, also, to re-calibrate all the parameters
related to the functions are controlled by it.
Related instructions are provided before the end
of this procedure.
• On the “T” CPU card (Clisis main), Re-connect the connector CN134.

• On the “In-Room” console, on CN1036, measure (again) the impedance

between Pin # 9 (Can_H) and Pin #8 (Can_GND) as well as the impedance
between Pin # 10 (Can_L) and Pin #8 (Can_GND).
multimeter on the “Can H” / “Can L” pin, while the Can_H
“negative/black tip” must be connected to the “Can_GND” pin
➢ If both the measured impedances are more than 60 KOhm, Can_L

change the cable CN134  CN1005
(In-room console cable). After this operation, re-connect all the Can_GND
disconnected cables, re-connect CN125 and, finally,
Jump back to point “2”. ➔
➢ If any one of the measured impedances is lower than 60 KOhm,

change the “Console Control/Interface” card. After this operation,
please to verify the correct setup of the card jumpers, as displayed
on the unit service manual (code 5793727-1EN).
Re-connect CN1005, re-connect CN125, and Jump back to the point “A”. ➔

4. Final test on switching relays of the “T” CPU card.
• Verify that the connector CN127 (generator ON/OFF commands) is

Disconnected, otherwise Disconnect it.

• Measure the impedance between pin 1 of JP1 and GND (Metal frame)
as well as the impedance between pin 1 of JP2 and GND.
multimeter to measure the CAN line (the “negative/black tip” must
be connected to the ground/metal frame).

➢ If both the above measured impedances are more than 60 KOhm,

jump to point “5”. ➔
➢ If any one of the measured impedances is lower than 60 KOhm, Change the “T” CPU card (Clisis Main).

commands)
• In case is disconnected, (on the “T” CPU card) Re-connect the connector CN125.
• In case is disconnected, (on the “T” CPU card) Re-connect the connector CN134.
power supply).
supply).

previous steps.

Console.
changed.
room” Console.

Appendix 05 – Driver CAN line troubleshooting

Following this Appendix, it is possible to analyze & troubleshoot the drivers CAN line connection.
The can line used to communicate with the drivers is completely separate from the one used inside the system between the different CPU cards.
The “T” CPU card (Clisis Main) act as a “bridge” between the above two CAN lines.
The Driver CAN line is built as:
Termination  Elevation Driver  “T” CPU  Column Scan Driver  SFD Scan Driver  TBT Long Driver  Terminator
As like the main line, the CAN_GND signal is connected to ground only at level of the “T” CPU card.


1) On the “T” CPU card, measure the impedance between the two pin of SW11.
➢ In case the measured impedance is about 185 Ohm (+/- 10 Ohm), Jump to point 4). ➔
➢ In case the measured impedance is less than 165 Ohm, the CAN line is in short circuit or, a driver is
defective. Jump to point 2). ➔
➢ In case the measured impedance is about 250 Ohm (+/- 10 Ohm), the CAN line is
broken or, one of the two (line) terminators is not mounted. Jump to point 3). ➔
➢ In case the measured impedance is more than 6 KOhm, the CAN line is broken
and/or one or both the (line) terminators are not mounted.
Jump to point 3). ➔
2) Line is in Short circuit.
2a) On “T” CPU card (Clisis main), Disconnect CN149
• Measure (again) the impedance between the two terminals of SW11.
➢ If the measured impedance is about 250 Ohm (+/- 10 Ohm), re-connect CN149 and Jump to point 2b). ➔

• Disconnect CN150
➢ If the measured impedance is less than 60 KOhm, re-connect CN150 and CN149 and Change the “T” CPU card (Clisis Main).
Jump back to point 1). ➔
➢ If the measured impedance is about 250 Ohm (+/- 10 Ohm), re-connect CN149 and Jump to point 2b). ➔
• Go to the TBT Longitudinal driver.
• Disconnect the terminator connector CN377 (X12).
➢ If the measured impedance is less than 6 KOhm, search for problem on CN377 and/or on the TBT Long driver, fix it, re-connect CN377 and
Jump back to point 2a). ➔
• Disconnect CN378 (X13)

➢ If the measured impedance is less than 6 KOhm, Change the TBT Long driver, re-connect CN378 and Jump back to point 2a). ➔
• Go to the SFD scanning driver
➢ If the measured impedance is less than 6 KOhm, Change the cable CN368  CN378 and, Jump back to point 2a). ➔
➢ If the measured impedance is less than 6 KOhm, Change the SFD Scanning driver, re-connect CN367 and, Jump back to point 2a). ➔

• Go to the Column scanning driver
➢ If the measured impedance is less than 6 KOhm, Change the cable CN357  CN367 and, Jump back to point 2a). ➔
➢ If the measured impedance is less than 6 KOhm, Change the Column Scanning driver, re-connect CN358 and, Jump back to point 2a). ➔
• Change the cable CN150  CN358 and, Jump back to point 2a). ➔
2b) Disconnect CN150
➢ If the measured impedance is about 250 Ohm (+/- 10 Ohm), re-connect CN150 and Jump back to point 1). ➔
• Go to the Table Elevation driver.
• Disconnect the terminator connector CN197 (X13).

➢ If the measured impedance is less than 6 KOhm, search for problem on CN197 and/or on the Elevation driver, fix it, re-connect CN197 and
Jump back to point 2b). ➔
➢ If the measured impedance is less than 6 KOhm, Change the Elevation driver, re-connect CN196 and Jump back to point 2b). ➔
• Change the cable CN150  CN358, re-connect CN197 and Jump back to point 1). ➔
3) Line is “cut” or not properly terminated.
3a) Measure (again) the impedance on the two terminals of SW11.
➢ If the measured impedance is about 250 Ohm (+/- 10 Ohm), re-connect CN149 and Jump to point 3c). ➔
3b) Problem on path: “T” CPU  Column Scan Driver  SFD Scan Driver  TBT Long Driver  Terminator.
• Mount a jumper on SW11.

• Measure the impedance between pin 6 and pin 9 of the card connector CN150.
➢ If the measured impedance is more than 150 Ohm, Change the “T” CPU card (Clisis Main).
• Go to the Column scanning driver (DRV10).
• Disconnect CN358 (X13).
• Measure, on the cable connector CN358, the impedance between pin 3 and pin 4.
➢ If the measured impedance is more than 150 Ohm, Change the cable CN150  CN358, remove the jumper from SW11 and, jump to point
3a). ➔
• Go to the TBT longitudinal driver (DRV12).
• Verify that, on CN377 (X12) is mounted the “pin1-pin6” termination connector (short circuit jumper).
➢ If it was not connected (or is faulty), fix it remove the jumper from SW11 and, jump back to point 3a). ➔
• Disconnect the cable connecting CN368 (X13, on SFD scanning driver) and CN378 (X13, on TBT long driver).

• With a multimeter, check the (cable) continuity between:

▪ CN368 pin 3 and CN378 pin 3 (Can_H signal).
▪ CN368 pin 4 and CN378 pin 4 (Can_L signal).
▪ CN368 pin 5 and CN378 pin 5 (Can_GND signal).
➢ If any one of the above three continuity tests is faulty (no continuity), Change the cable CN368  CN378,
remove the jumper from SW11 and, jump back to point 3a). ➔
• Measure, on the cable connector CN368 the impedance between pin 3 and pin 4.
➢ If the measured impedance is more than 150 Ohm, Change the TBT longitudinal Driver,
• Go to the Column scanning driver (DRV10).
• Disconnect the cable from CN357 (X12).
• Measure on the cable connector CN357 the impedance between pin 3 and pin 4.
➢ If the measured impedance is about 130 Ohm (+/-20 Ohm), Change the Column Scanning Driver,
• Re-connect CN357 (X12).

• Disconnect the cable from CN367 (X12).
➢ If the measured impedance is about 130 Ohm (+/-20 Ohm), Change the SFD Scanning Driver,
• Change the cable CN357  CN367.
• Remove the jumper from SW11.
• Jump back to point 1). ➔
3c) Problem on path: Termination  Elevation Driver  “T” CPU.
3d) Measure (again) the impedance between the two terminals of SW11.
➢ If the measured impedance is about 250 Ohm (+/- 10 Ohm), re-connect CN150 and Jump back to point 1). ➔
• Mount a jumper on SW11.

• Measure the impedance between pin 6 and pin 9 of the card connector CN149.
➢ If the measured impedance is more than 150 Ohm, Change the “T” CPU card (Clisis Main).
• Go to the Elevation driver.
• Verify that on CN197 (X13) is mounted the “pin1-pin6” termination connector (short circuit jumper).
➢ If it was not connected (or is faulty), fix it remove the jumper from SW11 and jump back to point 3d). ➔
• Disconnect CN196 (X12).
➢ If the measured impedance is about 130 Ohm (+/-20 Ohm), Change the Elevation Driver, remove the jumper from SW11
and, jump back to point 3d). ➔
• Change the cable CN149  CN196, remove the jumper from SW11 and, jump back to point 3d). ➔

4) Tests about grounding and insulation problems.
• Measure the impedance between pin 5 of the card connector CN149 and GND (metal
frame) as well as the impedance between pin 5 of the card connector CN150 and GND
(metal frame)
➢ If any one of the measured impedance is greater than 10 Ohm, Change the “T”
CPU card (Clisis Main).
displayed on the unit service manual (code 5793727-1EN).
• Measure the impedance between pin 5 of the cable connector CN150 and GND (metal frame).
➢ If the measured impedance is less than 400 KOhm, jump to point 4c). ➔
• Go to the TBT Longitudinal driver.

➢ If the measured impedance is less than 10 Ohm Re-connect CN378 and jump to point 4d). ➔
4a) Go to the SFD scanning driver.
➢ If the measured impedance is more than 15 Ohm, re-connect CN378, CN367 and jump to point 4b). ➔
• Measure the continuity between pin 5 of the cable connector CN368 and pin 5 of the cable connector CN378.
➢ If the measured impedance is less than 10 Ohm, Change the SFD Scanning Driver, reconnect CN367, CN368, CN378
and, finally jump back to point 4). ➔
• Change the cable CN368  CN378, re-connect CN367 and, jump back to point 4). ➔
4b) Go to the Column scanning driver.

➢ If the measured impedance is more than 15 Ohm, Change the cable CN150  CN358, re-connect CN367 and,
jump back to point 4). ➔
• Measure the continuity between pin 5 of the cable connector CN357 and pin 5 of the cable connector CN367.
➢ If the measured impedance is less than 10 Ohm, Change the Column Scanning Driver, reconnect CN357, CN358, CN367 and,
jump back to point 4). ➔
• Change the cable CN357  CN367, re-connect CN358 and, jump back to point 4). ➔
4c) Go to the TBT longitudinal driver.
• On the TBT longitudinal driver, disconnect CN378 (X13).
• Measure again the impedance between pin 5 of the cable connector CN150 and GND (metal frame).
➢ If the measured impedance is more than 400 KOhm, Change the TBT Longitudinal Driver, reconnect all and go back to point 4). ➔
• On the SFD Scanning Driver, disconnect CN368 (X13)

➢ If the measured impedance is more than 400 KOhm, Change the cable CN378  CN368, reconnect all and go back to point 4). ➔
• On the SFD Scanning driver, disconnect CN367
➢ If the measured impedance is more than 400 KOhm, Change the SFD Scanning Driver, reconnect all and go back to point 4). ➔
• On the Column Scanning Driver, disconnect CN357 (X12)
➢ If the measured impedance is more than 400 KOhm, Change the cable CN357  CN367, reconnect all and go back to point 4). ➔
• On the Column Scanning Driver, disconnect CN358 (X13)
➢ If the measured impedance is more than 400 KOhm, Change the Column Scan driver, reconnect all and go back to point 4). ➔
• Change the cable CN150  CN358, reconnect all and go back to point 4). ➔

4d) Elevation driver branch.
➢ If the measured impedance is less than 400 KOhm, jump to point 4e). ➔
➢ If the measured impedance is less than 10 Ohm Re-connect CN196 and jump to point 5). ➔
4e) Go to the Elevation driver.
➢ If the measured impedance is more than 400 KOhm, Change the Elevation driver, reconnect all and go back to point 4). ➔

5) Disconnect (if not already done) CN149 and CN150.
• On The “T” CPU card, Measure the impedance between pin1 of SW1 and GND (Metal frame)
as well as the impedance between pin2 of SW1 and GND.
➢ If one of the measured impedances is lower than 250 KOhm, Change the “T” CPU
card (Clisis Main).
displayed on the unit service manual (code 5793727-1EN).
By this changing, to resume the unit working, it will be necessary to load on the CPU
card the same software release loaded on the other unit’s CPUs and, also, to re-
• Re-connect CN150, leaving CN149 disconnected.
• Measure the impedance between pin1 of SW1 and GND (Metal frame).
➢ If the measured impedance is lower than 250 KOhm, there is a problem on the CAN line
Connection:
“T” CPU  Column Scan Driver  SFD Scan Driver  TBT Long Driver  Terminator.
Go to point 5a). ➔
• Measure the impedance between pin1 of SW1 and GND (Metal frame).
➢ If the measured impedance is lower than 250 KOhm, there is a problem on the CAN line Connection Termination  Elevation Driver  “T” CPU.
Go to point 5b). ➔

• Go to point 6). ➔
5a) Leaving CN149 disconnected and CN150 connected.
• Go to the TBT longitudinal driver.
• On The “T” CPU card, measure again the impedance between pin1 of SW1 and GND (Metal frame).
➢ If the measured impedance is lower than 250 KOhm, Change the TBT Longitudinal Driver, reconnect all and go back to point 5). ➔
• Go to the SFD scanning driver.
➢ If the measured impedance is lower than 250 KOhm, Change the cable CN368  CN378, reconnect all and go back to point 5). ➔

➢ If the measured impedance is lower than 250 KOhm, Change the SFD Scanning Driver, reconnect all and go back to point 5). ➔
• Go to the Column scanning driver.
➢ If the measured impedance is lower than 250 KOhm, Change the cable CN357  CN367, reconnect all and go back to point 5). ➔
➢ If the measured impedance is lower than 250 KOhm, Change the Column Scanning Driver, reconnect all and go back to point 5). ➔
5b) Leaving CN150 disconnected and CN149 connected.

➢ If the measured impedance is lower than 250 KOhm, Change the Elevation Driver, reconnect all and go back to point 5). ➔
6) Procedure / Appendix #5 final steps.
previous steps.
• According to the unit Service manual (code 5793727-1EN), Re-configure the parameters related to the functions controlled by the “T” CPU
card.
• According to the unit Service manual (code 5793727-1EN), Re-calibrate the parameters related to the functions controlled by the “T” CPU
card.

Appendix 06 – Driver (related) errors codes

In relation to the troubleshooting of the error codes related to the drivers ( errors 02 00 ccccc, 02 01 ccccc, 02 02 ccccc and, 02 03 ccccc), it is
necessary to take as reference the (two) manuals of the drivers (for a better understanding, parts of those manuals are also copied on the following pages).
Error Code Error source

SS DD CCCCC
02 00 ccccc Error is generated by (is coming from) "Column longitudinal motor driver "
02 01 ccccc Error is generated by (is coming from) "Table Elevation motor driver"
02 02 ccccc Error is generated by (is coming from) "SFD longitudinal motor driver"
02 03 ccccc Error is generated by (is coming from) "Table Top longitudinal motor driver"
The procedure to “decode the error codes” is the following:
1) Identify the driver by the related code (DD).

2) Note the hexadecimal error code “ccccc” = “ABCD(h)”, and go to the table on chapter 6.1 of the “AKD CANopen Communications Manual” (“ABCD”
digits are indicated as 0xABCD).
3) On the table, identify the corresponding Fault/Warning code. This code could be indicated as “nXXX” or as “FXXX” (where “n” means “warning” and
“F” means “Fault”) .
4) On the “AKD Servo Drive Fault Card” manual, locate the code as by the above point 3) and follow the related troubleshooting instructions (if present).
Example: Error 02 00 73C7h ➔ Column longitudinal motor driver error 0x73C7 ➔ Driver Error F484 (Motor V phase missing)
0x73C7 F484 Motor V phase missing.
Fault Message/Warning Cause Remedy Drive Response to

Fault
F484 Wake and Shake - Motor V No current was detected in the motor's V Check the motor connections and Disable power
phase missing. phase during Wake and Shake initialization WS.IMAX (very low current may stage
(Mode 0 only). produce this error).

5793731-1EN, Rev 8 Troubleshooting Guide Table
(from) ©Kollmorgen – AKD CAN-BUS Communication September 2016, Revision R - AKD CANopen | 6 CANopen Drive Profile
CANopen Emergency Messages and Error Codes

Emergency messages are triggered by internal equipment errors. They have a high ID-priority to ensure quick
access to the bus. An emergency message contains an error field with pre- defined error/fault numbers (2
bytes), an error register (1byte), the error category (1 byte), and additional information. Error numbers 0000h
to 7FFFh are defined in the communication or drive profile. Error numbers FF00h to FFFFh have manufacturer-
specific definitions.
Error Fault/ Description

Code Warning
0x0000 0 Emergency error free.
0x1080 - General Warning.
0x1081 - General Error.
0x3110 F523 DC Bus link over voltage FPGA.
0x3120 F247 DC Bus link voltage exceed allowed thresholds.
0x3130 F503 DC Bus link capacitor overload.
0x3180 n503 Warning: DC Bus link capacitor overload.
0x3210 F501 DC Bus link over-voltage.
0x3220 F502 DC Bus Link under-voltage.
0x3280 n502 Warning: DC Bus Link under-voltage.
0x3281 n521 Warning: Dynamic Braking I²T.
0x3282 F519 Regen short circuit.
0x3283 n501 Warning: DC Bus link over-voltage.
0x4210 F234 Excessive temperature, device (control board).
0x4310 F235 Excessive temperature, drive (heat sink).
0x4380 F236 Power temperature sensor 2 high.
0x4381 F237 Power temperature sensor 3 high.
0x4382 F535 Power board overtemperature.
0x4390 n234 Warning: Control temperature sensor 1 high.
0x4391 n235 Warning: Power temperature sensor 1 high.
0x4394 n240 Warning: Control temperature sensor 1 low.
0x4395 n241 Warning: Power temperature sensor 1 low.
0x4396 n242 Warning: Power temperature sensor 2 low.
0x4397 n243 Warning: Control temperature sensor 1 low.
0x4398 F240 Control temperature sensor 1 low.
0x4399 F241 Power temperature sensor 1 low.
0x439A F242 Power temperature sensor 2 low.
0x439B F243 Power temperature sensor 3 low.
0x5113 F512 5V0 under voltage.
0x5117 F514 +12V0 under voltage.
0x5118 F516 -12V0 under voltage.
0x5119 F518 Analog 3V3 under voltage.
0x5180 F504 1V2 over voltage.
( Appendix 06 beginning ➔ ) Page 285

(from) AKD CANopen | 6 CANopen Drive Profile

Code Warning
0x5184 F513 +12V0 over voltage.
0x5185 F515 -12V0 over voltage.
0x5186 F517 Analog 3V3 over voltage.
0x5530 F105 Hardware memory, non-volatile memory stamp invalid.
0x5580 F106 Hardware memory, non-volatile memory data.
0x5590 F204 Control board EEPROM read failed.
0x5591 F205 Control board EEPROM corrupted serial num stamp.
0x5592 F206 Control board EEPROM corrupted serial num data.
0x5593 F207 Control board EEPROM corrupted parameter stamp.
0x5594 F208 Control board EEPROM corrupted parameter data.
0x5595 F219 Control board EEPROM write failed.
0x55A0 F209 Power board EEPROM read failed.
0x55A1 F210 Power board EEPROM corrupted serial num stamp.
0x55A2 F212 Power board EEPROM corrupted serial num data.
0x55A3 F213 Power board EEPROM corrupted parameter stamp.
0x55A4 F214 Power board EEPROM corrupted parameter data.
0x55A5 F230 Power board EEPROM write failed.
0x55A6 F232 Power board EEPROM invalid data.
0x55B0 F248 Option board EEPROM corrupted.
0x55B1 F249 Option board upstream checksum.
0x55B2 F250 Option board upstream checksum.
0x55B3 F251 Option board watchdog.
0x55B8 F252 Firmware and option board FPGA types are not compatible.
0x55B9 F253 Firmware and option board FPGA versions are not compatible.
0x55C0 F621 Control Board CRC fault.
0x55C1 F623 Power Board CRC fault.
0x55C2 F624 Power Board Watchdog fault.
0x55C3 F625 Power Board Communication fault.
0x55C4 F626 Power Board FPGA not configured.
0x55C5 F627 Control Board Watchdog fault.
0x55C6 n103 Warning: Resident FPGA .
0x55C7 n104 Warning: Operational FPGA .
0x6380 F532 Drive motor parameters setup incomplete.
0x7180 F301 Motor overheat.
0x7182 F305 Motor Brake open circuit.
0x7183 F306 Motor Brake short circuit.
0x7184 F307 Motor Brake applied during enable state.
0x7185 F436 EnDAT overheated.
0x7186 n301 Warning: Motor overheated.
0x7187 F308 Voltage exceeds motor rating.
0x7188 F560 Regen near capacity, could not prevent over voltage.


Code Warning
0x7189 F312 Brake released when it should be applied.
0x7305 F417 Broken wire in primary feedback.
0x7380 F402 Feedback 1 Analog signal amplitude fault.
0x7381 F403 Feedback 1 EnDat communication fault.
0x7382 F404 Feedback 1 illegal hall state.
0x7383 F405 Feedback 1 BiSS watchdog.
0x7384 F406 Feedback 1 BiSS multi cycle.
0x7385 F407 Feedback 1 BiSS sensor.
0x7386 F408 Feedback 1 SFD configuration.
0x7387 F409 Feedback 1 SFD UART overrun.
0x7388 F410 Feedback 1 SFD UART frame.
0x7389 F412 Feedback 1 SFD UART parity.
0x738A F413 Feedback 1 SFD transfer timeout.
0x738C F415 Feedback 1 SFD mult. corrupt position.
0x738D F416 Feedback 1 SFD Transfer incomplete.
0x738E F418 Feedback 1 power supply fault.
0x738F F401 Feedback 1 failed to set feedback.
0x7390 n414 Warning: SFD single corrupted position.
0x7391 F419 Encoder init procedure failed.
0x7392 F534 Failed to read motor parameters from feedback device.
0x7393 F421 SFD position sensor fault.
0x7394 F463 Tamagawa encoder: overheat.
0x7395 n451 Warning: Tamagawa encoder battery.
0x7396 n423 Warning: Non volatile memory error, multi-turn overflow.
0x7398 F135 Homing is needed.
0x7399 F468 FB2.Source not set.
0x739A F469 FB1.ENCRES is not power of two.
0x739B F423 Non volatile memory error, multi-turn overflow.
0x739C F467 Hiperface DSL fault.
0x739D F452 Multiturn overflow not supported with this feedback.
0x739E F465 Excessive shock detected by feedback device.
0x73A0 F453 Tamagawa encoder: communication timeout.
0x73A1 F454 Tamagawa encoder: communication transfer incomplete.
0x73A2 F456 Tamagawa encoder: communication CRC.
0x73A3 F457 Tamagawa encoder: communication start timeout.
0x73A4 F458 Tamagawa encoder: communication UART overrun.
0x73A5 F459 Tamagawa encoder: communication UART framing.
0x73A6 F460 Tamagawa encoder: over speed.
0x73A7 F461 Tamagawa encoder: contouring error.
0x73A8 F462 Tamagawa encoder: counting overflow.
0x73A9 F464 Tamagawa encoder: multiturn error.
0x73AA F451 Tamagawa encoder: battery.
0x73B0 F486 Motor velocity exceeds emulated encoder maximum speed.


Code Warning
0x73B8 F420 FB3 EnDat communication fault.
0x73C0 F473 Wake and Shake. Insufficient movement.
0x73C1 F475 Wake and Shake. Excessive movement.
0x73C2 F476 Wake and Shake. Fine-coarse delta too large.
0x73C3 F478 Wake and Shake. Overspeed.
0x73C4 F479 Wake and Shake. Loop angle delta too large.
0x73C5 F482 Commutation not initialized.
0x73C6 F483 Motor U phase missing.
0x73C7 F484 Motor V phase missing.
0x73C8 F485 Motor W phase missing.
0x73C9 n478 Warning: Wake and Shake. Overspeed.
0x73D0 F487 Wake and Shake. Validating positive movement failed.
0x73D1 F489 Wake and Shake. Validating negative movement failed.
0x73D2 F490 Wake and Shake. Validating commutation angle time out.
0x73D3 F491 Wake and Shake. Validating commutation angle moved too far.
0x73D4 F492 Wake and Shake. Validating commutation angle required more than
MOTOR.ICONT.
0x73D5 F493 Invalid commutation detected, motor accelerates in wrong direction.
0x8130 F129 Life Guard Error or Heartbeat Error.
0x8180 n702 Warning: Fieldbus communication lost.
0x8280 n601 Warning: Modbus data rate is too high.
0x8311 F304 Motor foldback.
0x8331 F524 Drive foldback.
0x8380 n524 Warning: Drive foldback.
0x8381 n304 Warning: Motor foldback.
0x8382 n309 Warning: Motor I²t load.
0x8383 n580 Warning: Using derivate of position when using sensorless feedback type
in position mode.
0x8384 n581 Warning: Zero velocity when using induction sensorless feedback type
in position mode.
0x8480 F302 Over speed.
0x8481 F703 Emergency timeout occurred while axis should disable.
0x8482 F480 Fieldbus command velocity too high.
0x8483 F481 Fieldbus command velocity too low.
0x8582 n107 Warning: Positive software position limit is exceeded.
0x8583 n108 Warning: Negative software position limit is exceeded.
0x8611 F439 Following error (user).
0x8685 F138 Instability during autotune.
0x8686 n151 Warning: Not enough distance to move; Motion Exception.
0x8687 n152 Warning: Not enough distance to move; Following Motion Exception.
0x8688 n153 Warning: Velocity Limit Violation, Exceeding Max Limit.
0x8689 n154 Warning: Following Motion Failed; Check Motion Parameters.
0x868A n156 Warning: Target Position crossed due to Stop command.
0x86A0 n157 Warning: Homing Index pulse not found.


Code Warning
0x86A1 n158 Warning: Homing Reference Switch not found.
0x86A2 n159 Warning: Failed to set motion task parameters.
0x86A3 n160 Warning: Motion Task Activation Failed.
0x86A4 n161 Warning: Homing Procedure Failed.
0x86A5 F139 Target Position Over Short due to invalid Motion task activation.
0x86A6 n163 Warning: MT.NUM exceeds limit.
0x86A7 n164 Warning: Motion task is not initialized.
0x86A8 n165 Warning: Motion task target position is out.
0x86A9 n167 Warning: Software limit switch traversed.
0x86AA n168 Warning: Invalid bit combination in the motion task control word.
0x86AB n169 Warning: 1:1 profile cannot be triggered on the fly.
0x86AC n170 Warning: Customer profile table is not initialized.
0x86AD n171 Warning: Motion task activation is currently pending
0x86AE n135 Warning: Homing is needed.
0x86AF n174 Warning: Homing maximum distance exceeded
0x86B0 F438 Following error (numeric).
0x8780 F125 Fieldbus synchronization lost.
0x8781 n125 Warning: Fieldbus synchronization lost.
0x8AF0 n137 Warning: Homing and feedback mismatch.
0xFF00 F701 Fieldbus runtime.
0xFF01 F702 Fieldbus communication lost.
0xFF02 F529 Iu current offset limit exceeded.
0xFF03 F530 Iv current offset limit exceeded.
0xFF04 F521 Regen over power.
0xFF07 F525 Output over current.
0xFF08 F526 Current sensor short circuit.
0xFF09 F128 MPOLES/FPOLES not an integer.
0xFF0A F531 Power stage fault.
0xFF0B F602 Safe torque off.
0xFF0C F131 Secondary feedback A/B line break.
0xFF0D F130 Secondary feedback supply over current.
0xFF0E F134 Secondary feedback illegal state.
0xFF0F F245 External fault.
0xFF10 F136 Firmware and FPGA versions are not compatible.
0xFF11 F101 Firmware type mismatch.
0xFF12 n439 Warning: Following error (user).
0xFF13 n438 Warning: Following error (numeric).
0xFF14 n102 Warning: Operational FPGA is not a default FPGA.
0xFF15 n101 Warning: The FPGA is a laboratory FPGA.
0xFF16 n602 Warning: Safe torque off.
0xFF17 F132 Secondary feedback Z line break.
0xFF18 n603 Warning: OPMODE incompatible with CMDSOURCE.
0xFF19 n604 Warning: EMUEMODE incompatible with DRV.HANDWHEELSRC.

(from) ©Kollmorgen – AKD Fault Card September 2016, Revision N - AKD Fault Card | 2 Fault and Warning Messages
❖ Fault and Warning Messages

When a fault occurs, the drive fault relay is opened, the output stage is switched off (motor loses all torque), or the load is
dynamically braked. The specific drive behavior depends on the type of fault. The LED display on the front panel of the drive
shows the number of the fault that occurred. If a warning is issued prior to the fault, the warning is shown on the LED and has
the same number as the associated fault. Warnings do not trip the power stage of the drive or fault relay output.
The left side of the LED displays F for a fault or n for a warning. The right side displays the fault or warning number as follows: 1-
0-1-[break]. The highest priority fault is displayed on the LED. Multiple faults may be present when a fault condition is
occurring. Check the AKD WorkBench Fault Screen or read the status of DRV.FAULTS through the controller or HMI for the
entire list of faults.
Fault Message/Warning Cause Remedy Drive
Response
to Fault
.. 1. 24V Control P ower 1. Insure adequate 24V supply N/A
input voltage dip. current capacity for the
system.
or or
2. Auxiliary encoder 5V 2. Check and fix X9 wiring.

(X9-9) shorted.
F0 Reserved. N/A N/A
F101 Firmware incompatible. Installed firmware is not Load compatible firmware into Disable
compatible with the drive the drive. power
hardware. stage
n101 The FPGA is a lab FPGA. The FPGA is a lab version Load the released FPGA version None
FPGA. that is compatible with the
operational firmware.
F102 Resident Firmware failed. Software failure detected. Restart drive. If issue persists, Disable
contact technical support. power
stage
n102 Operational FPGA is not a The FPGA minor version is Load the released FPGA version None
default FPGA. larger than the operational that is compatible with the
firmware default FPGA minor operational firmware.
version
F103 Resident FPGA failed. Software failure detected. Restart drive. If issue persists, Disable
Load resident FPGA failure contact technical support. power
occurred (several cases stage
according to flowchart,
including incompatible image
to FPGA type and fieldbus
type).
F104 Operational FPGA failed. Software failure detected. Restart drive. If issue persists, Disable
Load operational FPGA failure contact technical support. power
occurred (several cases stage
according to flowchart).

(from) AKD Fault Card | 2 Fault and Warning Messages

Response
to Fault
F105 NV Memory Stamp. Non-volatile memory Reset the drive to default Disable
stamp is corrupted or memory values using power
invalid. Parameter Load in stage
WorkBench.
F106 NV Memory Data (might Non-volatile memory data Reset the drive to default Disable
occur when downloading is corrupted or invalid. memory values using power
firmware). When this fault occurs Parameter Load in stage
after a firmware download, WorkBench.
it is not an indication of a
problem (clear the fault and
perform a “save” to the
drive).
n107 Positive switch. Positive position limit is Move the load away from the Controlled
exceeded. limits. stop
n108 Negative switch. Negative position limit is Move the load away from the Controlled
exceeded. limits. stop
F121 Homing Error. Drive did not finish homing Check homing sensor, homing Controlled
sequence. mode, and homing con figuration. stop
F123 Invalid motion task. Invalid motion task. Check motion task settings and Disable
n123 parameters to make sure that power
the values entered will produce a stage
valid motion task.
F125 Fieldbus Sync frames lost. The fieldbus lost Check fieldbus connection (X5 Controlled
n125 synchronization. and X6 if you are using EtherCAT; stop
X12 and X13 if you are using
CANopen) or the settings of your
EtherCAT or CANopen master.
F126 Bode plot too much Too much movement was Check that the system is closed Dynamic
n126 movement. created during a Bode plot. loop stable. Refer to the system braking
Motor is unstable and is not tuning guide.
following drive instructions.
F127 Incomplete Emergency Incomplete emergency stop Disconnect power from drive and Dynamic
Procedure. procedure (problem with the check emergency stop procedure. braking
emergency stop motion
task).
F128 Mpoles / Fpoles not Ratio of motor poles to Change to a compatible Disable
integer. feedback poles must be a feedback device. power
whole number. stage
F129 Fieldbus Heartbeat lost. Heartbeat lost. Check CANopen cabling. Controlled
Reduce bus load or increase stop
the heartbeat update time.
F130 Secondary feedback sup- 5V power supply was Check X9 connection. Disable
ply over current. shorted out on X9. power
stage


Response
to Fault
F131 Secondary feedback A/B Problem in secondary Check secondary feedback (X9 Disable
line break. feedback detected. connection). power
stage
F132 Secondary feedback Z line Problem in secondary Check secondary feedback (X9 Disable
break. feedback detected. connection). power
stage
F133 Fault number changed to Disable
F138. See F138 for details. power
stage
F134 Secondary feedback Feedback signals were Check X9 connection. Disable
illegal state. detected in an illegal power
combination. stage
F135 Fault on FB2 is preventing Attempt to issue motion Change opmode or home axis. Disable
n135 remote commutation for task before the axis is power
FB1. homed. Axis must be homed stage
before motion task can start.
F136 Firmware and FPGA The FPGA version does not Load the FPGA version that is Disable
versions are not match the firmware FPGA compatible with the firmware. power
compatible. version constants. stage
n137 Homing and feedback The configured homing mode Change homing mode. None
mismatch is not supported by the motor
feedback type used.
F138 Instability during autotune. Drive current (IL.CMD) or Change BODE.MODE if Controlled
velocity feedback (VL.FB) appropriate. If BODE.MODE 5 is stop
exceeds allowable limit appropriate and the fault occurs
(BODE.IFLIMIT or at the end of an Autotuning, then
BODE.VFLIMIT). This the motor is not robustly
fault only occurs in stable. You can manually adjust
BODE.MODE 5. This Autotuner settings. Manual tuning
fault often occurs when may be required to make the motor
complex mechanics, belts, stable.
and compliant loads are
present.
F139 Target position was over- The drive cannot decelerate Change Motion task profile and Disable
shot due to invalid motion from its current speed to clear fault with DRV.CLRFAULTS. power
task activation. reach the end point of the Or change the value of stage
second motion task without FAULT139.ACTION = 1 to
moving past it. Increase the ignore this condition.
deceleration rate in the move
or trigger the move earlier.


Response
to Fault
n140 VBUS.HALFVOLT has The user has changed the Save the parameters in the non- None
changed. Save the para- numerical value of volatile memory via a
meters and reboot the VBUS.HALFVOLT. This DRV.NVSAVE command and turn
drive. change only takes effect off/on the 24[V] power supply in
after a DRV.NVSAVE order to reboot the drive or restore
command and after rebooting the original stetting of
the AKD. VBUS.HALFVOLT.
n151 Not enough distance to For trapezoidal and customer Activation of any new motion or None
move; motion exception. table motion tasks: The target using of DRV.CLRFAULTS will
velocity specified in the clear the warning. Check motion
motion task cannot be task settings and parameters to
reached via using the selected make sure that the values entered
acceleration and deceleration will produce a valid motion task.
since the distance to travel is
not sufficient.
For a 1:1 profile: The selected
acceleration and deceleration
will be extended since there is
too much distance to travel
and the motion task
would exceed its maximum
allowed velocity.
n152 Not enough distance to A new motion task activated, Activation of any new motion or None
move; following motion when one motion task is using of DRV.CLRFAULTS will
exception. already active and the target clear the warning. Check motion
position specified in the motion task settings and parameters to
task parameters cannot be make sure that the values entered
reached with specified target will produce a valid motion task.
velocity, acceleration and
deceleration parameters. The
motion task will directly
decelerate to into the target
position or ramps down to
velocity 0 and start another
move to reach target position
of the next motion task.
n153 Velocity limit violation, A new target velocity Activation of any new motion or None
exceeding max limit. calculated internally due to an using of DRV.CLRFAULTS will
exception, and is being limited clear the warning. Check motion
due to user velocity limit. task target velocity settings and
parameters to make sure that the
values entered will not exceed the
VL.LIMITP and VL.LIMITN setting.


Response
to Fault
n154 Following motion failed; Activation of the following Activation of any new motion or None
check motion parameters. motion task failed due to using of DRV.CLRFAULTS will
incompatible parameters, or clear the warning. Check following
motion task does not exist. motion task settings and
parameters to make sure that the
values entered will produce a valid
motion task.
n156 Target position crossed The motion task crosses the Activation of any new motion or None
due to stop command. target position after triggering using of DRV.CLRFAULTS will
a DRV.STOP command. This clear the warning.
situation can happen when
processing a change-on-the-fly
motion task and triggering a
DRV.STOP command close to
the target position of the
currently running motion task.
n157 Homing index pulse not A homing mode with index Activation of any new motion or None
found. detection is activated, and using of DRV.CLRFAULTS will
index pulse is not detected clear the warning.
while moving across the
range determined by the
hardware limit switches.
n158 Homing reference switch A homing mode with reference Activation of any new motion or None
not found. switch detection is activated using of DRV.CLRFAULTS will
and the reference switch is not clear the warning.
detected while moving across
the range determined by the
hardware limit switches.
n159 Failed to set motion task Invalid motion task Activation of any new motion or None
parameters parameters assignment. This using of DRV.CLRFAULTS will
warning can appear upon an clear the warning. Check motion
MT.SET command. task settings and parameters.
n160 Motion task activation Activation of the motion task Activation of any new motion or None
failed. failed due to incompatible using of DRV.CLRFAULTS will
parameters, or motion task clear the warning. Check motion
does not exist. This warning task settings and parameters to
can appear upon an make sure that the values entered
MT.MOVE command. will produce a valid motion task.
n161 Homing procedure failed. Homing error observed Activation of any new motion or None
during the operation of using of DRV.CLRFAULTS will
homing procedure. clear the warning.


Response
to Fault
n163 MT.NUM exceeds limit. This warning appears with Trigger only motion tasks None
n160. This warning is between 0 and 128. Activation of
triggered when you try to any new motion or using of
trigger a motion task > 128 DRV.CLRFAULTS will clear the
(such as MT.MOVE 130). warning.
n164 Motion task is not This warning appears with Initialize the motion task first None
initialized. n160. This warning is triggered before starting the task.
when you try to trigger a non- Activation of any new motion or
initialized motion task. using of DRV.CLRFAULTS will
clear the warning.
n165 Motion task target position This warning appears with Move the absolute target None
is out. n160. This warning is position of the motion task
triggered when you try to within the modulo range.
trigger a motion task with an Activation of any new motion or
absolute target position using of DRV.CLRFAULTS will
outside of the selected clear the warning.
modulo range (see also
MT.CNTL).
n168 Invalid bit combination in This warning appears with Correct the MT.CNTL setting for None
the motion task control n160. This warning is the specific motion task.
word. triggered when you try to Activation of any new motion or
trigger a motion task with an using of DRV.CLRFAULTS will
invalid bit combination in the clear the warning.
motion task control word
(see also MT.CNTL).
n169 1:1 profile cannot be This warning appears with 1:1 profile table motion tasks None
triggered on the fly. n160. This warning is should be started from velocity
triggered when you try to 0. Activation of any new motion
trigger a 1:1 profile table or using of DRV.CLRFAULTS will
motion task while another clear the warning.
motion task is currently
running.
n170 Customer profile table is This warning appears with Change the MT.TNUM parameter None
not initialized. n160. This warning is for this specific motion task in
triggered when you try to order to use an initialized profile
trigger a motion task table. Activation of any new
that uses a customer profile motion or using of
table for generating the DRV.CLRFAULTS will clear the
velocity profile and when the warning.
selected profile table is empty
(see MT.CNTL and MT.TNUM.
F201 Internal RAM failed. Hardware failure detected. Restart drive. If issue persists, Disable
stage


Response
to Fault
F202 External RAM failed. Hardware failure detected. Restart drive. If issue persists, Disable
stage
F203 Code Integrity failed. Software failure detected. Restart drive. If issue persists, Disable
FPGA register access failure contact technical support. power
occurred. stage
F204 EEPROM failure detected EEPROM failure detected Restart drive. If issue persists, Disable
to exchange drive. power
F232 stage
F234- Temperature sensor high. High temperature limit Check cabinet ventilation Disable
F237 reached. system. power
n234- stage
n237
F240- Temperature sensor low. Low temperature limit Check cabinet ventilation Disable
F243 reached. system. power
n240- stage
n243
F245 External Fault. This fault is user generated Users can configure a digital Disable
and is caused by user input to trigger this fault power
settings. (DINx.MODE = 10). The fault stage
occurs according to this input
setting. Clear the input to clear
the fault.
F247 Vbus read is out of Hardware problem in bus Troubleshoot and repair hard- Disable
thresholds. measurement. ware problem. power
stage
F248 Option board EEPROM EEPROM failure detected. Restart drive. If issue persists, Disable
corrupted. exchange drive. power
stage
F249 Option board downstream Communications with the I/O DRV.CLRFAULTS. If issue persists Disable
checksum. on the option board failed. If issue persists, contact technical power
support. stage
F250 Option board upstream Communications with the I/O DRV.CLRFAULTS. If issue persists Disable
checksum. on the option board failed. If issue persists, contact technical power
support. stage
F251 Option board watchdog. Communications with the I/O DRV.CLRFAULTS. If issue persists Disable
on the option board failed. If issue persists, contact technical power
support. stage
F252 Firmware and option board The option board FPGA is Download the correct firmware Disable
FPGA types are not not compatible with this file for this drive. power
compatible. hardware. stage
F253 Firmware and option board The version of the option board Download the correct firmware Disable
FPGA versions are not FPGA is not compatible with file for this drive. power
compatible. this firmware. stage


Response
to Fault
Analog Input over voltage The analog input value is Check the analog input signal or Controlled
F256
above the AIN.OVFTHRESH change the AIN.OVFTHRESH Stop
level. value.
F257 Analog Input under voltage The analog input value is Check the analog input signal or Controlled
below the AIN.UVFTHRESH change the AIN.UVFTHRESH Stop
level. value.
n256 Warning: Analog Input over The analog input value is Check the analog input signal or None
voltage above the AIN.OVWTHRESH change the AIN.OVWTHRESH
level. value.
n257 Warning: Analog Input The analog input value is Check the analog input signal or None
under voltage below the AIN.UVWTHRESH change the AIN.UVWTHRESH
level. value.
F301 Motor overheated. Motor overheated. Check ambient temperature. Disable

n301 Check motor mounting heat power
sink capability stage
F302 Over speed. Motor exceeded Increase VL.THRESH or lower Dynamic
VL.THRESH value. velocity command. braking
F303 Run away. Motor did not follow Current command to the motor Controlled
command values. is too high for too long. Reduce stop
servo gains, or reduce command
trajectory aggressiveness.
F304 Motor Foldback. Maximum motor power has Motion is requiring too much Controlled
n304 been exceeded; the power power. Change move profile to stop
has been limited to protect reduce load on motor. Check for
the motor load jamming or sticking.
Check that current limits are
set correctly.
F305 Brake open circuit. Motor brake open circuit. Check cabling and general Dynamic
Fault threshold is 200 mA. functionality. For special low braking
current brake applications, the
F305 fault can be bypassed using
the setting motor.brake = 100.
F306 Brake short circuit. Motor brake short circuit. Check cabling and general Dynamic
functionality. Check that braking
MOTOR.TBRAKERLS and
MOTOR.TBRAKEAPP are
configured.
F307 Brake applied during Motor brake closed Check cabling and general Dynamic
Enable-State. unexpectedly. functionality. braking
F308 Voltage exceeds motors Drive bus voltage exceeds Make sure that the motor fits Disable
rating. the motor’s defined the driving rating. power
voltage rating. stage


Response
to Fault
n309 Motor I2t load. reduce load Motor I2t load (IL.MI2T) has Reduce the load of the drive by None
exceeded the warning adjusting lower acceleration /
threshold IL.MI2TWTHRESH. deceleration ramps.
This warning can only be
generated in the case that the
motor protection mode
IL.MIMODE has been set to 1.
F312 Brake released when it Brake disengaged Check cabling and general Controlled
should be applied. unexpectedly. functionality. stop
F401 Failed to set feedback Feedback is not connected Check primary feedback (X10 Dynamic
type. or wrong feedback type connection). braking
selected
F402 Analog signal amplitude Analog signal amplitude is Check primary feedback (X10 Dynamic
fault. too low. Analog fault connection), resolver and sine/cos braking
(resolver signal amplitude or encoder only.
sin/cos amplitude)
F403 EnDat communication General communication Check primary feedback (X10 Dynamic
fault. problem with feedback. connection), EnDat only. If braking
feedback is linear, check
calibration.
F404 Illegal Hall state (111, Hall sensor returns invalid Check the feedback wiring; check Dynamic
000). Hall state (111, 000); either all feedback connectors to ensure braking
all Hall sensors are on or off. all pins are positioned correctly.
Legal Hall states are 001,
011, 010, 110, 100,
and 101. This fault can be
caused by a broken
connection in any one of the
Hall signals.
F405 BiSS watchdog fault. Dynamic

Bad communication with the Check primary feedback (X10 braking
F406 BiSS multi cycle fault.
feedback device. connection), Biss only.
F407 BiSS sensor fault.
F408- SFD feedback fault. Bad communication with the Check primary feedback (X10 Dynamic
F416 SFD device. connection).If fault persists, braking
internal feedback failure.
Return to manufacturer for
repair.
F417 Broken wire in primary In primary feedback, a broken Check feedback cable Dynamic
feedback. wire was detected continuity. braking
(incremental encoder signal
amplitude).
F418 Primary feedback power Power supply fault for Check primary feedback (X10 Dynamic
supply. primary feedback. connection). braking


Response
to Fault
F419 Encoder init procedure Phase find procedure did not Check encoder wiring, Disable
failed. complete successfully. reduce/balance motor load prior power
to phase finding. stage
F420 FB3 Endat communication A communication error Check pinout and FB3 Dynamic
fault. was detected with the configuration and reconnect braking
EnDat 2.2 device connected feedback. If problems persist,
to the X9 connector. contact customer support.
F421 SFD resolver sensor fault. Sensor or sensor wiring Try resetting the fault. If it Dynamic
failure inside motor. reappears return motor for braking
repair.
F423 NV Failure – Extended The position saved in Home axis or disable extended Disable
Multi-turn. memory is corrupted. multi-turn. If the fault persists, power
send the drive for repair. stage
F438 Deviation from predicted Motor did not follow command Check for increased load, Controlled
n439 trajectory fault. values. Motor exceeded jamming or sticking. Is position stop
maximum allowed position error set too low?
following error (numeric).
F439 Following error magnitude Motor did not follow command Check feedback commutation Controlled
n439 fault. values. setup and tuning parameters. stop
Motor exceeded maximum
allowed position following error
(user).
F450 Following error Motor did not follow command Check feedback commutation Controlled
presentation. values. Motor exceeded setup and tuning parameters. stop
maximum allowed position
following error (presentation).
F451 Feedback battery fault. The external battery voltage is Check or replace the external Dynamic
n451 too low. The F451 fault is battery. braking
generated if the AKD is not
powered. The n451 warning is
generated if the AKD is
powered. This fault can be
inhibited with
FAULT451.ACTION.
F452 Extended Multi-turn not Non-multi-turn feedback is Connect multi-turn feedback to Disable
supported with this connected while the drive or disable extended power
feedback. FB1.PMTSAVEEN is active. multi-turn. stage


Response
to Fault
F453 Tamagawa communication
fault (timeout).
fault (transfer incomplete).
F456 Tamagawa communication Bad communication with the Check the cabling to the drive and
fault (CRC). feedback device. if the problem persists then Dynamic
F457 Tamagawa communication Cabling or shielding fault, or return the feedback to the braking
fault (start timeout). internal feedback failure. manufacturer for repair.
fault (UART Overrun).
fault (UART Framing).
F460 Tamagawa encoder fault This fault is generated when Reset the fault on the drive with Dynamic
(over speed). the shaft is rotated above a DRV.CLRFAULTS. braking
maximum speed that can be
maintained while the external
battery is powered and the
drive is powered off.
F461 Tamagawa encoder fault When the feedback is Reset the fault on the drive with Dynamic
(counting Error). powered on the position DRV.CLRFAULTS, if the problem braking
(within one revolution) was persists then clean the feedback
incorrect because of a code plate.
problem with the feedback
device.
F462 Tamagawa encoder fault Multi-turn counter has Reset the fault on the drive with Dynamic
(counting overflow). overflowed. DRV.CLRFAULTS. braking
F463 Feedback overheat fault. The temperature of the encoder Reset the fault on the drive with Dynamic
substrate exceeds overheating DRV.CLRFAULTS after braking
detection temperature during temperature of encoder is lowered.
main power-on.
F464 Tamagawa encoder fault Any bit-jump occurs in the Return to the origin. Reset the Dynamic
(multi-turn error). multi-turn signal during main fault on the drive with braking
power-on. DRV.CLRFAULTS.
F465 Excessive shock detected 1. Excessive shock from an 1. Reduce external impacts to Dynamic
by feedback device. impact or vibration has caused the motor housing and shaft. braking
an error in the feedback device. Tune the control loops filters.
Reduce gains, particularly feed
or
forward gains. Reduce maximum
2. Internal error in the commanded acceleration.
feedback device
or
mechanism, resulted in bad
position data. 2. Replace the feedback
device.


Response
to Fault
F467 Feedback fault on The feedback device mal- Check FB1.FAULTS for Dynamic
feedback 1 (See FB1.FAULTS functioned. detailed fault information. braking
for details). If using a BiSS feedback device,
fault 467 indicates a
communications fault with the
BiSS feedback device. No
additional information is available
via FB1.FAULTS for this fault when
using a BiSS feedback device.
F469 FB1.ENCRES is not power of Feedback Type 43 requires If the remote feedback device's Dynamic
two, Remote Commutation that the feedback resolution resolution is a power of two, enter braking
not possible. be a power of two. Feedback that value in FB1.ENCRES.
Type 43 is not supported for Otherwise, choose a feedback
all feedback resolutions. device with a supported
resolution (power of two) and
enter that value in FB1.ENCRES.
F470 Feedback fault on Feedback is not connected Check tertiary feedback (X9 Dynamic
feedback 3. or general communication connection) braking
problem.
F473 Wake and Shake - There was less movement Increase WS.IMAX and/or Disable
Insufficient movement than defined by WS.T. Or try using power
WS.DISTMIN. WS.MODE 1 or 2. stage
F475 Wake and Shake - Excess WS.DISTMAX has been Increase WS.DISTMAX value or Disable
movement exceeded in reduce WS.IMAX or WS.T. Wake power
WS.MODE 0. Or more than and Shake is not supported for stage
360 degrees was traveled in vertical/overhung loads.
WS.MODE 2.
F476 Wake and Shake - Fine- The angle difference Modify WS.IMAX or WS.T and try Disable
Coarse delta too large. between the coarse and fine again. power
calculation was larger than stage
72 deg.
F478 Wake and Shake - Over WS.VTHRESH was Increase WS.VTHRESH value or Disable
n478 speed exceeded. reduce WS.IMAX or WS.T. power
stage
F479 Wake and Shake - Loop The angle between complete Modify WS.IMAX or WS.T and try Disable
n479 angle delta too large. loops was larger than 72 deg. again. power
stage
F480 Field bus command Fieldbus command velocity Lower fieldbus command Disable
velocity too high. exceeds VL.LIMITP. trajectory, or increase the value of power
VL.LIMITP. stage
F481 Field bus command Fieldbus command velocity Increase fieldbus command Disable
velocity too low. exceeds VL.LIMITN. trajectory, or decrease the value of power
VL.LIMITN. stage


Response
to Fault
F482 Wake and Shake - The motor requires the Clear any faults, activate the Disable
Commutation not commutation initialization Wake and Shake procedure power
initialized. (there are no encoder (WS.ARM) and enable the stage
commutation tracks, Hall drive.
sensors, etc.) and no successful
Wake and Shake sequence has
been performed
F483 Wake and Shake - Motor U No current was detected in Check the motor connections and Disable
phase missing. the motor's U phase during WS.IMAX (very low current may power
Wake and Shake initialization produce this error). stage
(Mode 0 only).
F484 Wake and Shake - Motor V No current was detected in Check the motor connections and Disable
phase missing. the motor's V phase during WS.IMAX (very low current may power
(Mode 0 only).
F485 Wake and Shake - Motor No current was detected in Check the motor connections and Disable
W phase missing. the motor's W phase during WS.IMAX (very low current may power
(Mode 0 only).
F486 Input change rate exceeds Motor velocity exceeds the Reduce value of Controlled
maximum speed of maximum speed the DRV.EMUEPULSEWIDTH. stop
emulated encoder. emulated encoder output can
generate.
F487 Wake and Shake - Validating After applying a positive Check motor phase wiring and Disable
Positive Movement Failed. current, motor moved in the motor encoder wiring is correct. power
wrong direction. stage
F489 Wake and Shake - Validating After applying a negative Check motor phase wiring and Disable
Negative Movement Failed. current, motor moved in the motor encoder wiring is correct. power
wrong direction. stage
F490 Wake and Shake - Validating During one of the W&S Contact customer support. Disable
Comm. angle timed out. validation stages, the drive power
stopped responding to stage
commands.
F491 Wake and Shake - Validating After applying a current, the This indicates a poor motor Disable
Comm. angle moved too far motor moved too far (>15 phase angle was found by Wake power
- Bad Comm Angle. electrical degrees). and Shake. Revise Wake and stage
Shake parameters, and re-run
Wake and Shake.


Response
to Fault
F492 Wake and Shake - Validating A current larger than This indicates one of the Disable
Comm. angle required more MOTOR.ICONT was following: power
than MOTOR.ICONT used to excite the motor. stage
l Phaseangleisincorrect
dueto a badwake and
shake.
l Motorhas very high
frictionrequiring high
current to break free.
l Motorpowercableis
disconnected or
improperly wired.
F493 Invalid commutation The velocity of the motor 1. Check motor phase wiring Dynamic
detected - motor exceeded WS.CHECKV and 2. Re-configure wake and braking
accelerating in the wrong the sign of the current was not shake (if Mode 0 or 1 is used)
direction. Motor phase may equal to the sign of motor
be incorrect. acceleration or the sign of 3. Re-run wake and shake to
motor velocity for a period of determine correct commutation
time larger than WS.CHECKT. angle
F501 Bus over voltage. Bus voltage too high. Reduce load or change motion Disable
n501 Usually, this problem is load profile. Check system regen power
related. capacity; add capacity if needed. stage
Check mains voltage.
F502 Bus under voltage. Bus voltage below Check mains voltage. Controlled
Warning issued prior to threshold value. stop
fault.
F503 Bus capacitor overloaded. Single phase AC input on a Check mains voltage. Controlled
n503 drive only rated for three- stop
phase input or excessive
single-phase power load.
F504- Internal supply voltage Internal supply voltage Check wiring for electromagnetic Controlled
F518 fault fault detected compatibility (EMC). If issue stop
persists exchange drive.
F519 Regen short circuit. Regen resistor short circuit. Regen IGBT short circuit. Disable
Contact technical support. power
stage
F521 Regen over power. Too much power stored in Either get larger regen resistor Disable
n521 regen resistor. or use DC bus sharing to power
dissipate power. stage
F523 Bus over voltage FPGA. Bus over voltage hard Check mains voltage and check Disable
fault. system brake capacity. power
stage


Response
to Fault
F524 Drive Foldback. Maximum drive power has Motion requires too much Controlled
n524 been exceeded. The power power. Change profile to stop
has been limited to protect reduce load .
the drive.
F525 Output over current. Current exceeds drive Check for short or feedback Disable
peak. faults. power
stage
F526 Current sensor short circuit. 1. Current sensor short 1. Restart drive. If issue persists, Disable
circuit. contact technical support. power
2. Motor cable plugged in 2. Plug in cable right-side up. stage
upside down
F527 Iu current AD converter Hardware failure detected. Restart drive. If issue persists, Disable
stuck. contact technical support. power
stage
F528 Iv current AD converter Hardware failure detected. Restart drive. If issue persists, Disable
stuck. contact technical support. power
stage
F529 Iu current offset limit Hardware failure detected. Restart drive. If issue persists, Disable
exceeded. contact technical support. power
stage
F530 Iv current offset limit Hardware failure detected. Restart drive. If issue persists, Disable
exceeded. contact technical support. power
stage
F531 Power stage fault. Hardware failure detected. Restart drive. If issue persists, Disable
replace drive. power
stage
F532 Drive motor parameters Before a motor can be Issue the command Disable
setup incomplete. enabled, you must configure a DRV.SETUPREQLIST to display power
minimum set of parameters. the list of the parameters that stage
These parameters have not you must configure. Configure
been configured. these parameters either
manually or automatically. You
can manually configure these
parameters in three ways: (1) set
each parameter individually; (2)
use the setup wizard to select
the motor; or (3) select the
motor type from the motor data
base in the Motor window
(MOTOR.AUTOSET must be set
to 0 (off)). If you use the Motor
window, you must first select
the feedback type. If the motor
has Biss Analog, Endat, or SFD
feedback (feedback with
memory), then these parameters
are set automatically when
MOTOR.AUTOSET is set to 1
(on).


Response
to Fault
F534 Failed to read motor Motor either does not have Try to read parameters again by Dynamic
parameters from feedback motor feedback memory, or clicking the Disable and Clear braking
device. the motor feedback memory Faults button, or by issuing the
is not programmed properly DRV.CLRFAULTS command. If
so the parameters cannot this attempt is not successful,
be read. then set MOTOR.AUTOSET to 0
(off) and program the parameters
using the setup wizard or
manually set up the parameters. If
the motor has motor memory
(Biss Analog, Endat, and SFD
motors have motor memory),
return the motor to have the
memory programmed.
F535 Power-board over- The power-board temperature Reduce the load of the drive or Disable
temperature fault. sensor indicates more than 85 ensure better cooling. power
°C. stage
F536 Standby power supply Standby voltage circuit Check total 24 V power load of Disable
fault. overloaded. AKD-N in the strings (sum of Drives
drive and motor brake supply).
The AKD-C must be power-
cycled to recover from this fault.
F537 Precharge fault. Precharge process could not Look for a shortcut in the string Disable
be performed in a reasonable (cable) or exchange hardware Drives and
amount of time. Unpower
Strings
F541 AC input phase 1 missing. Mains supply failure Check power connector and Disable
detected, phase L1 power source. Drives and
missed. Unpower
Strings
missed. Unpower
Strings
missed. Unpower
Strings


Response
to Fault
F545 String current over peak String current is higher Lower AKD-N current limits to Disable
limit than AKD-C Rated Peak prevent overdrawing AKD-C Drives and
Current. cur rent Unpower
Strings
F546 String current over String current is higher Lower AKD-N current limits to Disable
continuous limit than AKD-C Rated prevent overdrawing AKD-C Drives and
Continuous Current (I²T). cur rent Unpower
Strings
F560 Regen near capacity, An F501 Bus Over Voltage has Increase the size of regen Disable
could not prevent over occurred while the Regen resistor to be able to dissipate power
voltage. Resistor was at or above 75% more power. stage
of its dissipation capacity.
F561 More than 8 AKD-Ns Too many drives on Reduce NSDs on String 2 to 8 Disable
connected at string2 string 2. or less Drives and
Unpower
Strings
F562 More than 8 AKD-Ns Too many drives on Reduce NSDs on String 1 to 8 Disable
connected at string1 string 1. or less Drives and
Unpower
Strings
F564 Number of connected Drive has been removed Investigate AKD-N Ethercat Disable
nodes on string 1 has from string 1. communication, determine Drives and
decreased. where network connection Unpower
failed. Strings
F565 Number of connected Drive has been removed Investigate AKD-N Ethercat Disable
nodes on string 2 has from string 2. communication, determine Drives and
decreased. where network connection Unpower
failed. Strings
F570 Phase loss. Phase loss detected. Check mains power voltage. Disable
Fault action configurable by power
FAULT570.ACTION. stage
n582 Velocity has been limited Motor Velocity has Refer to ECCN 3A225 Velocity
commutation speed to less exceeded the allowed Limitations for Induction command
than 600Hz to meet ECCN commutation speed Motors. will be
3A225 requirements. (599Hz). clamped at
ECCN
3A225
regulation.
n601 Modbus data rate is too Modbus controller data rate Reduce data rate. Disable
high. is too high. power
stage
F602 Safe torque off. Safe torque off function has Reapply supply voltage to STO if Disable
been triggered. safe to do so. power
stage


Response
to Fault
n603 OPMODE incompatible This warning is generated Select a different DRV.OPMODE Disable
with CMDSOURCE when the drive is enabled and andDRV.CMDSOURCE power
the gearing command source is combination. stage
selected at the same time as
torque or velocity opmode.
n604 EMUEMODE incompatible Emulated encode mode is Select a compatible emulated Disable
with incompatible with the encode mode or change power
DRV.HANDWHEELSRC. selected handwheel source. handwheel source. stage
F621 Control Board CRC fault.

F623 Power Board CRC fault.
F624 Power Board Watchdog
fault.
Disable
F625 Power Board Communications with the DRV.CLRFAULTS. If issue persists,
power
Communication Power Board Failed contact technical support.
stage
F626 fault.
Power Board FPGA not
configured.
F627 Control Board Watchdog
fault.
F628 AKD-C Front door packet A data packet has not been Check cables and clear the Disable
not received on String 1. received by the AKD-N or AKD- fault. Drives and
C (String 1) Unpower
Strings
F629 AKD-C Front door packet A data packet has not been Check cables and clear the Disable
not received on String 2. received by the AKD-C (String fault. Drives and
2) Unpower
Strings
F630 FPGA cyclic read fault. FPGA-to-firmware data DRV.CLRFAULTS. If issue Disable
access error. persists, contact technical Power
support. Stage
F701 Fieldbus Runtime. Runtime communication Check fieldbus connections Controlled
fault. (X11), settings, and control stop
unit.
F702 Fieldbus Communication All fieldbus Check fieldbus connections Controlled
n702 lost. communication was lost. (X11), settings, and control stop
unit.
F703 Emergency timeout Motor did not stop in the Change timeout value, change Disable
occurred. timeout defined. stop parameters, improve tuning. power
stage

(from) AKD Fault Card | 3 Additional fault messages AKD-T
❖ Additional fault messages AKD-T

AKD BASIC runtime faults are displayed in the two-digits 7-segment display of the drive:
The two digits LED display

indicates the fault code.
The additional runtime fault messages for AKD-T are coded with numbers starting from F801.
Remedy for all errors: clear error, fix user program, recompile, download and attempt to run the program again.
Error Description Cause

F801 Divide by zero. User Program attempted to divide by zero.
F802 Stack Overflow. User Program contains an infinite recursion or incorrectly array.
F803 Insufficient Memory. User program creates an excessive demand for memory.
F804 No interrupt handler defined. User program is missing an interrupt service routine, but an interrupt
is called.
F805 Interrupt error. User program contains an error in an interrupt routine.
F806 Max string length exceeded. User program attempted to use a string exceeding 255 characters.
F807 String overflow. User program has a exception causing excessive string usage.
F808 Array out of bounds. User program exception caused an array to exceed its bounds.
F809 Feature not supported. User program contains a feature that the current firmware version
does not support.
F810 Internal firmware/hardware error. User program attempted to perform an action that causes a firmware
or hardware error.
F812 Parameter not supported. User program calls a parameter that is not supported by the firmware.
F813 Parameter access error. User program contains a parameter access error.
F814 Data not found. User program attempted writing an invalid recorder parameter.
F815 Data invalid. User program attempted executing an invalid command.

F816 Data too high. User program contains a parameter that is above the accepted range.
F817 Data too low. User program contains a parameter that is below the accepted range.
F818 Param type out of range. User program attempted to write a value which was out of a range.
F819 Data not divisible by 2. User program executed a function that requires it to be divisible by two.
F820 Invalid position modulo setting. User program contains an incorrectly configured modulo setting.
(from) AKD Fault Card | 3 Additional fault messages AKD-T

Error Description Cause

F821 Cannot read from command. User program attempted to perform a read of parameter that is a
command or statement.
F823 Enable Drive first. User program is attempting to execute motion that requires the drive
to be enabled.
F824 DRV.OPMODE must be 2 (position). User program is attempting to execute motion that requires the drive
to be in program mode.
F825 DRV.CMDSOURCE must be 5 User program is attempting to execute motion that requires the drive
(program). to be in position mode.
F826 Cannot execute during a move. User program is attempting an invalid execution during a move.
F827 Writing to read-only parameter. User program attempted writing to a read-only parameter.
F828 Disable Drive first. User program tries to execute a function that requires a disabled drive.
F829 Opcode not supported - upgrade User program contains unsupported Opcode.
firmware.
F830 No negative values allowed. User program uses illegal negative value.
F831 BASIC program is invalid. May User program contains invalid c
need firmware upgrade.
F832 BASIC program is missing. User program is missing.
F901 Too many cams. User program contains too many cams.

End of the Publication

You have reached the end of this Publication.
www.gehealthcare.com
Page 310

Discovery RF180 Troubleshooting Guide Table - SM - 5793731-1EN - 8

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Discovery RF180 Troubleshooting Guide Table - SM - 5793731-1EN - 8

Uploaded by

Copyright:

Available Formats

GE Healthcare Discovery RF180

5793731-1EN, Rev. 8 Troubleshooting Guide Table

Troubleshooting Guide Table

This page is blank.

Revision Date Reason for change

1 May 2018 Initial Release - Released version

Manufacturer: GENERAL MEDICAL MERATE S.p.A.

Distributor : GE Medical Systems, SCS

Troubleshooting guide - Index

Errors of "Tri-Phase" CPU card Codes 02 04 ccccc page 8

Warning messages of Tilting Table Codes 02 20 ccccc page 170

Errors & Warning related to “Stitching” Codes 02 50 ccccc page 189

Appendix 06 – Brushless Drivers error codes page 284

o Column longitudinal motor driver Codes 02 00 ccccc

Tilting Table Troubleshooting guide

The code is composed by three fields, displayed as: “SS-DD-CCCCC”.

SS is the subject (the entity) that generates / reports the error.

SS = 00 ➔ Subject = DLL (reference: 5793730-1EN TSG - Digital)

(TSG Index ➔) Page 5

Error Code Error source Notes

Error Code Error source

(TSG Index ➔) Page 6

❖ About the tables on the following pages:

(TSG Index ➔) Page 7

"T" CPU card (Clisis Main Card) related Errors

• Check Elevation Driver Power supply during “init

• If all the above test / values are correct, Change the

(TSG Index ➔) Page 8

• Check Column Longitudinal Driver Power supply

• If all the above test / values are correct, Change the

(TSG Index ➔) Page 9

• Check SFD Longitudinal Driver Power supply during

• If all the above test / values are correct, Change the

(TSG Index ➔) Page 10

EEProm CRC Error • Recalibrate (see service manual - code 5793727-1EN)

• Recalibrate (see service manual - code 5793727-1EN)

(TSG Index ➔) Page 11

• Check Driver’s CAN line. See appendix 05 In case of this

(TSG Index ➔) Page 12

In case of this error

(TSG Index ➔) Page 13

• Check CAN_GND line. See appendix 01

(TSG Index ➔) Page 14

(TSG Index ➔) Page 15

(TSG Index ➔) Page 16

The system “sense” that the contactor is feeding power to

➢ In case TRL2 is “OFF”, check the fuse F13 and / or verify

(TSG Index ➔) Page 17

(TSG Index ➔) Page 18

• In case the behavior of LD72 it is correct, change the

• In case LD4 is remains “OFF”, disconnect also CN136. If

(TSG Index ➔) Page 20

(TSG Index ➔) Page 21

In case of this error

(TSG Index ➔) Page 22

• Recalibrate (see service manual - code 5793727-1EN )

• If the above doesn’t solve the problem, check Column

If, after the above operations, the error is still present,

(TSG Index ➔) Page 23

• Check if other errors related to Column and/or SFD

(TSG Index ➔) Page 24

The system “sense” that the relay is feeding power to the

• Check the status of the relay RL4.