GE Healthcare · Nuclear MedicineInfinia02180100008553

Infinia Hawkeye 4 Failing to start NM scan and X-Ray Daily QC Failing after Warmup From Problem report, Log@Ac…

Infinia Hawkeye 4 Failing to start NM scan and X-Ray Daily QC Failing after Warmup

Symptom

Infinia Hawkeye 4 Failing to start NM scan and X-Ray Daily QC Failing after Warmup From Problem report, [email protected]. 07:33:37 Task:UTIL_APP Activity:OPEN Parameters:PRESET_NAME=X-ray Daily QC 07:33:40 Task:SCAN Activity:SETUP Parameters:SCAN_NAME=WarmUp|SCAN_TYPE=CTSlicesQC|PATIENT_NAME=N|PATIENT_ID=N/A|PATIENT_SEX=N/A|TASK_UID=N/A_WarmUp|MM_PER_PIXEL_X=2.0|MM_PER_PIXEL_Y=2.0|PATIENT_LOC=FFS|PROTOCOL_NAME=N/A|PAN_X=0.0|PAN_Y=0.0|CT_MA=2.5|CT_KV=140.0|NUM_STEPS=4|SLICE_THICKNESS=5.0|PITCH=1.923|FOV_RANGE=200|FILTER=stnd|TABLE_DIR=In|MATRIX=256x256 07:33:43 ERROR = Error in Activity ID:0 Stack trace:com.ge.med.fi.tacq.sequence.SequenceException: Failed to init the sequence (ERROR_SEQUENCE_INIT,11406,ERROR) at com.ge.med.fi.tacqUtil.ct.airtable.AirTableSequenceRunner.runnerSpecificSetup(AirTableSequenceRunner.java:41) at com.ge.med.fi.tacq.sequence.SequenceRunner.setup(SequenceRunner.java:676) at com.ge.med.fi.tacq.sequence.Sequence.setup(Sequence.java:543) at com.ge.med.fi.tacqUtil.ct.airtable.AirTableSequence.setup(AirTableSequence.java:132) at com.ge.med.fi.tacqUtil.ct.dailyqc.XRayDailyQCApp.handleStart(XRayDailyQCApp.java:273) at com.ge.med.fi.tacqUtil.ct.dailyqc.XRayDailyQCApp.handleControlEvent(XRayDailyQCApp.java:292) at com.ge.med.fi.tacqUtil.infra.UtilProtocol.handleControlEvent(UtilProtocol.java:837) at com.ge.med.fi.tacqUtil.vef.AppsControlUI$2.run(AppsControlUI.java:184) Caused by: com.ge.med.fi.tacq.sequence.SequenceException: Failed to Setup (ERROR_ACQ_ACTION_FAILED,10501,ERROR) at com.ge.med.fi.tacq.sequence.SequenceRunner.runnerSpecificSetup(SequenceRunner.java:694) at com.ge.med.fi.tacqUtil.ct.airtable.AirTableSequenceRunner.runnerSpecificSetup(AirTableSequenceRunner.java:38) ... 7 more Caused by: com.ge.med.fi.tacq.scan.ScanException: Failed to apply parameters to the scanner (ERROR_SCAN_APPLY,10203,ERROR) at com.ge.med.fi.tacq.scan.CTScan.apply(CTScan.java:467) at com.ge.med.fi.tacq.scan.CTSlicesScan.apply(CTSlicesScan.java:506) at com.ge.med.fi.tacq.scan.Scan.setup(Scan.java:1521) at com.ge.med.fi.tacq.sequence.SequenceRunner.runnerSpecificSetup(SequenceRunner.java:691) ... 8 more Caused by: com.ge.med.fi.tacq.scanner.ScannerException: Internal subsystem error (SCANNER_SUBSYETM_SETUP_FAIL,9012,ERROR) at com.ge.med.fi.tacq.hwifc.VG.VGCTAcquisitor.setup(VGCTAcquisitor.java:170) at com.ge.med.fi.tacq.hwifc.TACQScanner.setupScan(TACQScanner.java:707) at com.ge.med.fi.tacq.scan.CTScan.apply(CTScan.java:463) ... 11 more Caused by: com.ge.med.fi.tacq.hwifc.SubSystemServiceException: Failed to perform a subsystem service. SubSystem=CTServerComm; Service=setup; Param=PFlist (ERROR_SUBSYSTEM_SERVICE,9501,ERROR) at com.ge.med.fi.tacq.hwifc.SubSystem.doService(SubSystem.java:216) at com.ge.med.fi.tacq.hwifc.SubSystem.doService(SubSystem.java:239) at com.ge.med.fi.tacq.hwifc.VG.VGCTAcquisitor.setup(VGCTAcquisitor.java:165) ... 13 more Caused by: com.ge.med.fi.tacq.scanner.ServerRequestException: Error in CT Device. (CT_ERROR_FRONTEND_RESET,6703,ERROR) at com.ge.med.fi.tacq.hwifc.SubSystem$ServerCommunicator.sendRequest(SubSystem.java:605) at com.ge.med.fi.tacq.hwifc.SubSystem.sendRequest(SubSystem.java:320) at com.ge.med.fi.tacq.hwifc.VG.VGCT.setup(VGCT.java:428) at com.ge.med.fi.tacq.hwifc.VG.VGCT$1.performService(VGCT.java:264) at com.ge.med.fi.tacq.hwifc.SubSystem.doService(SubSystem.java:214) ... 15 more Source:not stated Description:com.ge.med.fi.tacq One Day before: FE_ECHO_CHECK_ERROR:.:Hardware communication error:.:Try again Perform system reset.:.: Echo check error of Front End port: ( Port: 0xd40 on ADAM board of detector #2):.:Trace:{1} During Troubleshooting: CIB diagnostic does not pass. Found failure also during NM Static Acquisition (System down) FSE order new: CIB, PDOC and ADAM, solved with PDOC. Contributor 100008553 B.Certo May 5, 2009

Error message

FE_WRITE_PORT_ERROR Hardware communication error:.:Try again Perform system reset.:.: Failed to write Front End port: ( Port: 0xe1e on DOC board of detector #):.:Trace:{1} FE_WRITE_PORT_ERROR Error found on Syslog.csv file: FE_WRITE_PORT_ERROR:.:Hardware communication error:.:Try again Perform system reset.:.: Failed to write Front End port: ( Port: 0xe1e on DOC board of detector #2):.:Trace:{1} Example: <Date> <Time> <Source> <Msg@Subsystem> <Type> <Category> <FileName> <Line> <Phase> <App> <Detail> <UID> <RootCause> <PID> <FRU> 04/23/09 7:33:43 AM CTServer.Tacq TLT_5009@ERROR_MSG Error Fatal d:\tacq\su\src\cpp\services\fe\lowlevel\felow.cpp 148 FE_WRITE_PORT_ERROR:.:Hardware communication error:.:Try again Perform system reset.:.: Failed to write Front End port: ( Port: 0xe1e on DOC board of detector #2):.:Trace:{1} 1 DOC Warning found on CTServer.Tacq.html file: WARNING=Warning in CTServer d:\tacq\su\src\cpp\services\fe\lowlevel\felowwithcib.cpp(232) Example: 07:33:43.312 [th:02180] WARNING=Warning in CTServer d:\tacq\su\src\cpp\services\fe\lowlevel\felowwithcib.cpp(232) CibFeWrite: - Failed writing FE port: 0xe1e , CIB communication status register = 0x2 Contributor 100008553 B

Applies to

Models
Infinia
Product
Infinia HE4 Infinia II Hawkeye 4 & Infinia II GP (Infinia running Windows XP software)
Component
*Detector (Imaging Detector) *Detector (Imaging Detector) *Detector (Imaging Detector)
Area
Nuclear Medicine

Full cause & step-by-step resolution

The complete cause analysis, the step-by-step remedy for this GE Healthcare Nuclear Medicine issue are available to FSELIB subscribers — re-authored, web-first, searchable.

Start free trialSign in

7-day free trial · no credit card required

Related GE Healthcare Nuclear Medicine issues