CT scanners

Picker Q: troubleshooting and error codes

The ServiceForge knowledge base holds 16 documented symptoms for the Picker Q, with 20 ranked causes, 7 diagnostic checks with test points and expected values, and 123 error codes. Each symptom below shows its causes and the first check; the rest is one connection away. Connect ServiceForge to your AI

Symptoms

Couch is not moving patient safety

CT scanner table fails to respond to movement commands in servo mode

Ranked causes

1. Programmed position interrupt not enabled or failed to occur within expected time (common)
2. Data cable cut or DREQ signal grounded (occasional)

First check

Verify exposure armed signal

Test point: XSC STAT register 5th nibble, Bit 1
Expected: Bit 1 = 1 (exposure armed)

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

Data acquisition did not complete properly

Either MPM or GPU failed to complete data acquisition correctly. Possible DAVG bit stuck on DPPC or faulty GPU.

Ranked causes

1. DAVG bit stuck on DPPC (unknown)
2. GPU data acquisition malfunction (unknown)

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Invalid GPU command received caution

Graphics Processing Unit cannot process command from touchpanel; couch or scanner function rejected

Ranked causes

1. GPU not programmed to understand command or GPU in incompatible state (occasional)
2. Crash pad engaged during scan or pilot (rare)

First check

Verify GPU state

Test point: GPU status register
Expected: GPU not in active scan or pilot mode when new command issued

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

SIF FIFO status error during or after scan

Incorrect SIF FIFO status detected. FIFO overflow bit should never be set during or after scan; FIFO empty bit should be set after scan completes.

Ranked causes

1. FIFO overflow during scan or improper status during acquisition (unknown)
2. FIFO empty bit not set after scan (unknown)

First check

Monitor FIFO status during scan

Test point: FIFO status register
Expected: Overflow bit=0 during scan, Empty bit=1 after scan completion

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

ANB error during scan communication

Error in communication with GPU or XSC. Max retries indicates loss of communications; max errors indicate faulty communication quality.

Ranked causes

1. XSC communication fault via Slip Rings 9, 10, 11, 12 (unknown)

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

Bad function parameter from GPU or XSC

Parameter returned from GPU or XSC does not match parameter sent by SIF

Ranked causes

1. GPU or XSC command echo mismatch (unknown)

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

DMA channel timeout waiting for data

Data Acquisition Manager waiting for data on DMA channel but timeout occurred

Ranked causes

1. DMA data source not providing data or DMA channel inactive (unknown)

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

Exposure delay request not executed before next exposure

Normal delay request by XSC was not completed before the next exposure request was issued

Ranked causes

1. XSC delay request timeout or queue overflow (unknown)

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

GPU device state error

GPU in unexpected device state. ASCII message contains device in error and expected state; actual state is in SIF error buffer.

Ranked causes

1. GPU state machine error or initialization failure (unknown)

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

GPU/XSC command reply does not match request

Command sent by SIF does not match the reply received from GPU or XSC

Ranked causes

1. GPU or XSC processing error or response error (unknown)

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

Illegal SIF command for current state

Computer attempted command that is illegal given SIF's current operational state

Ranked causes

1. Software command sequencing error or state machine logic error (unknown)

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

Laser pilot positioning error during scan frame calibration radiation

Laser is turned on while scan frame is positioned for pilot scan, generating error condition

Ranked causes

1. Operator activates laser during pilot scan frame position (unknown)

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

SIF fatal error: cannot boot

SIF cannot boot and is inoperable. System cannot function without operational SIF.

Ranked causes

1. SIF board hardware fault or firmware corruption (common)

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

SIF state machine error during action

Action started by SIF is incompatible with SIF's current operational state

Ranked causes

1. SIF state machine logic error or state transition fault (unknown)

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

X-ray system interlock preventing exposure high voltage

X-ray main contactor not energized or X-ray interlock condition active

Ranked causes

1. X-ray main contactor fault or interlock active (unknown)

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

XSC device state error

XSC in unexpected device state. ASCII message contains device in error and expected state; actual state is in SIF error buffer. Check XSC STAT 2nd LSB nibble Bit 4 for boot status.

Ranked causes

1. XSC boot failure or improper initialization (unknown)

First check

Check XSC STAT register bit 4 (boot status indicator)

Test point: XSC STAT register, 2nd LSB nibble, Bit 4
Expected: Bit 4 = 0 (boot successful)

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

Error codes

Code	Meaning	Trigger	Severity
`1`	Create exchange failure	Failure to create message exchange object in operating system	error
`10`	Cannot ident process	Failure to identify or locate process	warning
`100`	Cannot get a Regulus Server	System attempts to obtain Regulus Server connection	error
`1000-1099`	Scan errors reported by the XSC	Scan acquisition or XSC operation	error
`100-120`	RpIOS errors	RpIOS operating system operation	error
`1002`	High voltage interface driver error	High voltage interface failure	critical
`1003`	Low speed rotor software error	Low speed rotor control failure	error
`1004`	Small drives error	Small drive system failure	error
`1005`	Filament software error	Filament control system failure	error
`1006`	X-ray software error	X-ray generation failure	critical
`1007`	Kill error - XSC rebooted software	XSC software reset or crash	warning
`1008`	X-ray overtime error	X-ray exposure time exceeded	warning
`1009`	Heat calculator error	Heat calculation system failure	warning
`101`	Return/release a Regulus Server	System attempts to return or release Regulus Server	error
`1010`	Low speed rotor hardware error	Low speed rotor mechanical or electrical failure	error
`1011`	HVPSI hardware error	High voltage power supply interface hardware failure	critical
`1012`	CRX Generator Error	Generator control fault detected	error
`1013`	XSC Fault Latch Error	XSC fault latch activated	error
`1014`	Heat Calculator Error	Heat calculation subsystem failure	error
`1016`	High Speed Starter Fault Latch	Starter fault latch activated	error
`1017`	High Speed Starter Driver Error	Starter driver fault detected	error
`1018`	Improper ESTOP Sequencing	Emergency stop sequence violation	warning
`102`	Cannot receive message from regulus queue	System attempts to receive message from Regulus queue	error
`103`	Cannot send message to regulus queue	System attempts to send message to Regulus queue	error
`104`	Unable to get message from regulus queue	System attempts to retrieve message from Regulus queue	error
`105`	cannot open a file	File I/O operation attempted	error
`106`	cannot close a file	File close operation attempted	error
`107`	cannot read a file	File read operation attempted	error
`108`	cannot write to a file	File write operation attempted	error
`109`	cannot lseek in a file	File seek operation attempted	error
`11`	Cannot delete process	Failure to terminate or delete process	error
`110`	cannot change/set mode of file	File mode change operation attempted	error
`1-10`	Scan and pipp setup errors	System startup or scan initialization	error
`1100-1199`	DAQMAN Errors	Data acquisition manager subsystem error	error
`111`	cannot restart an agent	Agent restart requested	error
`112`	cannot download a task into an agent	Task download to agent attempted	error
`11-25`	File system errors	File system operation or access	error
`113`	cannot reassign ownership of a task	Task ownership change requested	error
`114`	rplwrite error (Regulus to PSOS write)	Regulus to PSOS write operation	error
`116`	cannot find board	Board detection or access attempted	error
`12`	Cannot suspend process	System attempts to suspend a process	error
`1200-1299`	Calibration Former Errors	Calibration subsystem error	error
`13`	Cannot resume process	System attempts to resume a suspended process	error
`14`	Cannot change priority	System attempts to change process priority	error
`15`	Cannot change mode	System attempts to change process mode	error
`1501-1536`	Scheduler Errors	Image reconstruction request queue or execution failure	error
`150-199`	Regulus errors	Regulus module operation	error
`151`	message control call fails	Message control system called	error
`152`	PIPE function fails	PIPE function called	error
`153`	cannot read pipe	Pipe read operation attempted	error
`154`	cannot write pipe	Pipe write operation attempted	error
`1540-1544`	Optable Manager Error	Optable buffer management fault	error
`1545-1546`	Internal Communications Error	Communication fault between Control processes	error
`1547-1575`	Optable Manager Error	Optable buffer management fault	error
`155`	cannot close pipe	Pipe close operation attempted	error
`156`	cannot fork	Process fork operation attempted	error
`157`	cannot activate task	Task activation requested	error
`1576-1596`	Data Manager Error	Data buffer management failure	error
`1599`	Boot Control Error	High level boot or initialization failure	critical
`16`	Cannot change to supervisor mode	System attempts to elevate to supervisor mode	error
`1601-1609`	Memory Manager Error	Memory usage tracking failure	error
`17`	Cannot allocate segment	System attempts to allocate memory segment	error
`18`	Cannot free segment	System attempts to deallocate memory segment	error
`19`	Cannot assign segment	System attempts to assign segment to process	error
`2`	Attach to exchange error	Failure to attach to existing message exchange	error
`20`	Cannot grab segment	System attempts to acquire segment lock	error
`2002`	Data Acquisition error during scan	DINT count fails to increase from zero at start, does not reach expected value at completion, or stops increasing mid-scan	error
`200-299`	Database errors	Database operation or access	error
`2003`	Invalid System Identifier	System switch setting on CTCC board is not IQ, HP, PGS1, or PGS2	error
`2004`	Door Open during scan	Scan room door is open while scan is in progress	error
`2006`	Invalid GPU Command	GPU receives command from touchpanel that it cannot process due to incompatible state or unknown command type	error
`2007`	Interference Limit exceeded	Couch positioned too close to gantry during horizontal or vertical servo motion or gantry tilt operation	warning
`2008`	Register Load error	GPU parameter register contents do not match values loaded after write and read verification check	critical
`2009`	Vertical Motion error	Couch vertical position changes by more than 3 mm during 50 msec scan interval	error
`21`	Cannot create partition	System attempts to create new partition	error
`22`	Cannot delete partition	System attempts to delete partition	error
`23`	Cannot get buffer	System attempts to allocate buffer	error
`24`	Cannot return buffer	System attempts to deallocate buffer	error
`25`	Cannot send signal	System attempts to send interprocess signal	error
`26`	No event received	System waits for expected event	warning
`26-99`	Program errors	Software execution or operation	warning
`27`	Same as 26 (no event received)	System waits for expected event	warning
`28`	Pause P error	System attempts pause operation	error
`29`	Announce T error	System attempts announcement operation	error
`3`	reqx function failure or SIF problem	Request exchange operation failed; possibly due to SIF hardware issue	error
`30`	Time and date are not set	System checks time/date configuration on startup	warning
`300-324`	System Monitor Board or Autovoice errors	System monitor or autovoice operation	error
`31`	Error setting time and date	System attempts to set time and date	error
`32`	Cannot initialize device	System attempts device initialization	error
`33`	Cannot open device for I/O	System attempts to open device file	error
`34`	Cannot close device after I/O	System attempts to close device after operation	error
`35`	Cannot read from device	System attempts to read data from device	error
`36`	Cannot write to device	System attempts to write data to device	error
`37`	Device control error	System attempts device control operation	error
`38`	Exception error (Task Died, Reboot!)	System encounters unhandled exception in task	critical
`4`	sendx function failure or SIF problem	Send exchange operation failed; possibly due to SIF hardware issue	error
`400-449`	Opcom errors	Opcom module operation	error
`450-499`	Display errors	Display subsystem operation	error
`5`	Cannot delete exchange	Failure to delete message exchange object	error
`50`	Cannot read (PPLREAD) from another agent	System attempts PPLREAD from remote agent	error
`500-599`	Scan errors reported by the SIF	Scan acquisition or SIF operation	error
`51`	PPCREATEX - creating exchange on another PSOS board fails	System attempts to create exchange on remote PSOS board	error
`512`	ANB error - Communication failure with GPU or XSC	Max retries on communication to GPU or XSC exceeded	error
`513`	Bad function parameter - GPU/XSC parameter mismatch	Parameter returned from GPU/XSC does not match parameter sent by SIF	error
`514`	X-ray error - Exposure prevention	X-ray main contactor not energized or safety interlock enabled	error
`515`	Bad function returned parameter - Command/reply mismatch	SIF command does not match GPU/XSC reply	error
`516`	Exposure request error - Timing violation	Exposure request issued before XSC delay request completed	error
`517`	Bad SIF state error - Incompatible state transition	SIF action initiated that is invalid for current SIF state	error
`518`	Bad SIF command error - Illegal command for state	Computer attempts command illegal for current SIF state	error
`519`	Data acquisition not complete - Acquisition failure	MPM or GPU did not complete data acquisition properly	error
`520`	Bad FIFO status error - FIFO overflow or status error	FIFO overflow detected during scan or FIFO not empty after scan	error
`523`	DMA channel timeout - Data acquisition timeout	Data Acquisition Manager waiting for DMA data; timeout occurred	error
`524`	XSC state error - XSC device state fault	XSC in unexpected state during operation	error
`525`	GPU state error - GPU device state fault	GPU in unexpected state during operation	error
`526`	SIF fatal error - SIF inoperable	SIF cannot boot; system is non-functional	critical
`527`	Laser at pilot start error - Laser positioning conflict	Laser activated while scan frame positioned for pilot scan	warning
`6`	Cannot free process	Failure to deallocate process resources	error
`600-699`	Scareman errors	Scareman module operation	error
`7`	Cannot send a message	Failure to send message on exchange	error
`700-799`	Network errors	Network communication or operation	error
`8`	Cannot spawn task	Failure to create new process/task	error
`800-899`	Auto_Cal errors	Auto_Cal calibration operation	error
`9`	Cannot activate process	Failure to activate or resume suspended process	error

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.