BV Faultfinding Manual
BV Faultfinding Manual
BV Faultfinding Manual
NEWSLETTER Service
Issued by : GXR Best Reference No. : XRD-Best 305
Publication No. : 4522 981 62981 Date : November 2008
Information for :
FSE X-ray Surgery Surgery Specialist
APPLIES TO:
This newsletter applies to the BV Family R.2.X. systems.
SUMMARY
The main purpose of this document is to address the newly released FCO’s published in 2008. These FCO’s
are focusing on solutions for a number of error codes (Error, 206, 327, 343, 393 and other messages which
can be found in the system logfile) and image quality problems like pixilated images and lines across the
image. These problems are mainly release 2.X system based. The workflow explained in this document could
greatly reduce the problems in the field related to error codes listed in this document and the image quality
problems.
NOTE: This document will not address problems related to the generator, battery (ESU), DFI and collimator.
The system faults in a BV Family release 2 system can be distinguished into 3 categories:
1. Errors indicated by error messages on the system.
2. Distorted images.
3. Other system faults (not described in the standard BV Family R2 service manuals).
Some system error messages reported on the C-Arm stand (SUCO) are explained in chapter 2.
When the system (C-arm stand) generates no error messages, and when distorted images are observed refer
to chapter 3.
SUMMARY .........................................................................................................................................................1
INTRODUCTION ................................................................................................................................................3
1.1 Abbreviations & terms..............................................................................................................................3
1.2 Overview of released FCO’s....................................................................................................................3
1.3 Schematic overview of the system ..........................................................................................................4
1.4 How to find and handle error messages..................................................................................................6
1.5 Error messages on the C-arc stand display ............................................................................................6
3 IQ COMPLAINTS ..................................................................................................................................19
3.1 Camera Test pattern..............................................................................................................................20
3.2 Stand MVS cable failure ........................................................................................................................22
3.3 C-arc cable failure..................................................................................................................................23
3.4 Auto Contrast Brightness artefacts........................................................................................................27
3.5 Movement ..............................................................................................................................................29
3.6 Movement distortion in subtracted images ............................................................................................29
3.7 “Dirty Noise” ...........................................................................................................................................29
3.8 Digital Exposure.....................................................................................................................................30
Please refer to the Service Manual Corrective Maintenance (SMCM) when a DFI error occurs.
Error messages on the C-arc stand display are generated by the SUCO or SCPU processor.
To identify an error:
1. Press <INFO> on the C-arc stand. A list of errors appears that occurred around the same point in
time. The first error in the list is probably the cause of the other errors.
2. Connect Service PC to the Service Ethernet port of the MVS.
3. Restart the system on the MVS.
4. In the setup panel of the MVS: select Enable service.
5. Startup BV-Scope on the Service PC.
6. Enter the Service IP-address from the system in BV-Scope.
7. In BV-Scope select: Faultfind > Logging > Logfile Complete System.
8. Save the logfile with the Serial number of the system and with the extension txt. (e.g. FK259.txt). To
do so, press the SAVE button in BV-Scope and change “logging.txt” to systemserialnumber.txt as
described above.
9. Open the logfile with Notepad.
10. Start the search function. Press <CTRL>+<F>
11. Fill in the parameters from table 5 (below) into the search window, press Find Next, exit the search
window by pressing <esc> and press F3 (next).
12. When one or more error(s) is/are found refer to the relevant FCO’s to solve the problem.
NOTE: when following this sequence it’s easier to search for errors in the logfile.
NOTE:
Error 0 in the logfile does not mean a real error occurred in the system, but a message from the system. The
error can be caused by the key switch (X-ray disabled) or after fluoroscopy longer then 5 minutes.
For faultfinding Error 0 can be ignored.
Error 371 refers to a malfunction of the oil pump of the monoblock(xray tank). When this error pops up
occasionally, it is caused by mis-communcation between the units. In these cases also this error can be
ignored.
2.1.2.2 Solution
Check the system for other errors and first solve these. Most likely afterwards the system will operate without
these errors.
Note the time gap between 08-04-25 08:55:36 and 08-04-25 08:59:10. Over here the customer has waited for
3.5 minutes before giving a restart to the system. During this time the system logfile did not record any action.
2.1.3.2 Solution
For this issue perform FCO71800027. Install software rel 2.2.6 (SUCO systems), this bug is already solved in
all 2.3 SCPU releases.
2.2.1 Error 393 in combination with message “unreliable IDS Link detected”.
This is caused by an incorrect stand-MVS cable and / or the interconnection between SA-X1 pin S and T and
the SHA 3 board.
2.2.1.2 Solution
Replace the Stand-MVS cable and the interconnection between SA X1 (pin S and T) and the SHA3 board as
mentioned in FCO 718 00 024.
2.2.2.2 Solution
Replace the Stand-MVS cable and the interconnection between SA X1 (pin S and T) and the SHA3 board as
mentioned in FCO 718 00 024.
2.2.3.2 Solution
Check the Knova tip regarding this issue. It will be updated on a regular basis. Look in Knova for the
searchstring “error 393 at first fluoro”. A definitive solution is still under investigation by PMG Best.
2.2.4.2 Solution
See step 1 till 4 as described in the log file above for faultfinding on this issue in the R2.3 systems.
2.3.1.2 Solution
Check camera, Camera Interface board and interconnections. In case all this is correct replace the c-arc
cable. Additional information can be found in FCO71800017. Before replacing the C-arc cable use the pre-
check FCO C-arc cable replacement document, listed on Incenter at FCO71800030 (452298162991) to check
the C-arc cable for its status.
Note in the last line with the message “error 206 resolved”
06-08-09 14:31:25 W IP intErrAtrFrameLost
06-08-09 14:31:27 M SYS rec ABORT XRAY from PMI_pack
06-08-09 14:31:27 N<PMI CAMLINK not OK triggers an emergency stop of the Timing Control Board !
06-08-09 14:31:27 F<PMI Performing emergency stop Timing Control Board !
06-08-09 14:31:27 W<PMI Error 206
06-08-09 14:31:27 M SYS rec ABORT XRAY from SYS_pack
06-08-09 14:31:27 M SYS rec BLOCK XRAY, PMI block cnt: 1, block cnt sum: 1
No camlink OK signal detected between IDS and
Timing Control Board. Check IDS subsystem and cabling.
06-08-09 14:31:46 W IP Exclusion levels timing error
06-08-09 14:31:46 W IP intErrAtrFrameLost
06-08-09 14:31:47 W<PMI Error 206 resolved
2.3.2.2 Solution
Use the pre-check FCO C-arc cable replacement document, listed on Incenter at FCO71800030
(452298162991) to check the C-arc cable for its status. If necessary replace the c-arc cable.
Error M327 shows up after startup. Error M326 becomes visible by activating the info button. Both errors can
also be found in the error log file. A restart usually fixes the problem. The problem only occurs during the
startup phase of the system. It will not occur during normal operation.
The root cause of the problem is an incorrect initialization of an ADC circuit on XGC Pulse board.
2.4.1.3 Solution
Replace the SHA4 generator control board according FCO 718 00 018
2.5.1.2 Solution
Perform the procedure mentioned in FCO 71800021.
In case the shutdown was not performed in a controlled way (as described above) the line
”W IP IdsLnkStatus changed from LINK_PRESENT to NO_LINK” is missing before the line “W INI Warning:
no msg received within GUARDING_WARNING time”
in the logging.
2.6.3.1 Logging example in case of C-arc stand reboot when using the remote control:
2.6.3.2 Solution
This problem will be solved by installing software release 2.2.4. (Refer to mandatory FCO 71800022),
superseded by software release 2.2.6 (refer to action for performance proactive FCO 71800027). Software
2.2.6. is not compatible with the 3DRX system, use 2.2.4. on these systems.
In rel 2.2.4 systems it is possible the logging does not function correctly.
BV-Scope
Click here to proceed to end of logging
[System ID Header]
System type : BV Pulsera-12"
System serial number : FK00996
SW Release : R2.2.4
Hospital name : PHILIPS HEALTHCARE
There was an error during ....
Click here to proceed to start of logging
2.7.1.2 Solution
This problem will be solved by installing software release 2.2.6 (refer to FCO’s 718 00 027 (SuCo) and
718 00 029 (SCPU)). With the installation of the SW rel 2.2.6 (SCUO) or SW rel 2.3.3 (SCPU) the system log
file will be reset automatically.
This chapter describes which steps to take when a customer complains about Image Quality (IQ) being
unsatisfactorily without a clear technical cause. Additionally no error message is displayed on the system. In
such a case you can check if the IQ issue can be recognized as a failure caused by one of the following
known cases:
• Stand MVS cable failure
• C-arc cable failure
• Auto Contrast Brightness artefacts
• Movement
• Incorrect use of Digital Exposure
If the cause of the IQ problem can be explained by one of the above specified situations, the cause and
solution can be will be clarified within this document.
If the cause of the IQ problems does not meet the one of the above specified examples, this document
describes some further checks and test which may lead to a solution. In case no clear failure cause can be
isolated or doubts remain, you’re advised to contact your Tier 2 helpdesk
The images in this document are best viewed as a digital document, IQ problems are difficult to see on black
and white prints.
NOTE
No X-ray will be generated during this test.
________
4. Check for image disturbance caused by play on the stand-trolley plug and cable but leave it connected to
the system.
5. Bend and move the cabling of the IDS-link connection inside the C-arc stand.
(For systems with a TCB-2 this is the connection between SHA3-X4 and the wired bracket SAX-1. In
case of a TCB-3D this is a round connector on SHA3-X5)
6. Check if the gray values are distorted on the camera test image during this action. (see examples of the
camera test image below)
7. If necessary replace the wired bracket SAX-1 or TCB2/TCB3 adapter cable and stand-trolley cable
(FCO71800024) if one or more of these items are suspected to be defect or worn.
A correct test pattern shown on the monitor should have the following characteristics:
• 16 grey levels visible in the upper and lower bar.
• In the middle a transition (in 32 steps) from black to white is visible.
Additionally one can check the system log-file on the appearance of “unreliable IDS link” and/or “error M393”.
3.2.1 Solution:
Perform Mandatory FCO 718 00 024.
Image with stripes in image due to Stand-MVS Image with bars of different brightnesses in image
cable failure (the so called “louvre effect”)
A fault caused by a bad C-arc cable (camera link) can be characterized by:
• Black pixel disturbance in a limited range of the grey level spectrum.
• Some areas of the image are not distorted at all, others are affected.
Image with pixel disturbance (this case in the grey level on the edge of the object)
Large pixelated area, with clear grey level problems. Another example of an extremity with pixilation.
Note the pixilation on the left edge of the II as well.
First step is to check the connection of the small blue ribbon cable (flex cable) from camera to the interface
board. This cable can be found in the II. Make sure that the cable is well connected on both ends.
For more detailed information on the recognition of the C-arc cables and the various versions see the
following document that is published with FCO71800030 available on Incenter.
Shielding of twisted pairs connected to each Shielding of twisted pairs connected to each other by
other by means of a soldered wire means of a metal tie-wrap
NOTE: when mounting the connector housing make sure that the analog ground contacts the connector
(white arrow) while the digital ground is isolated with isolation tape or equivalent (grey tape in the picture) to
ensure that there is no connection between the digital and the analog ground.
If the original c-arc cable is installed, repair the cable as described above and in FCO 71800017 or replace the
cable by the latest spare part version.
From November 2008 onwards an new designed c-arc cable will be offered in an FCO:
FCO 718 00 030 for BV Pulsera rel 2.2 (SUCO systems)
FCO 718 00 031 for BV Endura rel 2.2 (SUCO systems, currently to be released in Jan 2009)
The ACB function will “over-stretch” the limited grey-level range, resulting in an image which appears to be
distorted.
3.4.1 Solution:
Application instruction to customer with respect to correct use of kV /mA stabilization.
3.4.2 Simulation
The pixilation effect can be simulated by lowering the kV in manual mode. Below an example of such
simulation is shown:
Automatic stabilization at 60 kV. This image is Same situation but now in hand mode at 55 kV.
made at 56 kV. Note there are ACB artifact visible in the image
(Note there are no ACB artifacts visible) everywhere.
Image with ACB issue, note that the effect is Example of an image with ACB distortion while still
visible over the whole image. having a quite large contrast in the image.
Example of a spine with ACB artefacts. Example of an almost empty II showing ACB
artefacts.
characterized by:
• “Pepper and salt” noise
• Bright and dark object
edges (enhanced)
3.6.1 Solution:
Application instruction to customer with respect to subtraction procedures.
3.7.1 Solution:
improved exam setting as supported in rel 2.2.6. or rel 2.3.3.
Image where the scout fluoroscopy time was too short Image with correct scout fluoroscopy
As you can see first there’s a run on continuous fluoroscopy which sets the actual kV value. After this the
digital exposure is activated.
This results in almost blank grey images as shown in the 3rd digital exposure example.
3.8.1.3 Solution:
Application instructions to customer to perform LDF scout prior to using digital exposure to set the correct KV
level.