LightSpeed 5.X (60kW)
Symptom
Scan would immediately abort after bringing up rotor and pressing start scan light. See LD for details Scan would immediately abort after bringing up rotor and pressing start scan light. This problem has been reported to occur on occasion after Performing FMI 25365 Have also seen this after setting up to scan scout, axial or any type of data collection. The start scan light will light up and then the system will lose the DARC. The DARC will no longer be up at Linux level. Customer would then shut down the system and reboot, then the scenario would repeat.
Error message
Error: 260118223 (60-0402)mA scale error See Long Description for complete error Error 260118223 orp orp_subsys gen_exec.c 2213 Host : Jedi Ermes # : 260118223 Exception Class : Abort Severity : Primary File : gen_exec.c Line# : 2213 Function : No System Function Reported Scan Type : Static Scan: 50074/1/9 (60-0402) mA scale error. mA has been measured to be either too low or too high with respect to mA demand 20 ms after the beginning of the exposure. Z6,Z7= 0h,0h
Applies to
- Models
- LightSpeed
- Product
- LightSpeed 5.X (60kW) LightSpeed 5.X (60kW) ~ Use with MDAS or GDAS HP_P_G4 HP_P_G8 HP_P_G16 HP_P_M16 LightSpeed 5.X 60KW G-DAS16 with GRE Links to the updated Product Service Manuals, FMIs, Service Notes, Option Manuals and Operator Documents can be found online at the attached sites. Always use the most appropriate documentation for your system.
- Software
- 06MW03.5 For Pathfinder 1.5 ! NOT FOR VCT ! VCT uses 06MW03.4 06MW03.5 For Pathfinder 1.5 ! NOT FOR VCT ! VCT uses 06MW03.4 06MW03.5 For Pathfinder 1.5 Reboot BEFORE and AFTER detailed cals. Used on 1X/2X/3X/4X/5X, BrightSpeed & HS QX/i with GRE Consoles ! NOT FOR VCT ! VCT uses 06MW03.4 Reboot BEFORE and AFTER detailed cals This software was released with FMI 25365 in 2nd quarter 2006. 06MW03C.5 Class C Software (tab 182 distribution) Part # 5165729 06MW03M.5 Class M Software (tab 182 distribution) Part # 5154540 Training for this software (including Network Filters) can be found at http://data.supportcentral.ge.com/upload/25823/doc_1221870.pdf BrightSpeed S/W Information: You may see 06MW03.4 or 06MW03.5 loaded on BrightSpeed Systems. Why two different Versions? The story is when the program team released the BrightSpeed M3 Pilot sites in FW10 2006, 06MW03.5 (PF1.5 M3 version) was not ready, so the program team decided to use 06MW03.4 as BrightSpeed M3 version. When 06MW03.5 was released, BrightSpeed systems phased 06MW03.5 into the production line. The only difference between the two versions is the "Rotor not at speed" issue which was resolved in 06MW03.5. For BrightSpeed systems running 06MW03.4, a patch is needed to resolve the "Rotor not at speed" issue. The patch was shipped with all BrightSpeed systems running 06MW03.4. There is no reason to upgraded BrightSpeed systems running 06MW03.4 with the rotor patch installed. For systems running 06MW03.4 verify the rotor patch is installed: [insite@ct01 ~]$ showprods | grep -i patch I patch 04/10/2006 The GNU patch command, for modifying/upgrading files. ver 2.5.4 rel 2.5.4.19 I MX200ROTOR_PATCH 04/10/2006 This is a MX200 Rotor patch for 06MW03.* ver 1 rel 1.1 For 06MW03.4 the correct classC & classM: ClassC = part# 5167665 Ver 06MW03C.4 ClassM = part# 5167597 Ver 06MW03M.4
- Area
- CT
Full cause & step-by-step resolution
The complete cause analysis, the step-by-step remedy and the attached service documents for this GE Healthcare CT issue are available to FSELIB subscribers — re-authored, web-first, searchable.
7-day free trial · no credit card required