Pular para o conteúdo principal
GE Healthcare · CTLightSpeed29000902329000901229000901029000900931809

LightSpeed 5.X (60kW)

Symptom

System will not scan helical images Troubleshooting 1) Check the VDARC /var/log/messages: rsh darc cat /var/log/messages Dec 6 11:08:47 darc recon_control[2717]: FILE: recon_control_cb.cxx, LINE: 397. Lost connection with IG. fd: 44 Dec 6 11:08:54 darc data_restore: ERROR: Checksum mismatch for view 1241 expected:0xc32731e, got 0xc32741e, file = md as_intf_object.cxx, line = 370 Dec 6 11:09:05 darc last message repeated 3 times Dec 6 11:09:07 darc data_restore: ERROR: Sender thread failed sending view data file = sender_thread_object.cxx, line = 634 Dec 6 11:09:07 darc data_restore: ERROR: Sender thread failed sending view block header file = sender_thread_object.cxx line = 693 So far the above points to scan files corruption 2) An indication to DARC software corruption is IG0 in the errors. The VDARC assigns the IG's starting with IG1. IG0 is not present in the configuration.

Error message

Error: 290009023 Resetting IG (1,2,3) because it has reached max consecutive retries: 4 See Long Description for complete error. Error: 290009023 Resetting IG (1,2,3) because it has reached max consecutive retries: 4 Sun May 14 13:40:24 2006 Error: 290009023 Host: darc Process: recon_control File: IG_interface_list.cxx Line: 1272 Resetting ig2 because it has reached max consecutive retries: 4 Note: This could be IG1, IG2, IG3

Error: 290009012 Lost connection with IG(X) X =ig number that failed ie 1, 2 or 3 See the LD for the complete error code Error: 290009012 Lost connection with IG(X) X =ig number that failed ie 1, 2 or 3 Tue Apr 19 12:44:41 2005 Error: 290009012 Host: darc Process: recon_control File: recon_control_cb.cxx Line: 393 Lost connection with IG1 in fd: 33. Fri Oct 6 08:29:53 2006 Error: 290009012 Host: darc Process: recon_control File: recon_control_cb.cxx Line: 419 Socket event on 3, fd: 43.

Error: 290009010 Image suspended due to: image installed with status -1. See long description for full error Fri Sep 30 15:00:17 2005 Error: 290009010 Host: darc Process: recon_control File: ImageSetRequest.cxx Line: 4129 Function: Image Generation : SBC Processing Job Type: R

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

Related GE Healthcare CT issues