Determining The Cause Of A Runaway Condition - Philips CARDIOMD Service Manual

Diagnostic Software Utilities
5.6.5

Determining the Cause of a Runaway Condition

When a Runaway condition exists, all the following symptoms are present:
1. A Fatal Runaway Error pop-up message is displayed on the acquisition PC.
2. No manual or preprogrammed motions are possible.
3. The yellow Collision Override LED on the hand controller is ON and cannot be turned off by
pressing the hand controller Collision Override button.
4. The green motor power LED on the gantry connector panel or the LED panel next to the
acuqisition PC is off.
Fatal runaway errors can be caused by one or more of the following:
1. The motion controllers detect conflicting position information from the incremental encoder
and absolute encoder on one or more of the motion axes (horizontal (X), vertical (Y), rotate
(Z)).
2. Actual motion runaway, that is, an un-requested motion has been detected.
Note. An actual motion runaway detected on the X and Y axis is not reported to the acquisition
PC but is only indicated by the red Runaway LED on the safety board. One example of this is
when the crank is used for emergency Y-motion retraction.
3. The two motion controllers (located in the table console) are unable to communicate with each
other.
The most likely cause for the runaway condition is that the motion controllers are detecting
different position information from the two position encoders (cause 1).
The most likely reasons for this are:
•
A defective absolute encoder, cable, or connector.
•
An absolute encoder gear has come loose from the encoder shaft.
•
A defective safety board.
The first thing to determine is which of the axes (motions) is causing the runaway error. To do
this, examine the system log file as follows:
1. On the Acquisition PC, ensure that the CardioMD application is displaying the Persistence
page.
2. Click the
the CardioMD application.
3. In the Windows Start menu, select Programs, Accessories, Notepad.
4. In Notepad, select File, Open.
5. Select the file
Note. Every time the CardioMD application is started, a new log file is created.
A runaway caused by a faulty absolute encoder will appear in the log file. An example is shown
below:
Motion Status: Ack = 0xFFFF, Error = 0x0010, X = 0x00, Y = 0x00, Z
= 0x01
[22.33.15] Motion controller error: Runaway
5-42 CardioMD Service Manual
button in the rupper right-hand corner of the application window to close down
C:\cardiocam\SystemLog\log{"last date"}.txt.
1MAN0158-H11 04-2005 CSIP Level 1