Mammography systems · SENOGRAH family

GE Healthcare IDC Dione: troubleshooting and error codes

The ServiceForge knowledge base holds 14 documented symptoms for the GE Healthcare IDC Dione, with 21 ranked causes, 29 diagnostic checks with test points and expected values, and 7 error codes. Each symptom below shows its causes and the first check; the rest is one connection away. Connect ServiceForge to your AI

Symptoms

Detector boot incomplete or firmware load failure

Detector firmware fails to load or boot sequence does not complete; detector firmware version or signature mismatch

Ranked causes

1. Firmware file corrupted or signature mismatch (rare)
2. Power supply boot failure or timeout (occasional)

First check

Verify power supply boot completes

Test point: Power supply boot sequence
Expected: Power Supply boot done message appears

1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Detector boot sequence fails

System enters boot process but communication fails; detector firmware loads (m3_9, signature 0x40081039) and temperatures/voltages are normal, but ADS communication drops repeatedly with socket read errors.

Ranked causes

1. IDC-ADS socket communication failure or timeout (common)
2. ADS process or service not running or unresponsive (occasional)

First check

Verify detector firmware load completes

Test point: System log output
Expected: Detector FW Version m3_9 and Detector FW Signature 0x40081039 both logged without error

2 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Detector environment failed caution

ErrorFlag (11) indicates detector environment sensor failure; detector temperature, humidity, or manifold readings out of range

Ranked causes

1. Detector temperature out of operating range (common)
2. Detector humidity out of specification (occasional)

First check

Measure detector temperatures Temp1, Temp2, Temp3

Test point: Detector temperature sensors
Expected: Within operational range specified in service manual °C

1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Detector firmware loading incomplete or detector startup issue

Log shows detector firmware loaded (m3_9, signature 0x40081039, DMA memory allocated); detector boot initiated but communication or initialization may be incomplete given subsequent ADS communication failures.

Ranked causes

1. Detector firmware version mismatch or firmware load corruption (rare)
2. DMA memory allocation issue (rare)

First check

Verify detector firmware version

Test point: Detector firmware version register
Expected: m3_9

1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

IDC-ADS communication failed

System logs show inability to read ADS command header, socket closure, SendStatus task failures, and repeated communication timeouts between IDC and ADS server

Ranked causes

1. ADS socket closed or connection lost (common)
2. ReadAdsCommand timeout on 8-byte header prolog (common)

First check

Verify IDC-Conditioner link status

Test point: System startup log output
Expected: Link between IDC and Conditioner is UP

1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

IDC-ADS communication failure after detector boot

Detector boots successfully and enters MEDICAL_STATE, but repeated socket communication failures prevent image acquisition and status reporting to ADS.

Ranked causes

1. ADS socket closed unexpectedly or ADS process terminated (common)
2. Network timeout on ADS command read (occasional)

First check

Verify ADS process is running and responsive

Test point: Network connectivity and process list on ADS host
Expected: ADS listening on expected port; process active in task list

2 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

ImageAcquisitionStatus warning during boot

Detector boot transitions to IDC_WARNING state with PanelEnvironmentStatus showing IGS_NOT_FUNCTIONAL, indicating acquisition or environment subsystem issue.

Ranked causes

1. Environmental sensor or monitoring fault (rare)
2. IGS (Image Gating/Sync) module malfunction (rare)

First check

Verify humidity sensor reading is valid

Test point: System log humidity value
Expected: Humidity of the detector = 38%, 10–90% typical operating range

1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Detector booting in progress

System reports detector is in boot state; acquisition cannot proceed until complete

Ranked causes

1. Normal detector initialization sequence in progress (common)

First check

Monitor processing machine state

Test point: IDC-PROCESSING MACHINE STATE
Expected: Transition from IDC_BUSY_STATE to IDC_READY_STATE

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

IDC-ADS communication not established at boot

System logs indicate ADS communication link not ready during boot sequence

Ranked causes

1. ADS service not running or network link down (common)

First check

Verify ADS is reachable on network

Test point: 192.168.1.10
Expected: Ping successful; ADS service responding

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

ImageAcquisitionStatus warning

IDC sends ImageAcquisitionStatus:IDC_WARNING to ADS; SendStatus task fails to complete

Ranked causes

1. SendStatus task communication failure (common)

First check

Monitor SendStatus task execution

Test point: SendStatus task log
Expected: Task completes without errors

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

notifySystem semaphore timeout during boot

Boot sequence logs timeout on notifySystem semaphore; SendStatus task fails to send status to ADS

Ranked causes

1. Communication delay or task synchronization issue during state transitions (unknown)

First check

Verify ADS communication establishment

Test point: IDC-to-ADS link
Expected: Connection established before moving to MEDICAL_STATE

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Panel environment status not functional

PanelEnvironmentStatus:IGS_NOT_FUNCTIONAL sent to ADS; panel interface unavailable

Ranked causes

1. Panel communication or connection issue (occasional)

First check

Verify panel interface connectivity

Test point: Panel communication channel
Expected: Connection established and functional

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Power supply voltage levels abnormal high voltage

Detector power supply voltages show deviation from nominal values during boot sequence diagnostics

Ranked causes

1. Power supply regulation circuit not fully stabilized (occasional)

First check

Measure positive 5V supply

Test point: P5VA_SW
Expected: 4.7V

3 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Power supply voltage out of range high voltage

Negative supply voltages and positive 17V supply show deviation from nominal values (N5VA_SW -4.3V, N22V_SW -20.9V, P17V_SW 16.2V); positive 5V rail nominal at 4.7V.

Ranked causes

1. Power supply regulation or loading issue (occasional)

First check

Measure positive 5V supply rail voltage

Test point: P5VA_SW test point
Expected: 5.0V nominal, ±0.5V

3 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Error codes

Code	Meaning	Trigger	Severity
`ErrorFlag (11)`	Detector Environment Failed	Environmental monitoring subsystem detects abnormal condition or sensor failure during boot	warning
`ErrorFlag (12)`	IDC-ADS Communication failed	IDC unable to read 8-byte header prolog from ADS; socket closes during command read or image write	error
`IDC_BOOT_STATE`	IDC acquisition system in boot state	System power-on or reset	info
`IDC_BUSY_STATE`	IDC processing machine busy loading firmware	STC and FPGA initialization	info
`IDC_DIAGNOSTIC_STATE`	IDC application in diagnostic state	Intermediate state during boot sequence	info
`IDC_MEDICAL_STATE`	IDC application ready for medical imaging	All subsystems initialized and communication established	info
`IDC_READY_STATE`	IDC processing machine ready for acquisition	FPGA and DSP drivers fully initialized	info

Likely causes and actions for each code are in ServiceForge. Connect ServiceForge to your AI

Community

0 fixes logged by technicians through their AI, with outcomes, for this model.

ServiceForge knowledge base record. Field-unverified unless technicians confirmed it. A teaching summary of the record, not a service manual. Export 2026-10-14.