Fluoroscopy systems · Arcadis family

Siemens Healthineers Arcadis Orbic: troubleshooting and error codes

The ServiceForge knowledge base holds 106 documented symptoms for the Siemens Healthineers Arcadis Orbic, with 157 ranked causes, 172 diagnostic checks with test points and expected values, and 128 error codes. Each symptom below shows its causes and the first check; the rest is one connection away. Connect ServiceForge to your AI

Symptoms

Image transfer from remote system to local system fails

DICOM image transfer aborts; session terminated by sender; error messages appear in UI and event log

Ranked causes

1. Configuration problem with remote system (common)
2. Network connectivity issue (common)
3. Presentation Context rejected during Association Negotiation (occasional)
4. Wrong or missing command set request at T7 level (occasional)
5. Transfer Syntax causes problems or is required but not sent (occasional)
6. Timeout in message stream (occasional)
7. Timeout waiting for transfer response (occasional)
8. Local system fails to enter image in local database (occasional)

First check

Verify remote system configuration at local system

Test point: Network Nodes configuration
Expected: Remote system correctly configured

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

TCP/IP ping fails

Connection failed error messages in UI; remote node does not respond. Event log shows association errors; merge log shows TCP init errors or timeout.

Ranked causes

1. Network problems or configuration error (common)
2. Wrong IP address, subnet mask, or gateway configuration (common)
3. Network cable not connected at hub or switch (occasional)
4. Domain Name Service (DNS) misconfiguration or failure (occasional)
5. Gateway not accessible or incorrectly configured (occasional)
6. Network collisions or poor performance (occasional)
7. Problem in remote system (occasional)

First check

Examine merge log for TCP/IP init error

Test point: merge_stu.log, merge_hc.log, merge_HRI.log
Expected: No 'TCP/IP init error' or 'timeout in select()' messages

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

DICOM verification fails with TCP/IP ping OK

UI shows 'No response from node name'; Event log shows 'Could not open association with remote node / service not acceptable'; Merge log shows 'E: TCP init error'

Ranked causes

1. AET or port number of remote system is wrong (common)
2. Remote process is not running (common)
3. Remote system does not support DICOM verification (SCP) (rare)
4. Remote system is SCU only; C_ECHO not supported (occasional)

First check

Verify AET and port number configuration

Test point: Service Tool Configuration
Expected: Remote system AET and port match Conformance Statement

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

Search platform logical name breaks down during searching

UI and Event log show 'Logical name breaks down during searching'; Merge log shows 'E: Peer aborted association'

Ranked causes

1. Any error on DICOM level (unknown)
2. Local SCU does not send TCP/IP packets or network switch does not forward message (occasional)
3. Network switch does not forward DICOM verification message (occasional)
4. Our local AET not correctly configured at remote system (occasional)

First check

Review DICOM merge.log for error messages

Test point: merge_stu.log, merge_hc.log, merge_HRI.log
Expected: Error message describing DICOM-level issue

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

C-arm motion limit switches not functioning caution

C-arm does not stop at mechanical limits or limit switches fail to activate before mechanical end-stop is reached.

Ranked causes

1. Limit switch misadjusted (common)
2. Limit switch cabling faulty or disconnected (common)
3. Limit switches installed upside-down or reversed (occasional)

First check

Test limit switch activation during C-arm motion

Test point: Limit switches on C-arm assembly
Expected: Limit switches engage before C-arm reaches mechanical limit stop

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

Calibration: C-arm limit switch verification caution

Manual C-arm orbital movement and limit switch actuation requires verification

Ranked causes

1. Limit switch not actuating at proper position (occasional)
2. Limit switch misalignment (occasional)
3. Limit switch cable fault (occasional)

First check

Remove cable module cover

Test point: Cable module enclosure
Expected: Cover removed safely, mechanical components accessible

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

Coupling unit defective or 24V power missing high voltage

Coupling unit is not functioning; either 24V supply is absent or unit hardware is faulty.

Ranked causes

1. Fuse F2 on PCB D200 is open (common)
2. 24V supply voltage missing at coupling unit (common)
3. Coupling unit hardware failure (occasional)

First check

Check fuse F2 on printed circuit board D200

Test point: PCB D200 fuse F2
Expected: Fuse intact and not open

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

Disk space low on C: or D: drive

System may have insufficient free space for operations; affects file storage and temporary operations.

Ranked causes

1. Temp directory contains large files (common)
2. Patient data stored locally instead of archived (occasional)
3. CD-ROM write jobs remain in AN_CDR_DIR after process complete (occasional)

First check

Verify free space on C: drive meets minimum

Test point: C: drive Properties
Expected: at least 15% of capacity as free space

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

FTP transfer fails

IP connection to SRS server is working but functional check of FTP transfer fails; cannot upload diagnostic data via FTP protocol

Ranked causes

1. FTP configuration is incorrect (common)
2. FTP account or password settings incorrect (common)
3. FTP port blocked by firewall in hospital network (occasional)

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

IP connection to SRS server fails

System cannot establish network connection to remote service server at 194.138.39.18; tracert command shows 'Destination host unreachable' after maximum hops

Ranked causes

1. Default gateway or static route not correctly defined (common)
2. Customer router not correctly installed or configured (common)
3. Hospital routing incorrect when system and router not in same network (occasional)

First check

Verify static route configuration

Test point: Command interpreter
Expected: route print output showing configured gateway

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

No network connection available

System cannot communicate with network resources; affects patient archiving and data sharing.

Ranked causes

1. Network cable disconnected or faulty (common)
2. TCP/IP configuration incorrect (common)
3. Navigation system not responding (occasional)

First check

Test connection to navigation system

Test point: Service software Configuration > Network nodes
Expected: Host name and TCP/IP address displayed; Test successful

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

No network transfer via DICOM

DICOM services cannot transfer data over TCP/IP network; remote systems are unreachable

Ranked causes

1. Network problems (common)
2. Configuration problem (common)
3. DICOM process not started (occasional)

First check

Verify network connectivity using TCP/IP ping

Test point: Remote DICOM nodes
Expected: Ping response received

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

USB-to-CAN adapter not functioning

Communication with CAN bus or navigation system fails; indicator light not green or device not recognized by system.

Ranked causes

1. USB-to-CAN module LED not green (common)
2. USB-to-CAN module driver not installed or corrupted (common)
3. Cable connection issue between main system and imaging system (common)

First check

Verify USB-to-CAN module LED indicator

Test point: USB-to-CAN compact module
Expected: LED is green

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

Access to CS knowledge base fails

Intranet address entered for CS knowledge base is not reachable; tracert output shows 'Destination host unreachable'

Ranked causes

1. Intranet address entered is incorrect (common)
2. Internet Explorer configuration is incorrect (occasional)

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

CAN bus connection to main system not established

System cannot communicate with main system via CAN bus; coupling or communication failure.

Ranked causes

1. Monitor trolley not connected to main system or cable faulty (common)
2. USB-to-CAN adapter not connected or LED not green (common)

First check

Verify physical connection to main system

Test point: Main system connection cable at monitor trolley rear
Expected: Cable securely connected; no bent contacts at plug

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

Capture DICOM traffic for remote analysis by specialist

DICOM transfer fails and local troubleshooting is insufficient; specialist requires captured network traffic or local test receiver data

Ranked causes

1. Specialist needs detailed packet or log analysis to diagnose network or protocol issues (unknown)
2. Network traffic capture not possible; alternative is to capture image with test receiver (occasional)

First check

If possible, capture DICOM transfer using network analyzer (snoop or NetXray)

Test point: Network interface on sending or receiving system
Expected: Captured DICOM packet trace file (.pcap or .cap format)

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

DICOM image transfer fails with wrong or missing command set request

T7 level command set request is incorrect or not sent; association may have failed at T3 level

Ranked causes

1. T7 command set not sent because Association Negotiation (T3) failed (common)
2. Extended negotiation SCU/SCP roles not supported by peer system (occasional)

First check

Enable T3 and T7 trace levels in merge_stu.log; send test image

Test point: syngo DICOM Service Tools - Storage - Extend Trace Level, merge_stu.log
Expected: T3 shows Association Negotiation succeeded; T7 shows command set request sent

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

DICOM image transfer timeout in message stream or waiting for response

Transfer stalls or times out in the middle of the message stream; timeout while waiting for successful transfer response

Ranked causes

1. Inactivity timeout too short for slow network or large image (occasional)
2. Read PDU timeout too short; remote system slow to respond (occasional)

First check

Examine merge_stu.log for timeout error: 'timeout in the middle of the stream'

Test point: merge_stu.log Analysis tool
Expected: Log shows timeout error location and timestamp

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

DICOM image transfer to remote system fails at association negotiation

DICOM association negotiation fails during image transfer to remote DICOM system; session aborted by sender

Ranked causes

1. Network connectivity issue between systems (common)
2. Association negotiation protocol failure or service incompatibility (occasional)

First check

Verify network connectivity (see network troubleshooting reference)

Test point: Network link between systems
Expected: Network connection established and stable

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

DICOM image transfer to remote system fails during association negotiation

Session aborted by sender with error 'Session aborted by sender (40003) and service is unacceptable (30023)' during T3 association negotiation phase

Ranked causes

1. Network connectivity issue between systems (common)
2. DICOM Association Negotiation parameters mismatch or Presentation Context rejected (occasional)

First check

Enable trace level T3 in merge_stu.log to capture Association Negotiation Request/Response

Test point: syngo DICOM Service Tools - Storage - Extend Trace Level
Expected: T3 trace enabled; merge_stu.log file available

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

DICOM remote system cannot process transferred image or service failures

Remote system receives image but fails to store or display it; remote system database insertion fails; service errors occur on remote side

Ranked causes

1. Remote system internal database error or local process interference (occasional)
2. Remote system unable to validate or display image attributes (occasional)

First check

Try sending image from different modality or application

Test point: Remote DICOM storage provider, AET and port
Expected: Image from different source accepted and stored on remote system

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

DICOM retrieve of selected data fails

Query/retrieve operation does not complete; images not transferred to local system

Ranked causes

1. C_MOVE request fails due to incorrect AETs (common)
2. C_STORE fails on separate association (common)

First check

Verify network level connectivity

Test point: Network path between systems
Expected: Network connectivity established

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

Emergency stop button inoperative patient safety

Pressing emergency stop button does not block vertical lift, or lift cannot be resumed after release

Ranked causes

1. Emergency stop switch electrical circuit fault (rare)
2. Emergency stop button release mechanism stuck (occasional)

First check

Press emergency stop switch

Test point: Emergency stop button
Expected: Vertical lift motor stops and does not respond to raise/lower buttons

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

I.I. laser light localizer function defective

Laser diodes non-functional or laser light fan beams not adjustable to focal point of tube housing

Ranked causes

1. Laser diodes failed (occasional)
2. Laser beam alignment out of adjustment (occasional)

First check

Test laser diode function

Test point: Laser diodes
Expected: Laser diodes emit light

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

I.I. laser light localizer mechanics damaged caution

Image intensifier laser light localizer shows mechanical damage, loose components, or improper seating

Ranked causes

1. Impact or wear on I.I. laser light localizer (unknown)
2. I.I. ring loose or damaged (occasional)

First check

Inspect I.I. laser light localizer for damage

Test point: Integrated I.I. laser light localizer
Expected: No visible damage

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

No 24V supply at D10 connector

System electronics does not provide required 24V power to 3D drive subsystem

Ranked causes

1. System electronics D200 defective (common)
2. Fuse F1 open on D200 (occasional)

First check

Inspect fuse F1 on printed circuit board D200

Test point: fuse F1, D200
Expected: fuse intact

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

USB-to-CAN module not detected or not functioning

CAN board fails to appear in control panel or test returns unsuccessful results

Ranked causes

1. USB-to-CAN module driver not installed or module disconnected (common)
2. USB-to-CAN module hardware failure (rare)

First check

Verify USB-to-CAN module appears in Interfaces control panel

Test point: Control panel Interfaces dialog
Expected: Board appears in dialog box

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

3D license not recognized after upgrade to Orbic 3D

System does not properly recognize the 3D license after an upgrade to the system type Orbic 3D

Ranked causes

1. System type not applied after upgrade (common)

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

3D reconstruction function

3D reconstruction system must function properly and meet performance specifications

Ranked causes

1. 3D reconstruction system malfunction or error (unknown)

First check

Test 3D reconstruction system

Test point: 3D reconstruction hardware and software
Expected: System produces valid 3D images

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

3D reconstruction with navigation system

3D reconstruction in combination with navigation system must function properly

Ranked causes

1. Combined 3D and navigation system malfunction (unknown)

First check

Test integrated 3D and navigation

Test point: 3D reconstruction and navigation system
Expected: Systems integrate and function properly

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

Accessory condition patient safety

Undamaged accessories must be in use to ensure safe operation

Ranked causes

1. Damaged or defective accessories in use (unknown)

First check

Verify accessories are undamaged

Test point: All installed accessories
Expected: All accessories undamaged and functional

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

C-arm movement restricted or noisy caution

C-arm movements exhibit slackness in bearings, noise during operation, or resistance to smooth motion

Ranked causes

1. Bearing wear or contamination (occasional)

First check

Test C-arm movement through full range

Test point: C-arm bearings and joints
Expected: Smooth movement with no slackness or noise

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

Cable and cable guide integrity high voltage

Cables and cable guides may be loose or damaged, affecting electrical safety

Ranked causes

1. Loose or damaged cables and cable guides (unknown)

First check

Inspect cables and cable guides

Test point: All cable routing and guides
Expected: All cables secure and undamaged

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

Cable deflectors damaged or misaligned caution

Physical damage or improper positioning of cable deflectors on stand or monitor trolley

Ranked causes

1. Impact or wear damage to cable deflectors (unknown)

First check

Inspect cable deflectors for damage and proper positioning

Test point: Stand and monitor trolley cable deflectors
Expected: Intact, properly secured, no cracks or deformation

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

Cable deflectors damaged or missing caution

Cable deflectors on stand or monitor trolley show visible damage, cracks, or are missing

Ranked causes

1. Wear or impact damage (unknown)

First check

Visual inspection of cable deflectors

Test point: Stand and monitor trolley cable deflectors
Expected: Intact with no visible damage

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

Cable, belt, and spindle wear caution

Wire cables, belts, and spindles must be free of wear and tear

Ranked causes

1. Worn or damaged cables, belts, or spindles (unknown)

First check

Inspect cables, belts, and spindles

Test point: Lifting column, 3D reconstruction system
Expected: No visible wear or damage

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

Calibration: 3D adjustment repeat

3D adjustment and orbital movement calibration repeated after limit switch verification

Ranked causes

1. 3D adjustment re-verification required after hardware work (unknown)

First check

Access 3D adjustment menu

Test point: Service software Main system
Expected: 3D adjustment/potentiometer option accessible

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

Calibration: Angulation potentiometer adjustment

Orbital and angulation potentiometers require adjustment via service software

Ranked causes

1. Potentiometer calibration required (unknown)

First check

Access potentiometer adjustment menu

Test point: Service software Main system menu
Expected: 3D adjustment/potentiometer option available

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

Calibration: C-arm position alignment caution

C-arm requires positioning according to service UI reference image

Ranked causes

1. C-arm position misalignment (unknown)

First check

Display service UI reference position

Test point: Service UI screen
Expected: Reference image of correct C-arm position visible

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

Calibration: Edge enhancement filter configuration

Maximum number of edge enhancement filters per examination set requires adjustment

Ranked causes

1. Edge enhancement filter count needs configuration (unknown)

First check

Open service software

Test point: Configuration menu
Expected: Service software displays Configuration option

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

Calibration: Laser light localizer (April 2006 models)

Verify and adjust laser diode function and beam alignment on image intensifier focal point

Ranked causes

1. Routine maintenance per service schedule (common)

First check

Test laser diode operation

Test point: Laser diodes in localizer
Expected: Diodes emit visible light

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

Calibration: LUT configuration

Maximum number of LUTs per examination set requires adjustment in service software

Ranked causes

1. LUT count needs configuration (unknown)

First check

Open service software

Test point: Configuration menu
Expected: Service software displays Configuration option

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

Calibration: System calibration

3D imaging system or navigation system requires full calibration procedure

Ranked causes

1. System calibration needed (unknown)

First check

Access system calibration menu

Test point: Service software Main system
Expected: 3D calibration option for ORBIC 3D visible

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

Calibration: Use PC Diagnosis software

Diagnostic maintenance procedure using PC Diagnosis software to check system health including drivers and hard drive

Ranked causes

1. Routine maintenance or system verification required (unknown)

Codonics printer hardcopy printing fails from base unit

Printing may fail when hardcopy is initiated from the base unit if the Codonics printer parameter is not properly configured

Ranked causes

1. Parameter "Hardcopy button sends image to film task card" not activated on Codonics printer (unknown)

First check

Verify Hardcopy button parameter is activated

Test point: Codonics printer settings
Expected: Parameter "Hardcopy button sends image to film task card" is enabled

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

Codonics printer print job fails from base unit

Printing may fail when initiated from base unit if Hardcopy button parameter not configured

Ranked causes

1. Hardcopy button parameter not enabled on Codonics printer (common)

First check

Verify Hardcopy button parameter status

Test point: Codonics printer settings
Expected: Hardcopy button sends image to film task card enabled

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

Collision protection functioning patient safety

Collision protection system must properly stop system movements when activated

Ranked causes

1. Collision protection system malfunction or damage (unknown)

First check

Verify collision protection presence

Test point: Collision protection system
Expected: System present and functional if installed

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

Cover panels damaged caution

Physical damage visible on cover panels of stand or monitor trolley

Ranked causes

1. Impact or wear damage to cover panels (unknown)

First check

Inspect cover panels for mechanical damage

Test point: ARCADIS Orbic stand and monitor trolley covers
Expected: No cracks, dents, or breaks

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

DICOM image transfer fails with non-zero status code in command set response

T7 level command set response returns status code other than 0 (success); transfer was rejected or resource error occurred

Ranked causes

1. Status 0xA7xx indicates out of resources on remote system or incorrect attribute in dataset (occasional)

First check

Enable T2, T3, and T7 trace levels; send test image and capture response status code

Test point: merge_stu.log, T7 status code field
Expected: T7 response status = '0' for successful transfer

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

DICOM transfer fails due to transfer syntax encoding problems or JPEG decoding

Image transfer fails with value representation or JPEG decoding error; explicit VR transfer syntax causes problems

Ranked causes

1. Remote system does not support explicit VR or JPEG transfer syntax (occasional)

First check

Review transfer syntax setting in syngo Configuration DICOM network nodes

Test point: syngo Configuration > DICOM > network nodes
Expected: Currently enabled transfer syntax is either explicit VR or JPEG

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

Driver error detected in Device Manager

One or more files displayed in Device Manager marked in red or with question mark, indicating driver malfunction

Ranked causes

1. Missing or corrupted device driver (unknown)

First check

Open Device Manager and inspect for error indicators

Test point: Device Manager display
Expected: No files marked in red or with question mark
Tools: Windows Device Manager

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

Dual monitor setting lost

Dual monitor configuration is not retained, typically after monitor replacement or system fault.

Ranked causes

1. Defective monitor or monitor replacement (common)

First check

Access service software utilities menu

Test point: Service software interface
Expected: Utilities menu accessible

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

Emergency stop switch functional patient safety

Emergency stop switches must be fully functional for operator safety

Ranked causes

1. Damaged or non-responsive emergency stop switch (unknown)

First check

Test emergency stop switch activation

Test point: Emergency stop button
Expected: System stops immediately when activated

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

Error 0001 appears after main system software download

Error 0001 displayed on base unit display following main system software download

Ranked causes

1. Software download incomplete or system state not refreshed (common)

First check

Verify error 0001 is displayed on base unit

Test point: base unit display
Expected: Error 0001 visible

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

Error code 30023 in DICOM session

DICOM session error 30023 - service unacceptable

Ranked causes

1. DICOM service or presentation context not supported by remote system (unknown)

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

Error code 40003 in DICOM session

DICOM session aborted by sender with error code 40003

Ranked causes

1. Service unacceptable or association negotiation failure (unknown)

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

Foot brakes ineffective patient safety

ARCADIS Orbic stand or monitor cart moves or rolls when brakes applied on flat surface

Ranked causes

1. Brake pads worn or brake mechanism faulty (occasional)

First check

Test foot brake effectiveness

Test point: Foot brakes on stand and monitor cart
Expected: Equipment remains stationary when brakes engaged on flat surface

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

Ground wire resistance measurement high voltage

Protective conductor resistance must be measured and evaluated

Ranked causes

1. Elevated or excessive ground wire resistance (unknown)

First check

Measure ground wire resistance

Test point: Protective conductor circuit
Expected: Resistance within acceptable limits
Tools: Ground resistance meter

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

Hard drive errors or bad sectors

Hard drive contains file system errors or bad sectors that may affect system performance or data integrity

Ranked causes

1. File system errors or corrupted sectors on hard drive (unknown)

First check

Run disk check utility on hard drive

Test point: Hard drive
Expected: Checking disk completes without critical errors
Tools: Windows Disk Check

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

Hard drive fragmentation

Hard drive file system is fragmented, potentially affecting access speed and system performance

Ranked causes

1. File fragmentation on hard drive (unknown)

First check

Analyze hard drive fragmentation status

Test point: Hard drive
Expected: Analysis indicates defragmentation needed or not needed
Tools: Windows Defragmentation Utility

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

More symptoms

Host name or IP address changes not applied
ID labels missing or illegible
Images loaded in viewing application consuming resources
Imaging system PC defect
Integrated I.I. laser light localizer function check
Integrated I.I. laser light localizer mechanics damaged
Integrated laser light localizer near tube function check
IP address conflict detected
IQ quick test
Laser light localizer near tube mechanics damaged
Leakage current exceeds limit
Leakage current measurement
Lifting column noisy or obstructed
Mechanical parts clean and lubricated
Mobile equipment wheels and brakes
Monitor 1 not properly recognized
Monitor damaged or improperly mounted
Monitor enters hibernate mode instead of shutting down
Monitor trolley remains powered after system shutdown
Motor does not move when starting 3D scan
Navigation system I.I. ring damaged
Operating controls and indicators functional
Operator documentation availability
Orbital potentiometer out of adjustment
Orbital, angulation, swivel, or lift brakes below spec
Performance problems with service software and 30 f/s fluoroscopy
Protective conductor resistance exceeds limit
Radiation protection devices present
Remote system does not support DICOM features or roles required for transfer
Removable I.I. laser light localizer mechanics damaged
Restart Application via Local Service fails with Timeout error
Safety cutoff devices functioning
Safety distances maintained
Shutdown fails with CD-ROM in CD/DVD drive
System movements stop at end positions
System start not guaranteed with Grace Period below 800
System start-up failures with low Grace Period setting
Table and system position reproducibility
Unusual noise during operation
USB-to-CAN driver problems
Visual damage affecting safety
Wall, ceiling, and floor mountings secure
Warning devices functioning
Warning labels missing or illegible
Warning labels present and recognizable
Wheels or castors defective

46 more symptoms with ranked causes and checks are in ServiceForge. Connect ServiceForge to your AI

Error codes

Code	Meaning	Trigger	Severity
`0001`	Error following main system software download	After completion of main system software download to base unit	warning
`30023`	Service unacceptable	Remote DICOM system rejected the requested service or presentation context	error
`40003`	Session aborted by sender	DICOM Association negotiation fails or is rejected	error
`A7xx`	Out of resources	Command set response contains error status	error
`Connection failed because the remote node does not exist`	Remote system cannot be contacted	TCP/IP ping fails to reach remote node	error
`Could not open association with remote node`	DICOM association with remote system failed	Network or remote system problem prevents connection establishment	error
`E: TCP init error`	TCP/IP initialization failed	Network connectivity or configuration problem	error
`[MC_ALREADY_REGISTERED]`	Application was already registered		unknown
`[MC_ASSOCIATION_ABORTED]`	Association was aborted		unknown
`[MC_ASSOCIATION_CLOSED]`	Association was closed by peer		unknown
`[MC_ASSOCIATION_REJECTED]`	Association negotiation failed		unknown
`[MC_ATTRIBUTE_HAS_VALUES]`	Attribute has value(s) - VR cannot be changed to SQ		unknown
`[MC_BAD_DIR_RECORD_TYPE]`	Invalid directory record type		unknown
`[MC_BUFFER_TOO_SMALL]`	Value too large for buffer		unknown
`[MC_CALLBACK_CANNOT_COMPLY]`	Callback cannot comply		unknown
`[MC_CALLBACK_DATA_SIZE_NEGATIVE]`	Callback provided negative data size		unknown
`[MC_CALLBACK_DATA_SIZE_UNEVEN]`	Callback provided uneven data size		unknown
`[MC_CALLBACK_PARM_ERROR]`	Invalid parameter from callback		unknown
`[MC_CALLBACK_REGISTERED]`	Not allowed if callback is registered		unknown
`[MC_CANNOT_COMPLY]`	Callback cannot comply with request		unknown
`[MC_CANT_ACCESS_PROFILE]`	Cannot access MergeCOM services file		unknown
`[MC_CONFIG_INFO_ERROR]`	Invalid configuration parameter		unknown
`[MC_CONFIG_INFO_MISSING]`	Required configuration info missing		unknown
`[MC_CONNECTION_FAILED]`	Failed to connect to remote host		unknown
`[MC_DDFILE_ERROR]`	Problem with data dictionary file		unknown
`[MC_DOES_NOT_VALIDATE]`	Message contains validation errors		unknown
`[MC_EMPTY_VALUE]`	Attribute has no value yet		unknown
`[MC_END_OF_DATA]`	End of data		unknown
`[MC_END_OF_LIST]`	End of list has been reached		unknown
`[MC_ENTITY_ALREADY_EXISTS]`	Lower level directory entity already exists		unknown
`[MC_EXT_INFO_UNAVAILABLE]`	Extended negotiation information unavailable		unknown
`[MC_FOUND]`	Private block found		unknown
`[MC_FUNCTION_UNAVAILABLE]`	Function not available on this machine		unknown
`[MC_INACTIVITY_TIMEOUT]`	Timed out waiting on network partner in middle of a transfer		unknown
`[MC_INCOMPATIBLE_VALUE]`	Tag's value incompatible with function call		unknown
`[MC_INCOMPATIBLE_VR]`	Tag's VR incompatible with function call		unknown
`[MC_INVALID_APPLICATION_ID]`	Application ID parameter is invalid		unknown
`[MC_INVALID_APPLICATION_TITLE]`	Application Title parameter is invalid		unknown
`[MC_INVALID_ASSOC_ID]`	Association ID parameter is invalid		unknown
`[MC_INVALID_CHARS_IN_VALUE]`	Invalid characters in value for this VR		unknown
`[MC_INVALID_COMMAND]`	Invalid command parameter		unknown
`[MC_INVALID_DATA_TYPE]`	Invalid data type parameter		unknown
`[MC_INVALID_DICOMDIR_ID]`	DICOMDIR ID parameter invalid		unknown
`[MC_INVALID_DIRECTORY_RECORD_OFFSET]`	Directory record offset doesn't match a directory record		unknown
`[MC_INVALID_ENTITY_ID]`	Entity ID parameter invalid		unknown
`[MC_INVALID_FILE]`	Invalid DICOM file: did not contain DICM in prefix		unknown
`[MC_INVALID_FILE_ID]`	File ID parameter invalid		unknown
`[MC_INVALID_GROUP]`	Private group not an odd number		unknown
`[MC_INVALID_HOST_NAME]`	Host name parameter invalid		unknown
`[MC_INVALID_ITEM_ID]`	Item ID parameter invalid		unknown
`[MC_INVALID_LENGTH_FOR_TITLE]`	Application title not 1-16 bytes long		unknown
`[MC_INVALID_LENGTH_FOR_VR]`	Invalid VR length in stream data		unknown
`[MC_INVALID_LICENSE]`	Invalid license number specified in ASSOC_PARMS		unknown
`[MC_INVALID_LOWER_DIR_RECORD]`	Invalid lower-level directory record type		unknown
`[MC_INVALID_MESSAGE_ID]`	Message ID parameter invalid		unknown
`[MC_INVALID_MESSAGE_RECEIVED]`	Network partner sent an invalid message		unknown
`[MC_INVALID_MRDR_ID]`	MRDR ID parameter invalid		unknown
`[MC_INVALID_PAD]`	Invalid number for padding, must be even		unknown
`[MC_INVALID_PARAMETER_NAME]`	Invalid name parameter value		unknown
`[MC_INVALID_PORT_NUMBER]`	Port number parameter not positive		unknown
`[MC_INVALID_PRIVATE_CODE]`	Invalid private group code		unknown
`[MC_INVALID_SERVICE_LIST_NAME]`	Invalid service list name parameter		unknown
`[MC_INVALID_SOP_CLASS_UID]`	SOP class UID parameter is invalid		unknown
`[MC_INVALID_TAG]`	Tag parameter invalid		unknown
`[MC_INVALID_TRANSFER_SYNTAX]`	Invalid transfer syntax code		unknown
`[MC_INVALID_VALUE_FOR_VR]`	Invalid value for this tag's VR		unknown
`[MC_INVALID_VALUE_NUMBER]`	Invalid value number for the attribute		unknown
`[MC_INVALID_VERSION]`	Invalid version of utilities used to generate configuration functions		unknown
`[MC_INVALID_VR_CODE]`	VR parameter is invalid		unknown
`[MC_LIBRARY_ALREADY_INITIALIZED]`	MC_Library_Initialization has already been called		unknown
`[MC_LIBRARY_NOT_INITIALIZED]`	MC_Library_Initialization not called yet		unknown
`[MC_LOG_EMPTY]`	No messages have been logged		unknown
`[MC_MESSAGE_EMPTY]`	The message object is empty		unknown
`[MC_MESSAGE_VALIDATES]`	Message validates		unknown
`[MC_MISSING_CONFIG_PARM]`	Required parameter missing in merge.ini		unknown
`[MC_MSGFILE_ERROR]`	Problem with message information file		unknown
`[MC_MUST_BE_POSITIVE]`	Value is not positive		unknown
`[MC_NETWORK_SHUT_DOWN]`	Network unexpectedly shutdown		unknown
`[MC_NO_APPLICATIONS_REGISTERED]`	No applications registered		unknown
`[MC_NO_CALLBACK]`	Attribute has no callback registered		unknown
`[MC_NO_CONDITION_FUNCTION]`	Warning: no function specified for Type 1C or Type 2C attribute		warning
`[MC_NO_FILE_SYSTEM]`	No file system available to perform requested function		unknown
`[MC_NO_INFO_REGISTERED]`	No negotiation information registered for the service		unknown
`[MC_NO_LICENSE]`	License not found in ASSOC_PARMS		unknown
`[MC_NO_MERGE_INI]`	MERGE.INI file cannot be located		unknown
`[MC_NO_MORE_ATTRIBUTES]`	Message has no more attributes		unknown
`[MC_NO_MORE_VALUES]`	Attribute has no more values		unknown
`[MC_NON_SERVICE_ATTRIBUTE]`	Invalid attribute for service		unknown
`[MC_NO_PROFILE]`	Could not access MergeCOM Profile		unknown
`[MC_NO_REQUEST_PENDING]`	No association request to accept/reject		unknown
`[MC_NOT_FOUND]`	Private block not found		unknown
`[MC_NOT_ONE_OF_DEFINED_TERMS]`	Value not one of defined terms		unknown
`[MC_NOT_ONE_OF_ENUMERATED_VALUES]`	Value not an enumerated value		unknown
`[MC_NULL_POINTER_PARM]`	Null parameter		unknown
`[MC_NULL_VALUE]`	Attribute's value is NULL		unknown
`[MC_OUT_OF_ORDER_TAG]`	A tag was encoded in the stream not in ascending order		unknown
`[MC_PROTOCOL_ERROR]`	Protocol violation: Call made out of sequence		unknown
`[MC_REQUIRED_ATTRIBUTE_MISSING]`	Required attribute not in message		unknown
`[MC_REQUIRED_DATASET_MISSING]`	Missing required data set for this message command		unknown
`[MC_REQUIRED_VALUE_MISSING]`	Required attribute has no value		unknown
`[MC_STATE_VIOLATION]`	Function call invalid now		unknown
`[MC_SYSTEM_CALL_INTERRUPTED]`	System call was interrupted		unknown
`[MC_SYSTEM_ERROR]`	System error		unknown
`[MC_TAG_ALREADY_EXISTS]`	Tag already exists		unknown
`[MC_TEMP_FILE_ERROR]`	Temporary file I/O error		unknown
`[MC_TIMEOUT]`	Timed out waiting on network partner		unknown
`[MC_TOO_FEW_VALUES]`	Attribute must have more values		unknown
`[MC_TOO_MANY_BLOCKS]`	No room for more private blocks		unknown
`[MC_TOO_MANY_VALUES]`	Too many values for this attribute		unknown
`[MC_UNABLE_TO_CHECK_CONDITION]`	Unable to check condition		unknown
`[MC_UNABLE_TO_GET_ITEM_ID]`	Function unable to get item ID from DICOMDIR object		unknown
`[MC_UNACCEPTABLE_SERVICE]`	Message service unacceptable for this association		unknown
`[MC_UNEXPECTED_EOD]`	Unexpected end of stream data		unknown
`[MC_UNKNOWN_HOST_CONNECTED]`	Unknown host attempted to connect		unknown
`[MC_UNKNOWN_HOST_NAME]`	Unable to resolve host name to ip address		unknown
`[MC_UNKNOWN_ITEM]`	Item is not configured		unknown
`[MC_UNKNOWN_SERVICE]`	Service is not configured		unknown
`[MC_VALUE_MAY_NOT_BE_NULL]`	Type 1[C] value may not be NULL		unknown
`[MC_VALUE_NOT_ALLOWED]`	Attribute must not be used under current condition		unknown
`[MC_VALUE_OUT_OF_RANGE]`	Out of range: Numeric precision would be lost		unknown
`[MC_VALUE_TOO_LARGE]`	Stream value length too large		unknown
`[MC_VR_ALREADY_VALID]`	Value representation is already valid		unknown
`Read PDU timeout`	Timeout occurred while waiting for response PDU after sending command set request	Remote system is not responding within the configured read PDU timeout interval	warning
`Service is unacceptable (30023)`	Remote system rejected the DICOM service parameters offered by sending system	Incompatible service configuration, unsupported roles, or presentation context mismatch	error
`Session aborted by sender (40003)`	DICOM association was aborted by the sending system during negotiation	Remote system rejects association parameters or presentation context during T3 negotiation phase	error
`Status A7xx`	Remote DICOM system returned out-of-resources status code in command set response	Transfer was attempted but remote system cannot accept image due to resource constraints or attribute errors	error
`Timeout`	Restart operation did not complete within expected time	Attempted restart via Local Service > Utilities > System > Restart Application	error
`Timeout in the middle of the message stream`	Transfer was interrupted due to inactivity timeout while sending DICOM image data	No data transmitted for longer than inactivity timeout interval during transfer of large image or slow network	warning

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.