Rel15logfileexamplesv2 1

Logfile examples CT Aura
Logfile examples of the CT Aura
PHILIPS CT AURA 02.1 1

Copyright © 2002 Philips Medical Systems Nederland B.V.
ALL RIGHTS RESERVED
CT Aura Logfile examples
Contents
1. LOGFILE EXAMPLES...................................................................................................................................................................................................................... 3
1.1. Introduction .................................................................................................................................................................................................................................... 3
1.2. Logged situations which are not a real error or problem............................................................................................................................................................... 3
1.2.1. Stop scanner rotation. ............................................................................................................................................................................................................ 3
1.2.2. Get put object not found (Feerrlog) ........................................................................................................................................................................................ 4
1.2.3. Timing ack timeout (Feerrlog) ................................................................................................................................................................................................ 5
1.2.4. Timing state timeout (Feerrlog) .............................................................................................................................................................................................. 5
1.2.5. Export error (Beerrlog) .......................................................................................................................................................................................................... 6
1.2.6. Cannot copy ctLs command (Beerrlog).................................................................................................................................................................................. 7
1.2.7. Warning panel "Error exporting" (Bealtlog), Error DICOM Out of Resources (Beerrlog)....................................................................................................... 7
1.2.8. HVPS Advisory (Feerrlog) ...................................................................................................................................................................................................... 7
1.2.9. Emergency stop, Rotate power off, Motion power off, Comm error (Feerrlog)...................................................................................................................... 8
1.2.10. Communications Error Recon/RS232 (Feerrlog) ................................................................................................................................................................... 8
1.2.11. Restore of system data 'configfe.txt' is rejected, Restore of system data 'confinfo.txt' is rejected (Bealtlog)........................................................................ 8
1.2.12. System data 'xxxxxxxx.txt' not correct release (Bealtlog) ...................................................................................................................................................... 9
1.3. Logged situations which are (could be) a real error or problem.................................................................................................................................................. 10
1.3.1. Unrecoverable arc, Anode arc, Xray mode not on (Feerrlog) .............................................................................................................................................. 10
1.3.2. Isolator/Rectifier prime power error, Anode rotate error, Low input power to anode drive, Comm error (Feerrlog)............................................................ 10
1.3.3. BE not consuming images, BE cannot consume images fast enough (Feerrlog)................................................................................................................ 11
1.3.4. Max invalid views (Feerrlog)................................................................................................................................................................................................. 12
1.3.5. Communications Error - Dlink Time-out, Comm. Error (Framing Data CH Packet), Comm. Error (CRC Data CH Packet) (Feeerlog)............................ 13
1.3.6. Power Regulator Fault , Filament Fault , Watch Dog Fault , Input Hi, Input Lo, High Voltage (Kv) Overvoltage (Feerrlog) ............................................... 14
1.3.7. #SCANNER_DISCONNECTED Protocol finished with CC_ProtocolError (Beerrlog) ......................................................................................................... 16
1.3.8. Protocol error (Feerrlog)....................................................................................................................................................................................................... 19
1.3.9. Command failed due to incorrect state (Feerrlog)................................................................................................................................................................ 19
1.3.10. Collimator Command Retry, Collimator Move Timeout (Feerrlog)....................................................................................................................................... 21
1.3.11. #SCANNER_INITIALIZATION_ERROR Could not initialize connection to the scanner (Beerrlog) and many Tbl/Tilt Cntrl errors (Feerrlog). .................. 21
1.3.12. Unsolicited xxxxxx movement (Feerrlog) ............................................................................................................................................................................. 23
2 02.1 PHILIPS CT AURA

ALL RIGHTS RESERVED
1. LOGFILE EXAMPLES.
1.1. INTRODUCTION
Next subchapters will give several logfile examples and explanations.
The examples are based on release 1.5, but some of them are also valid for previous releases.
The tables as shown, are generated from merged logfiles, so you can see the time relation between the messages in the different logfiles.
The Feerrlog does not generate milliseconds in the timestamp.
Also read the chapter "Logfile Analysis" in Section F of the Technical Service Manual for the CT Aura.
Chapter 1.2 will give examples of situations, which are not a real problem (hardware or software).
Chapter 1.3 will give examples of real problems with hardware and some release 1.5 related issues.
Compared to release 1.3 (or lower), in release 1.5 the messages "System Error" and "Gantry Error" are changed in "System Status" and "Gantry Status".
The Bealtlog logfile will show if the message as shown to the Operator is an "Info", "Warning" or "Error" panel message.
1.2. LOGGED SITUATIONS WHICH ARE NOT A REAL ERROR OR PROBLEM.

This chapter will give an overview and explanation of logfile items which are not really a problem (hardware or software), but a result of the situation or the used
method.
1.2.1. STOP SCANNER ROTATION.

In release 1.5 this new function is implemented to set the Disc already in the Lateral Scanogram position when preparing the next patient, so that the operator does
not need to wait 1 to 2 minutes when he wants to make the scanogram. Because this is not a real feature in the frontend, the scanogram protocol is used without the
START function. So after PREPARE immediately a STOP is send to the frontend.
Logfile Time ms Unit Subunit Message
Bealtlog 15:43:58 185 #Info panel: 'Stop rotation' <dismissed>
Beevtlog 15:43:59 196 #STOP_SCANNER_ROTATION_START
Beevtlog 15:43:59 200 #SCANOGRAM_PREPARE kV:120, mA:20 slit:2.0, scan direction:ScanDirectionInward, scan length:75 tube angle:90, matrix:512
Beevtlog 15:43:59 605 #SCANOGRAM_STOP
Beevtlog 15:44:02 619 #SCANOGRAM_END
Beevtlog 15:44:02 623 #STOP_SCANNER_ROTATION_END
Next error will be mentioned if on the BE a "Stop Scanner Rotation" is requested while the buttons for table or tilt movement on the FE are used (FE moving direct).
Beevtlog 13:30:12 281 #SCANNER_MOVE_DIRECT Start
Feerrlog 13:30:14 DBASE invalid BE request

ALL RIGHTS RESERVED

Beerrlog 13:30:15 743 #IF_ERROR_REPORTED [ETCScanogramProtocol] completed with completion code: CC_InvalidRequest: FE Moving direct
Beerrlog 13:30:15 764 #IF_ERROR_REPORTED [ETCStopScannerRotationProtocol] completed with completion code: CC_InvalidRequest: FE Moving direct
Bealtlog 13:30:15 777 #Error panel: 'System status', System processes running or requested action currently not possible.
Bealtlog 13:30:17 865 #Error panel: 'System status' <dismissed>
Beevtlog 13:30:22 846 #SCANNER_MOVE_DIRECT Stop
Next error will be mentioned if on the BE a "Stop Scanner Rotation" is requested while the table vertical is below the normal working height or if the gantry is tilted.
This means that a scanogram prepare (as used for the "stop rotation"0) is not possible.
Beevtlog 13:29:04 754 #SCANOGRAM_PREPARE kV:120, mA:20 slit:2.0, scan direction:ScanDirectionOutward, scan length:75 tube angle:90, matrix:51
Bealtlog 13:29:05 662 #Error panel: 'System status', System processes running or requested action currently not possible.
1.2.2. GET PUT OBJECT NOT FOUND (FEERRLOG)

Every 2 hours the logfiles are copied to the "Service Data Store" area on the BE. The Feerrlog is then cleaned on the FE.
If no errors will occur (and logged) on the FE, then 2 hours later the Feerrlog will not be available and when trying to retrieve it, it will result in the error "get put object
not found". This error is then logged and so when doing the "Service Data Store" update again 2 hours later, there will be a Feerrlog and the error is not mentioned.
2 hours later the error will be mentioned again, and so on......
Feerrlog 22:44:08 DBASE get put object not found
Beevtlog 22:44:09 450 #SERVICE_DATA_STORE_UPDATE log
Feerrlog 2:44:08 DBASE get put object not found

ALL RIGHTS RESERVED
1.2.3. TIMING ACK TIMEOUT (FEERRLOG)

Since release 1.3.2 the system shutdown (power down) after exit of the application software, is logged in the following way.
All logfiles will be closed and because the Timing computer is stopped faster than the Dbase, the Dbase will still log the error "timing ack timeout".
Feerrlog 17:56:31 ========= CLOSE LOG==========
Bealtlog 17:56:31 849 #Info panel: 'Exit application' <confirmed>
Beerrlog 17:56:31 877 #LOG_CLOSE ========== CLOSE LOG ==========
Bealtlog 17:56:31 883 #LOG_CLOSE ========== CLOSE LOG ==========
Beevtlog 17:56:31 888 #LOG_CLOSE ========== CLOSE LOG ==========
Beerrlog 17:56:36 920 #LOG_OPEN ========== OPEN LOG ==========
Beerrlog 17:56:36 925 #LOG_ENV
Bealtlog 17:56:36 931 #LOG_OPEN ========== OPEN LOG ==========
Bealtlog 17:56:36 936 #LOG_ENV
Beevtlog 17:56:36 942 #LOG_OPEN ========== OPEN LOG ==========
Beevtlog 17:56:36 945 #LOG_ENV
Beevtlog 17:56:47 977 #SYSTEM_SHUTDOWN_START
Feerrlog 17:57:17 DBASE Base timing ack timeout
Beevtlog 17:57:18 583 #SYSTEM_SHUTDOWN_END
1.2.4. TIMING STATE TIMEOUT (FEERRLOG)

If a certain function like for example a scanogram is prepared, but if the function is not started or stopped then the FE will give a "timing state timeout" error.
Feerrlog 10:24:22 DBASE Base timing state timeout
Bealtlog 10:24:23 872 #Error panel: 'Gantry Status', Error detected.
Bealtlog 10:24:24 153 #Error panel: 'System Status', System error..

ALL RIGHTS RESERVED
In a normal situation there is also a START and STOP logged.

Beevtlog 10:25:42 721 #SCANOGRAM_START
1.2.5. EXPORT ERROR (BEERRLOG)

This error will be reported in the Beevtlog, if images need to be transferred and the Scan Control has no connection with the Image Handler (easyvision).
Nothing is shown to the user (nothing in Bealtlog), so the user does not get the images on the IH until the connection is (Re-)Established.
Next example shows that 10 images need to be transferred at 12:49:11.

This does not seem to happen immediately (easyvision to busy or no connection) and the user decides to exit the application (12:59:17) with the warning as
mentioned.
After start of application again, the image transfer starts again (13:01:12) before the connection with easyvision is ready and the transfer will be rescheduled for
retry.
A shutdown is done and after power on the transfer is started again (13:33:20), but the easyvision is not ready and the job will be rescheduled.
Finally 5 minutes later, the transfer succeeds.
The message now is: Those actions (exit application and login in again or shutdown) are not necessary. If the easyvision is too busy for receiving images the
scan control will retry the transfer every 5 minutes. If the cause is the exportserver software module, then this will be restarted after 15 minutes.

Beevtlog 12:49:11 159 #EXPORT Job 40 <PATIENT NAME:> Start transfer 10 images.
............. ...................................
Bealtlog 12:59:17 482 #Warning panel: 'Exit application', Not all images transferred. If you exit, some images cannot be viewed until restart
Bealtlog 12:59:32 402 #Warning panel: 'Exit application' <confirmed>
............. ...................................
Beerrlog 13:01:14 724 #EXPORT_ERROR Job 40 <PATIENT NAME:> No connection or connection lost with easyvision
Beevtlog 13:01:14 755 #EXPORT Job 40 <PATIENT NAME:> aborted; 0 images transferred.
Beevtlog 13:01:14 821 #EXPORT Job 40 <PATIENT NAME:> Rescheduled for retry.
............. .....................................
Beevtlog 13:02:06 721 #SYSTEM_SHUTDOWN_START
Beevtlog 13:14:34 191 #SYSTEM_SHUTDOWN_END
............. .....................................

ALL RIGHTS RESERVED

Beerrlog 13:33:21 282 #EXPORT_ERROR Job 40 <PATIENT NAME:> No connection or connection lost with easyvision
Beevtlog 13:33:21 409 #EXPORT Job 40 <PATIENT NAME:> aborted; 0 images transferred.
Beevtlog 13:33:21 595 #EXPORT Job 40 <PATIENT NAME:> Rescheduled for retry.
.............
Beevtlog 13:38:24 990 #EXPORT (Re-)Established connection with easyvision
Beevtlog 13:38:30 254 #EXPORT Job 40 <PATIENT NAME:> completed; 10 images transferred.
1.2.6. CANNOT COPY CTLS COMMAND (BEERRLOG)

This will be logged in the Beerrlog if the Image Handler (easyvision) is not ready during a service backup/restore action.
This service backup/restore could be an automated system request to update the service data store area on the Scan Control or it could be an action issued by the
service engineer (backup/restore function in service mode).
Beevtlog 13:01:26 119 #SERVICE_DATA_STORE_UPDATE system
Beerrlog 13:01:31 205 #GET_SYSTEM_FILE_TOC_ERROR Cannot copy ctLs command '/tmp/ctLs' to easyvision
1.2.7. WARNING PANEL "ERROR EXPORTING" (BEALTLOG), ERROR DICOM OUT OF RESOURCES (BEERRLOG)
The database on the Image Handler (easyvision) is full.
Beerrlog 8:13:25 486 #EXPORT_ERROR Job 104 HUNINK, H. : EV1, easyVision database full (ErrorDICOMOutOfResources).
Bealtlog 8:13:25 592 #Warning panel: 'Error exporting
· Delete some images.
1.2.8. HVPS ADVISORY (FEERRLOG)

Since release 1.3.2 (arcing recovery) and the modification of the HVPS's to rev 12, one can expect more HVPS advisory errors in the Feerrlog.
This can be with Warm-up, Aircalibrations, Scanning.
However the user will not notice this (no messages on the monitor).
Beevtlog 19:29:59 553 #WARMUP_PREPARE
Beevtlog 19:30:21 742 #WARMUP_START
Feerrlog 19:30:21 DISC HVPS Advisory: kV |CMD - MEAS| > 2%
Feerrlog 19:30:26 DISC HVPS Advisory: mA |CMD - MEAS| > 5%
Beevtlog 19:31:27 095 #WARMUP_STOP
Beevtlog 19:31:28 195 #WARMUP_END

ALL RIGHTS RESERVED
1.2.9. EMERGENCY STOP, ROTATE POWER OFF, MOTION POWER OFF, COMM ERROR (FEERRLOG)
During an emergency stop (emergency button pressed) the rotation power (disc rotation) and motion power (table/tilt movement) are disabled.
Also the RF link will stop, which will cause the x-ray to stop because the disc computer does nor receive any commtrigger anymore.
Feerrlog 18:51:48 DBASE Reconstructor Das View Timeout
Feerrlog 18:51:52 BASE Rotate Cntlr Emergency Stop
Feerrlog 18:51:52 BASE Rotate Cntlr Rotate Power Off
Feerrlog 18:51:52 BASE Comm. Error (Missed Data CH Packet)
Feerrlog 18:51:52 BASE Table/Tilt Cntl Emergency Stop
Feerrlog 18:51:52 BASE Rotate Cntlr Motion Power Off
Feerrlog 18:51:52 BASE Emergency Stop
Beerrlog 18:51:56 774 #EMERGENCY_CLEARANCE_ERROR Emergency button is not cleared yet.
Bealtlog 18:51:56 826 #Error panel: 'System status', Emergency stop is not cleared.
1.2.10. COMMUNICATIONS ERROR RECON/RS232 (FEERRLOG)

If you do not keep the START button pressed during a scanogram, but only touch it for a short time, a communication error with the reconstructor can occur.
Feerrlog 14:38:36 BASE Reconstructor Communications Error (Recon/RS232)
1.2.11. RESTORE OF SYSTEM DATA 'CONFIGFE.TXT' IS REJECTED, RESTORE OF SYSTEM DATA 'CONFINFO.TXT' IS REJECTED (BEALTLOG)
During the restore procedure of the system files, the Configfe.txt and the Confinfo.txt should not be selected because it is not possible to restore these files.
If selected they will generate the errors as listed in next table.
Bealtlog 11:23:14 212 #Info panel: 'Restore' <dismissed>
Bealtlog 11:23:14 244 #Error panel: 'Restore', Restore of system data 'configfe.txt' is rejected, data is not valid for this system.
Beerrlog 11:23:14 253 #RESTORE_REJECT Restore of system data 'configfe.txt' is rejected, data is not valid for this system.
Beevtlog 11:23:14 269 #RESTORE_EVENT Restore aborted.
Bealtlog 11:23:32 777 #Error panel: 'Restore' <confirmed>
Beevtlog 11:23:35 116 #RESTORE_EVENT Restore started.
Bealtlog 11:23:38 939 #Info panel: 'Restore' <confirmed>

ALL RIGHTS RESERVED

Bealtlog 11:23:39 807 #Error panel: 'Restore', Restore of system data 'confinfo.txt' is rejected, data is not valid for this system.
Beerrlog 11:23:39 822 #RESTORE_REJECT Restore of system data 'confinfo.txt' is rejected, data is not valid for this system.
Beevtlog 11:23:39 840 #RESTORE_EVENT Restore aborted.
Bealtlog 11:23:47 938 #Error panel: 'Restore' <confirmed>
1.2.12. SYSTEM DATA 'XXXXXXXX.TXT' NOT CORRECT RELEASE (BEALTLOG)

Messages like this can occur when restoring certain files (for example 'custombe.txt' or 'userprot.txt') from a backup CD of an incorrect (previous) release.
The same occurs if the scanner type is changed from C150 to C200 or vice-versa.
Beerrlog 11:23:54 158 #RESTORE_WARNING Caution: system data 'xxxxxxxx.txt' not correct release.
Bealtlog 11:23:57 286 #Info panel: 'Restore' <confirmed>
· Make sure that after a software upgrade to a new (higher) release version, a new backup CD is made.

ALL RIGHTS RESERVED
1.3. LOGGED SITUATIONS WHICH ARE (COULD BE) A REAL ERROR OR PROBLEM.
Next examples are related to hardware problems or release 1.5 related issues.
1.3.1. UNRECOVERABLE ARC, ANODE ARC, XRAY MODE NOT ON (FEERRLOG)

Since release 1.3.2 arcing recovery is implemented (software + hvps upgrade to rev 12). During an Aircalibration arcing is not allowed and will therefor not be
recovered and logged as unrecoverable arc. A lot of times you will see more "Gantry Status" logged untill the panel is confirmed.
The Reconstructor will receive data of which the value for the reference detectors is too low and will result in "Xray Mode Not On" error.
If the arcing occurs in the first 70ms of the scan (the arcing recovery is not yet enabled), then only "Xray Mode Not On" error will be logged.
Beevtlog 15:48:08 831 #AIR_CALIBRATION_PREPARE kV:140, slit:3.0,
Beevtlog 15:48:13 412 #AIR_CALIBRATION_START
Feerrlog 15:48:15 DISC Hvps Anode Arc
Feerrlog 15:48:15 DBASE Reconstructor Xray Mode Not On
Beevtlog 15:48:16 112 #AIR_CALIBRATION_END
Beerrlog 15:48:16 158 #SCANNER_ARCING [ETCAirCalibrationProtocol] completed with unrecoverable arc
Bealtlog 15:48:16 720 #Error panel: 'System Status', Unrecoverable arcing occurred.
Bealtlog 15:48:52 394 #Panel: 'System Status' <dismissed>
Bealtlog 15:48:54 326 #Panel: 'Gantry Status' <confirmed>
Bealtlog 15:48:54 736 #Panel: 'Recover' <dismissed>
· Follow the instructions as indicated in chapter 1 "Beamline" with respect to HVPS 's, HV cables and X-ray tube to troubleshoot the acring problem.
1.3.2. ISOLATOR/RECTIFIER PRIME POWER ERROR, ANODE ROTATE ERROR, LOW INPUT POWER TO ANODE DRIVE, COMM ERROR (FEERRLOG)
If the FE is not powered down in the normal way, for example because the hospital mains is switched off suddenly, then the Base computer will stay on for a while
by the UPS in the Isolator Rectifier. Because everything else is OFF, most of the following errors will be logged.

ALL RIGHTS RESERVED

Feerrlog 5:24:02 BASE Communications Error (Dlink Time-out)
Feerrlog 5:24:02 BASE Comm. Error (Framing Data CH Packet)
Feerrlog 5:24:02 BASE Comm. Error (CRC Data CH Packet)
Feerrlog 5:24:02 DISC Anode MRC only, Low input power to anode drive
Feerrlog 5:24:02 DISC Anode Anode Rotate Error
Feerrlog 5:24:04 BASE Comm. Err (CAN Time-out, Tbl Cntl)
Feerrlog 5:24:04 BASE Comm. Err (CAN Time-out, Rotate Cntl)
Beevtlog 5:24:04 008 #SCANNER_DOOR_SWITCH door open
Beevtlog 5:24:04 089 #SCANNER_DOOR_SWITCH door closed
Beevtlog 5:24:04 134 #SCANNER_DOOR_SWITCH door open
Feerrlog 5:24:06 BASE Isolator/Rectifier prime power error
The problem can be caused by :
· Hospital mains power switched off suddenly.
· Problem in the UCI box which switches off the FE.
· By the service engineer by using the service switch in the "base power assy".
1.3.3. BE NOT CONSUMING IMAGES, BE CANNOT CONSUME IMAGES FAST ENOUGH (FEERRLOG)
The BE sends an acknowledge for every received image from the FE. If the BE does not send this acknowledgement anymore, the FE will wait with sending images.
The FE has a buffer of 16 images. If after those 16 images (buffer full) the FE did still not receive an acknowledgment, then it will stop the post recon process and
log the error "BE not consuming images".
Beevtlog 9:22:16 450 #MULTI_SCAN_START
Beevtlog 9:22:17 010 #MULTI_SCAN_BLOCK_PREPARE_VOLUME blockno:1 kV:120, mA:120 slit:5.0, rec.center:[-0.72,0.00], fov:281.7, matrix: 512x512
Beevtlog 9:23:24 078 #MULTI_SCAN_BLOCK_START Block: 1
Beevtlog 9:24:21 762 #MULTI_SCAN_BLOCK_END Block: 1 Acquired slices:[1..54]
Beevtlog 9:24:22 624 #MULTI_SCAN_END
Beevtlog 9:24:22 990 #POST_RECON_START Volume reconstruction, control key:1012206038018221, # slices:37, start image:29, start pos.: -158.50
Beevtlog 9:24:50 985 #POST_RECON_SUSPEND 51 of 66 images received

ALL RIGHTS RESERVED
Beevtlog 9:24:51 348 #POST_RECON_START Volume reconstruction, control key:1012206038018221, # slices:15, start image:51, start pos.: -224.50
Beevtlog 9:25:11 233 #POST_RECON_END 66 images received
Beevtlog 9:25:11 888 #EXPORT Job 10 Anbeek-Simens, Marjon: Start transfer 66 images.
Beevtlog 9:25:11 971 #EXPORT (Re-)Established connection with EV1
Beevtlog 9:25:12 196 #POST_RECON_START Volume reconstruction, control key:1012206135044229, # slices:131, start image:0, start pos.: -71.50,
Beevtlog 9:25:45 060 #EXPORT Job 10 Anbeek-Simens, Marjon: completed; 66 images transferred.
Feerrlog 9:27:06 DBASE BE not consuming images
· When during a reconstruction of a large set of images the table is moved from the FrontEnd control panels it may happen that the BackEnd is not accepting
images fast enough which results in the message "BE not consuming images" in the Feerrlog. Another possible error message is: BE cannot consume images
fast enough.
A typical sequence of events is shown above.
This is still under investigation but we have some preliminary results which may clarify the matter.
Usually this happens when a volume reconstruction (or post-reconstruction) is done with a large number of images. If during this reconstruction a table
movement button is pressed and NOT released again and is being pressed for a very long time (like can happen with the home-button) this slows down the
speed of the BE until the image buffer on the FE is full.
A temporay fix would be to ask the operator to release the button every once in a while.
When the error occurs the jobs in the post-reconstruction queue are sometimes suspended and sometimes rejected.
If suspended you need to go out/in the application software and reconstruction will start again.
If rejected the job can be restarted by pressing the redo-button.
In both cases all images can be recovered.
· Another reason could be too many retries on the ethernet link. Check the total ethernet connection between the BE and the FE.
In some cases, replacing the UTP cable with an STP cable will help.
1.3.4. MAX INVALID VIEWS (FEERRLOG)

When there is no x-ray generated the system will measure the offset data of the detector channels to generate an offset calibration table.
If during this process more than 256 detector read outs (views) have invalid data, then this error will be generated.
Bealtlog 08:56:18 558 #Panel: 'Scanning not possible' <dismissed>
Feerrlog 08:58:16 DBASE Reconstructor Max Invalid Views
Feerrlog 08:58:33 DBASE Reconstructor Max Invalid Views
Bealtlog 08:58:33 102 #Panel: 'Gantry Status' <confirmed>

ALL RIGHTS RESERVED

Bealtlog 08:58:34 373 #Panel: 'Recover' <dismissed>
Bealtlog 08:58:34 508 #Error panel: 'Reset failed', Recovery failed
Bealtlog 08:58:34 565 #Error panel: 'Reset failed', Recovery failed
· The error can de reset by switching OFF and ON the Gantry.
· The problem can be caused by incorrect offset data, disturbed data due to a problem in the communication between DAS and Reconstructor or a problem with
the reconstructor.
· From the Service Interface, run the following from the Diagnostics pull down menu.
- Low level Diagnostics, Communication test.
- Offset statistics.
- Continuous offset test.
- Reconstruction test.
· Check all cabling to the Reconstructor (internal and external in the Base computer)
· Check the complete RF-link and cabling.
· In a lot of cases the tests run fine although this error still occurs now and then.
The most probable cause in this case is one of the COMM cards.
1.3.5. COMMUNICATIONS ERROR - DLINK TIME-OUT, COMM. ERROR (FRAMING DATA CH PACKET), COMM. ERROR (CRC DATA CH PACKET)
(FEEERLOG)
A lot of these errors occur at any time while doing nothing or just making airtables or a scan. In next example the reconstructor also gives an error because of not
receiving the data due to the communication error.
Feerrlog 7:54:53 BASE Comm. Error (Framing Data CH Packet)
Feerrlog 7:54:53 BASE Comm. Error (CRC Data CH Packet)
Bealtlog #Error panel: 'Gantry Status', Error detected.
· The problem can be caused by a problem in the RF link or the Disc computer.
· From the Service Interface, run the following from the Diagnostics pull down menu.
- Low level Diagnostics, Communication test.
- Continuous offset test.

ALL RIGHTS RESERVED
· Check the complete RF-link and cabling.

· Check if the Disc computer is up and running.
In several cases the Disc computer is reset every time by a defective Disccomputer-LVPS board.
Measure the reset signal for the Disc computer on TP8. It should be a 5-volt signal of about 1/2 second, only one time at power-up.
· Check the anti static brushes of the drive- and idler-truck.
1.3.6. POWER REGULATOR FAULT , FILAMENT FAULT , WATCH DOG FAULT , INPUT HI, INPUT LO, HIGH VOLTAGE (KV) OVERVOLTAGE
(FEERRLOG)
st
At 1 warm-up after system power all errors from the HVPS will be logged in the Feerrlog, but the user does not get any error message displayed (nothing in
Bealtlog). The first scan after the warmup (airtable or scan) will also generate all errors, but a "Gantry error" will be displayed.
Next scan (airtable or scan) will be possible and give a normal result, but the error "High Voltage (Kv) Overvoltage" will be logged every time after Prepare.
Beevtlog 8:39:18 724 #WARMUP_PREPARE
Feerrlog 8:39:24 DISC Hvps Power Regulator Fault
Feerrlog 8:39:24 DISC Hvps Filament Fault
Feerrlog 8:39:24 DISC Hvps Watch Dog Fault
Feerrlog 8:39:24 DISC Hvps Input Hi
Feerrlog 8:39:24 DISC Hvps Input Lo
Feerrlog 8:39:24 DISC Hvps High Voltage (Kv) Overvoltage
Feerrlog 8:39:25 DISC HVPS Advisory: kV |CMD - MEAS| > 2%
Feerrlog 8:39:25 DISC HVPS Advisory: mA |CMD - MEAS| > 5%
Beevtlog 8:39:25 398 #WARMUP_START
Feerrlog 8:39:28 BASE Filament aux. reading out of range

ALL RIGHTS RESERVED

Beevtlog 8:40:46 921 #WARMUP_END
........... ..........................
Feerrlog 8:42:29 DISC Hvps Power Regulator Fault
Feerrlog 8:42:29 DISC Hvps Filament Fault
Feerrlog 8:42:29 DISC Hvps Watch Dog Fault
Feerrlog 8:42:29 DISC Hvps Input Hi
Feerrlog 8:42:29 DISC Hvps Input Lo
Feerrlog 8:42:33 DBASE Reconstructor X-ray Below Threshold
Bealtlog 8:42:33 782 #Error panel: 'Gantry error', Error detected.
Bealtlog 8:42:34 903 #Error panel: 'System error', System error..
............ ...............................
· Check if the following is noticed
- The HVPS status indicator on the timing monitor was 03BF (hex), but should be 0200 (h)
- The 'FAULT" LED on the HVPS will stay on until the first scan (airtable or scan) is made.
- During warm-up, the tube heat load indicator goes up as normal, but the X-ray indicator LED in the UCI does not go on, so no real X-rays are generated.
If this is the case, then most probably the Disc Storage Assembly does not supply the +120 VDC to the HVPS 's at power on.
To make X-rays, the system needs +160 VDC supply to the HV tanks. To avoid that the system (in any way) can generate unwanted X-rays during start-up
before the right SW and HW parameters are set, the +160 VDC is not supplied to the tanks during the first 40 - 45 seconds after the start-up.
To supply the electronics of the HV tanks, a reduced power of +120 VDC is supplied. The Disc Storage Assembly (DSA) supplies this +120 VDC.
After power on to the HVPS 's, the Fault error will normal be on until a reset from the Disc computer is received. This is normal within 1 second after power
supplied to the Disc. If the +120 VDC is not supplied at power on, but the +160 VDC is switching on the HVPS 's 40 seconds later, then the reset signal is
already gone, so the HVPS 's will stay in an error situation until after the first scan. An error is detected and the software will generate a reset signal.
Replace the Disc Storage Assembly on the Disc.

ALL RIGHTS RESERVED
1.3.7. #SCANNER_DISCONNECTED PROTOCOL FINISHED WITH CC_PROTOCOLERROR (BEERRLOG)

Next three examples of lost connections all occur because the BE receives information from the FE which it does not expect (at least not at that moment). In other
words, the BE-FE protocol (the way information is transferred between BE and FE) ends with a CC_protocol error. As this happens the BE reacts by breaking off the
connection. This is as specified. In this way it is assured that the software is in a defined state after restart of application software.
An investigation was done on the occurrence of these three "lost connections". In 40 systemweeks we have seen in total 9 disconnects. This is about one per month.
When either of these three "lost connections" happen they always happen after data-acquisition and system can be restarted within one minute. This means no data
is lost nor has contrast been administered without images being made.
Besides that in release 1.5 several other "lost connections" have been solved: in release 1.3.1 there was a "lost connection" during Volume scan which is solved in
1.3.2 (and 1.5). In release 1.3.1 and 1.3.2 there was a "lost connection" before the start of a serial scan sequence. So if a system suffers from "lost connections" the
advice would be first to implement 1.5.
Remark: every time a service session is started there is always a "lost connection" in the beerrlog. It goes without saying that one should not try and repair this
particular "lost connection".
Some more explanation to the remaining 1.5 "lost connections" you will find below.
1. Lost connection after scanogram

Connection betweenFrontEnd and BackEnd is lost after scanogram is finished.
Typical sequence of events is shown below. It shows a scanogram being made:
#SCANOGRAM_PREPARE
#SCANOGRAM_START
#SCANOGRAM_STOP
After this the FE probably sends some extra info which the BE does not expect, leading to:
#IF_ERROR_REPORTED [ETCScanogramProtocol] completed with completion code: CC_ProtocolError
Because of this the BE breaks off the connection and requires the operator to restart the application software as below.
#SCANNER_DISCONNECTED Received nil message
#SCANNER_CONNECTION_ERROR Lost connection to the scanner.
#Error panel: 'System status', Reset has been activated.
Beerrlog 12:57:41 654 #IF_ERROR_REPORTED [ETCScanogramProtocol] completed with completion code: CC_ProtocolError
Beerrlog 12:57:41 662 #SCANNER_DISCONNECTED Protocol finished with CC_ProtocolError
Beerrlog 12:57:41 666 #SCANNER_DISCONNECTED Received nil message
Beerrlog 12:57:41 670 #SCANNER_CONNECTION_ERROR Lost connection to the scanner.
Bealtlog 12:57:41 679 #Error panel: 'System status', Reset has been activated.
Beevtlog 12:57:41 998 #EXPORT Job 40 BERGHMANS, P.J.A.: Start transfer 1 images.
Beevtlog 12:57:42 058 #EXPORT (Re-)Established connection with CT1imageha

ALL RIGHTS RESERVED
Beerrlog 12:57:42 175 #CLEAR_TABLE_STOP_POSITION_IGNORE Scanner is disconnected

Beerrlog 12:57:42 198 #CLEAR_GANTRY_STOP_POSITION_IGNORE Scanner is disconnected
Beevtlog 12:57:42 839 #EXPORT Job 40 BERGHMANS, P.J.A.: completed; 1 images transferred.
Feerrlog 12:57:53 ==== CLOSE LOG ==========
Bealtlog 12:57:53 010 #Error panel: 'System status' <confirmed>
2. Lost connection after volume scan

Connection between FrontEnd and BackEnd is lost after volume scan is finished.
Typical sequence of events is shown below.
This shows the sequence of a volume scan being made and finished with a protocol error this time showing up as:
#IF_ERROR_REPORTED [ETCStartMultiScanProtocol] completed with completion code: CC_ProtocolError.
This leads again to the BE breaking off the connection and requiring a restart.
Beevtlog 11:06:47 498 #EXPORT Job 6 GERSEN, P.C.: Start transfer 1 images.
Beevtlog 11:06:47 554 #EXPORT (Re-)Established connection with CT1imageha
Beevtlog 11:06:48 265 #EXPORT Job 6 GERSEN, P.C.: completed; 1 images transferred.
Beevtlog 11:07:20 843 #MOVE_TABLE_MANUAL_START plannedTablePosition: 1103.000000
Beevtlog 11:07:22 638 #MOVE_TABLE_START displacement: 461.000000
Beevtlog 11:07:29 861 #MOVE_TABLE_END
Beevtlog 11:07:31 338 #MOVE_TABLE_MANUAL_END
Beerrlog 11:09:52 946 #IF_ERROR_REPORTED [ETCStartMultiScanProtocol] completed with completion code: CC_ProtocolError
Beerrlog 11:09:52 983 #IF_ERROR_REPORTED [ETCMultiScanProtocol] completed with completion code: CC_Disconnected

ALL RIGHTS RESERVED
Beerrlog 11:09:53 170 #CLEAR_TABLE_STOP_POSITION_IGNORE Scanner is disconnected

Beerrlog 11:09:53 173 #CLEAR_GANTRY_STOP_POSITION_IGNORE Scanner is disconnected
Beerrlog 11:09:53 339 #IF_ERROR_REPORTED [ETCPostReconstructionProtocol] completed with completion code: CC_Disconnected
3. Lost connection after "BE cannot consume images fast enough"

Connection between FrontEnd and BackEnd is lost after "BE cannot consume images fast enough".
Typical sequence of events is shown below.
The BE breaks off connection here because of the message from the FE: BE cannot consume images fast enough.
Beevtlog 20:22:17 068 #POST_RECON_START Volume reconstruction, control key:1021054804639216, # slices:259, start image:0, start pos.: -16.00,
Feerrlog 20:27:05 DBASE BE cannot consume images fast enough
Bealtlog 20:27:08 636 #Error panel: 'Gantry status', Error detected.
Beerrlog 20:27:09 159 #IF_ERROR_REPORTED [ETCPostReconstructionProtocol] completed with completion code: CC_ProtocolError

ALL RIGHTS RESERVED
Beevtlog 20:27:10 014 #EXPORT Job 3 Klaver, Ruurd: Start transfer 256 images.
Beevtlog 20:27:10 090 #EXPORT (Re-)Established connection with EV1
· We have not been able to reproduce this problem (yet) but it is very probably closely related to 1.3.3
1.3.8. PROTOCOL ERROR (FEERRLOG)

When a Scan prepare times out sometimes in this system a "Protocol error" appears. See below for more details.
This seems to be related to the fact that the start button was not pressed in due time (5 minutes) after the prepare button has been pressed
Beevtlog 12:50:02 743 #MULTI_SCAN_BLOCK_PREPARE_SERIAL blockno:1 kV:130, mA:140 slit:3.0, #rotations:11 #rot:2.0 rec.center:[0.00,-91.99], fo
Feerrlog 12:55:19 DBASE Reconstructor Protocol Error
Feerrlog 12:55:19 DISC Current operation timed out
Bealtlog 12:55:20 265 #Error panel: 'User input timeout', System will not be ready after delay time. Please retry..
· This problem could not be reproduced. Any new insights are welcome.
1.3.9. COMMAND FAILED DUE TO INCORRECT STATE (FEERRLOG)

When the customer is doing the so-called HI-RES examination it can happen that the disc computer changes state such that it is in the incorrect state.
An example is given below.
Beevtlog 11:58:16 990 #EXPORT Job 36 HODSON, ROYDEN: Start transfer 1 images.
Beevtlog 11:58:18 344 #EXPORT Job 36 HODSON, ROYDEN: completed; 1 images transferred.
Beevtlog 11:58:36 030 #MOVE_TABLE_MANUAL_START plannedTablePosition: 1130.000000

ALL RIGHTS RESERVED
Beevtlog 11:58:36 788 #MOVE_TABLE_START displacement: -108.000000

Beevtlog 11:58:40 215 #MOVE_TABLE_END
Beevtlog 11:58:43 010 #MOVE_TABLE_MANUAL_END
Beevtlog 11:58:43 286 #MULTI_SCAN_BLOCK_PREPARE_SERIAL blockno:1 kV:120, mA:70 slit:2.0, #rotations:17 #rot:1.0 rec.center:[2.16,0.00], fov:3
Feerrlog 12:00:21 DISC Command failed due to incorrect state
· The cause of the problem could not be established. However, there is probably a relation with the working procedure. Any new insights are welcome.

ALL RIGHTS RESERVED
1.3.10. COLLIMATOR COMMAND RETRY, COLLIMATOR MOVE TIMEOUT (FEERRLOG)

Some systems seem to suffer from these collimator errors during aircalibration or normal scanning, allthough transparent to the customer (nothing in Beerrlog or
Bealtlog).
Feerrlog 7:32:36 DISC Collimator Command Retry

Beevtlog 11:20:42 949 #MULTI_SCAN_BLOCK_PREPARE_SERIAL blockno:1 kV:140, mA:100 slit:3.0, #rotations:55 #rot:2.0 rec.center:[0.00,0.00], fov:
Feerrlog 11:23:03 DISC Collimator Move Timeout
Feerrlog 11:23:18 DISC Collimator Move Timeout
· A maintenance procedure should be done to prevent the collimator getting defective.
We are currently busy with our supplier to establish a maintenance procedure.
1.3.11. #SCANNER_INITIALIZATION_ERROR COULD NOT INITIALIZE CONNECTION TO THE SCANNER (BEERRLOG) AND MANY TBL/TILT
CNTRL ERRORS (FEERRLOG).
During start of the application software the FE has many Unsolicited vertical movements and the Tbl/Tilt Cntrl generates some errors as well.
This caused the BE is not being able to make the connection with the Scanner. Exit Apllication and Login again was possible, but some time later the Tbl/Tilt Cntrl
generated more errors like WDTS error, EEProm Checksum Error, CAN BUS Error etc.
Beerrlog 11:36:21 514 #LOG_OPEN ========== OPEN LOG ==========
Beerrlog 11:36:21 702 #LOG_ENV
Bealtlog 11:36:21 826 #LOG_OPEN ========== OPEN LOG ==========
Bealtlog 11:36:21 945 #LOG_ENV
Feerrlog 11:36:22 ==== OPEN LOG ==========
Beevtlog 11:36:22 108 #LOG_OPEN ========== OPEN LOG ==========
Beevtlog 11:36:22 213 #LOG_ENV
Feerrlog 11:36:23
Feerrlog 11:37:49 BASE Unsolicited vertical movement

ALL RIGHTS RESERVED

Feerrlog 11:37:57 BASE Tbl/Tilt Cntlr Error Horizontal
Feerrlog 11:37:57 BASE Tbl/Tilt Cntlr Horizontal In Latch
Feerrlog 11:38:01 BASE Tbl/Tilt Cntlr Horizontal In Latch
Feerrlog 11:38:01 BASE Tbl/Tilt Cntlr Error Horizontal
Beerrlog 11:38:01 356 #SCANNER_INITIALIZATION_ERROR Could not initialize connection to the scanner.
............. ....................................................
Feerrlog 12:42:51 BASE Tbl/Tilt Cntlr Tilt In Switch Hit
Feerrlog 12:42:51 BASE Tbl/Tilt Cntlr WDTS Error
Feerrlog 12:42:51 BASE Tbl/Tilt Cntlr EEProm Checksum Error
Feerrlog 12:42:51 BASE Tbl/Tilt Cntlr CAN BUS Error
Feerrlog 12:42:51 BASE Tbl/Tilt Cntlr Internal RAM Error
Feerrlog 12:42:51 BASE Tbl/Tilt Cntlr Tilt Out Switch Hit
· The Base motion controller was the cause of the problem.

ALL RIGHTS RESERVED
1.3.12. UNSOLICITED XXXXXX MOVEMENT (FEERRLOG)

The message xxxxxx can be "horizontal", "vertical" or "tilt".
Feerrlog 3:41:37 BASE Unsolicited tilt movement
Feerrlog 23:05:30 BASE Unsolicited horizontal movement
· These messages are generated when there is a movement without a command to move.
Mostly this happens during patient positioning on the table, but should not occur during the examination.
· If a lot of those errors occurs, it could be jitter from the belonging potmeter as well.
· In case of many " unsolicited vertical movement" errors, then check the vertical potmeter and the damper (see service manual section F).
· In case of many " unsolicited tilt movement" errors, then verify the tilt potmeter and the belt of the tilt potmeter. Also check if there is any play on the tilt actuator
and if the bolts on the inside of the frame (which hold the pipe of the Disc to the actuator) are tightend. See newsletter CT-077.

ALL RIGHTS RESERVED

Rel15logfileexamplesv2 1

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

Rel15logfileexamplesv2 1

Uploaded by

Copyright:

Available Formats

Logfile examples CT Aura

Logfile examples of the CT Aura

PHILIPS CT AURA 02.1 1

2 02.1 PHILIPS CT AURA

1.2. LOGGED SITUATIONS WHICH ARE NOT A REAL ERROR OR PROBLEM.

1.2.1. STOP SCANNER ROTATION.

PHILIPS CT AURA 02.1 3

Logfile Time ms Unit Subunit Message

1.2.2. GET PUT OBJECT NOT FOUND (FEERRLOG)

4 02.1 PHILIPS CT AURA

1.2.3. TIMING ACK TIMEOUT (FEERRLOG)

1.2.4. TIMING STATE TIMEOUT (FEERRLOG)

PHILIPS CT AURA 02.1 5

In a normal situation there is also a START and STOP logged.

1.2.5. EXPORT ERROR (BEERRLOG)

Next example shows that 10 images need to be transferred at 12:49:11.

Logfile Time ms Unit Subunit Message

6 02.1 PHILIPS CT AURA

Logfile Time ms Unit Subunit Message

1.2.6. CANNOT COPY CTLS COMMAND (BEERRLOG)

1.2.8. HVPS ADVISORY (FEERRLOG)

PHILIPS CT AURA 02.1 7

1.2.10. COMMUNICATIONS ERROR RECON/RS232 (FEERRLOG)

8 02.1 PHILIPS CT AURA

Logfile Time ms Unit Subunit Message

1.2.12. SYSTEM DATA 'XXXXXXXX.TXT' NOT CORRECT RELEASE (BEALTLOG)

PHILIPS CT AURA 02.1 9

1.3.1. UNRECOVERABLE ARC, ANODE ARC, XRAY MODE NOT ON (FEERRLOG)

10 02.1 PHILIPS CT AURA

Logfile Time ms Unit Subunit Message

PHILIPS CT AURA 02.1 11

1.3.4. MAX INVALID VIEWS (FEERRLOG)

12 02.1 PHILIPS CT AURA

Logfile Time ms Unit Subunit Message

PHILIPS CT AURA 02.1 13

· Check the complete RF-link and cabling.

14 02.1 PHILIPS CT AURA

Feerrlog 8:40:46 BASE Filament aux. reading out of range

PHILIPS CT AURA 02.1 15

1.3.7. #SCANNER_DISCONNECTED PROTOCOL FINISHED WITH CC_PROTOCOLERROR (BEERRLOG)

1. Lost connection after scanogram

16 02.1 PHILIPS CT AURA

Beerrlog 12:57:42 175 #CLEAR_TABLE_STOP_POSITION_IGNORE Scanner is disconnected

2. Lost connection after volume scan

PHILIPS CT AURA 02.1 17

Beerrlog 11:09:53 170 #CLEAR_TABLE_STOP_POSITION_IGNORE Scanner is disconnected

3. Lost connection after "BE cannot consume images fast enough"

18 02.1 PHILIPS CT AURA

1.3.8. PROTOCOL ERROR (FEERRLOG)

1.3.9. COMMAND FAILED DUE TO INCORRECT STATE (FEERRLOG)

PHILIPS CT AURA 02.1 19

Beevtlog 11:58:36 788 #MOVE_TABLE_START displacement: -108.000000

20 02.1 PHILIPS CT AURA

1.3.10. COLLIMATOR COMMAND RETRY, COLLIMATOR MOVE TIMEOUT (FEERRLOG)

Logfile Time ms Unit Subunit Message

PHILIPS CT AURA 02.1 21

Logfile Time ms Unit Subunit Message

22 02.1 PHILIPS CT AURA

1.3.12. UNSOLICITED XXXXXX MOVEMENT (FEERRLOG)

PHILIPS CT AURA 02.1 23

You might also like