Catheterization lab systems · Cardiolab family

GE Healthcare CardioLab: troubleshooting and error codes

The ServiceForge knowledge base holds 102 documented symptoms for the GE Healthcare CardioLab, with 221 ranked causes, 163 diagnostic checks with test points and expected values, and 26 error codes. Each symptom below shows its causes and the first check; the rest is one connection away. Connect ServiceForge to your AI

Symptoms

Excessive noise on intracardiac signal traces patient safety

Traces appear fuzzy, thick, or dull; noise appears on one or all intracardiac channels during or after cardiac procedures

Ranked causes

1. Power line frequency noise (60Hz or 50Hz) (common)
2. Bad electrical grounds (power outlets, cords, equipment) (common)
3. Bad ablation device cabling or personality module (occasional)
4. Poor routing of wires around other equipment (occasional)
5. Poor electrode connection or Right Leg lead issue (common)
6. High gain amplification (occasional)
7. Bad or worn patient cables or lead wires (common)
8. Bad grounding pad (occasional)

First check

Measure period of sine wave on trace to confirm 60Hz or 50Hz power line frequency

Test point: Intracardiac trace
Expected: 16.7ms for 60Hz or 20ms for 50Hz, ±0.5ms
Tools: Oscilloscope or display speed measurement

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

Ablation noise on ECG

Large spikes and noise on waveform occur while RF generator actively ablates heart; disappears when generator turned off

Ranked causes

1. Bad lead wires (common)
2. Bad patient cables (common)
3. Poor electrode connections with patient (common)
4. Bad ablation grounding pad (occasional)
5. Proximity of electrodes/lead wires to RF source (occasional)
6. Improper grounding of equipment (occasional)

First check

Inspect lead wires for damage or wear

Test point: All ECG lead wires
Expected: No visible damage, corrosion, or wear

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

Ablation noise on intracardiac signal high voltage

Noise occurs while RF generator actively ablates; disappears when generator is turned off. Higher power settings produce higher amplitude noise. Most difficult to eliminate on Ablation Distal signal; noise expected above 35W.

Ranked causes

1. High power setting on RF generator (above 35W) (common)
2. Poor electrode connections with patient (common)
3. Bad ablation grounding pad (occasional)
4. Proximity of electrodes or lead wires to RF source (occasional)
5. Equipment grounding issues (occasional)
6. Old EPT personality module without Ablate and Record capability (rare)

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

Supplies added to CVIS do not appear on Mac-Lab

List items added in CVIS system are not visible in Mac-Lab/CardioLab

Ranked causes

1. INW service that processes lists not configured or started (common)
2. CVIS List Sharing Delta export not configured for the location (common)
3. Corrupt XML export from CVIS system (occasional)
4. CVIS List Sharing services not started on CVIS server (common)
5. Replication errors or INW server issues (occasional)
6. Network connection between CVIS and INW server lost (occasional)

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

Cannot connect to remote DICOM host

Mac-Lab/CardioLab system fails to establish DICOM connection to CVIS, EMR, or scheduling system; no patient records returned or error messages displayed

Ranked causes

1. Incorrect hostname or IP address configured (common)
2. Incorrect port number configured (common)
3. Incorrect AE Title configured (common)
4. Transport Layer Security (TLS) mode mismatch (occasional)
5. Remote DICOM host not actively listening (occasional)

First check

Resolve hostname to IP address

Test point: Command Prompt on Mac-Lab/CardioLab
Expected: Valid IP address resolved or configured IP address is reachable
Tools: DICOMDiag tool

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

Cannot establish connection to patient monitor patient safety

Mac-Lab/CardioLab application reports connection lost or cannot be established to patient monitor at pre/post-workstation

Ranked causes

1. Physical connection issue between workstation and patient monitor (common)
2. Patient monitor configuration mismatch (occasional)
3. Patient monitor not powered on or devices not connected (common)
4. CARESCAPE B450 software version outdated (occasional)
5. Review workstation needs reboot (occasional)

First check

Verify physical cable connections

Test point: Connection between workstation and patient monitor
Expected: All cables properly connected and tight

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

Intracardiac signal noise or degraded waveform display patient safety

Lost or degraded display and accuracy of intracardiac waveforms due to electromagnetic disturbances; intracardiac signal noise may occur

Ranked causes

1. Use with high-frequency surgical equipment (common)
2. Portable RF communications equipment used too close (common)
3. Incorrect HDMI video cables installed (occasional)
4. Non-approved accessories, transducers or cables used (occasional)
5. Strong intentional radio transmitters in vicinity (occasional)

First check

Verify distance of portable RF communications equipment from system

Test point: All parts of CardioLab system and its cables
Expected: All RF equipment and antennas at least 30 cm (12 in) away

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

Pacing artifact noise on ECG patient safety

Noise with spikes occurs while pace generator actively paces heart; disappears when pacing pulses turned off

Ranked causes

1. Excessively high pacing current settings (common)
2. Bad stimulator cables (common)
3. Loose fitting or bad stimulator connections (common)
4. Stimulator Isolation/Interface box low batteries (occasional)
5. Charge build-up on pacing poles from extended pacing (occasional)

First check

Verify pacing current settings

Test point: Stimulator milliamp output and duration controls
Expected: Current set to 1-5mA @ 2.0ms or clinically appropriate levels

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

Send Movies option disabled in EP recording preferences

Send Movie Option grayed out when configuring EP recording preferences for CARTO 3 System movies

Ranked causes

1. MapImageImport directory not shared on CardioLab (common)
2. MapImageImport directory permissions not set for CARTO 3 interface user (common)
3. CARTO 3 interface user credentials mismatch (common)
4. CARTO 3 interface user account password changed (occasional)
5. CARTO 3 System moved to unconfigured CardioLab (rare)

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

Unable to capture X-ray image in image capture window

Image grabber window is blank or displays 'Failed to capture an image' error

Ranked causes

1. DVI cable not connected to correct OrionHD board connector (common)
2. Incorrect .dcf configuration file selected (common)
3. OrionHD board driver not installed or not detected (occasional)
4. MLCL or ImgTest application still running (occasional)
5. Non-standard video source format not supported (rare)

First check

Verify DVI cable connection

Test point: DVI connector #3 on OrionHD board
Expected: DVI-to-5BNC cable securely connected; green and blue BNC inputs available

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

Baseline drift noise on ECG

ECG trace moves vertically up and down; noise frequency varies and correlates with physical movement near patient

Ranked causes

1. Bad or worn lead wires (common)
2. Bad or worn patient cables (common)
3. Poor electrode connection with patient (common)
4. Patient table not grounded properly (occasional)

First check

Inspect lead wires for damage or wear

Test point: All ECG lead wires
Expected: No visible damage, corrosion, or wear

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

Baseline drift noise on intracardiac signal

Entire trace moves vertically; low frequency noise similar to ECG baseline drift noise

Ranked causes

1. Bad lead wires or patient cables (common)
2. Poor electrode connection or location (common)
3. Patient movement or drape movement (occasional)
4. Patient table not grounded properly (occasional)

First check

Adjust high pass filter to higher setting

Test point: High pass filter setting
Expected: Higher than normal (normal: 30 Hz for intracardiac signal)

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

CardioLab amplifier does not send signals to system

Amplifier is not responding when a new study is started; system displays 'Prucka 3 Amplifier is not responding' or 'Clab II Amplifier is not responding' message

Ranked causes

1. Amplifier not plugged in or turned off (common)
2. External cables not connected or not secure (common)
3. Fiber optic cable (FOC) defective or dirty (occasional)
4. FOC connector not properly mated or no light output (occasional)

First check

Verify amplifier power status

Test point: Amplifier power switch
Expected: Amplifier plugged in and powered on

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

Cases performed on Mac-Lab do not appear in CVIS

Study data acquired on Mac-Lab/CardioLab system does not transfer to CVIS archive

Ranked causes

1. Interfaces on CVIS server not running or configured incorrectly (common)
2. Data Export Utility on Mac-Lab not configured correctly (common)
3. Enable file export on study close not checked (common)
4. Network connection between Mac-Lab and CVIS server down (common)

First check

Verify file export enabled on study close

Test point: Administration > System Settings > File Paths
Expected: Enable file export on study close option is checked

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

DICOM interface connectivity not established

Mac-Lab/CardioLab system cannot communicate with remote DICOM hosts (X-ray, ultrasound, CVIS/EMR)

Ranked causes

1. Incorrect DICOM AE Title configuration (common)
2. Incorrect Listen Port or remote host port configuration (common)
3. Remote host DICOM configuration incomplete or incorrect (common)
4. Security mode mismatch between systems (occasional)

First check

Verify local system AE Title is configured

Test point: Administration > System Settings > Connectivity > Local System > DICOM Settings
Expected: AE Title filled with alphanumeric/underscore, ≤16 chars, case-sensitive

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

Mapping system noise on intracardiac signal

Noise typically associated with power line frequency noise or magnet-generated noise. Can be measured by display speed to determine if 60Hz or 50Hz.

Ranked causes

1. Power line frequency noise or magnet interference (common)
2. Poor electrode connections with patient (common)
3. Equipment grounding issues (occasional)
4. 5.6 KHz End Guide Signal interference (rare)

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

Mapping system noise on intracardiac signals patient safety

Noise visible on intracardiac mapping signals; typically power line frequency or magnet-generated noise

Ranked causes

1. Power line frequency interference (60 Hz or 50 Hz) (common)
2. Poor electrode connections or improper electrode placement (common)
3. Magnet interference or 5.6 KHz End Guide Signal interference (occasional)
4. Inadequate grounding of equipment and patient (occasional)

First check

Measure noise frequency with CardioLab calipers

Test point: Intracardiac ECG display
Expected: 16 ms time base peak-to-peak for 60 Hz power line; magnet noise differs

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

Muscle artifact noise on ECG

Variable noise riding on ECG trace(s) caused by patient movement such as shivering or snoring

Ranked causes

1. Bad or worn lead wires (common)
2. Bad or worn patient cables (common)
3. Poor electrode connection with patient (common)
4. Patient movement caused by cold, medications, or snoring (common)

First check

Inspect lead wires for damage or wear

Test point: All ECG lead wires
Expected: No visible damage, corrosion, or wear

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

Pacing artifact noise on intracardiac signal

Noise occurs while pace generator actively paces heart; disappears after pacing pulses are turned off. Amplitude increases with higher pacing current.

Ranked causes

1. Excessively high pacing current settings (common)
2. Bad stimulator cables or loose connections (common)
3. Stimulator isolation box with low batteries (occasional)
4. Charge build-up on pacing poles from prolonged pacing (occasional)

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

Patient search returns no results

CVIS patient search fails to return scheduled or admitted patients from Mac-Lab/CardioLab system

Ranked causes

1. AE Title mismatch between Mac-Lab/CardioLab and CVIS (common)
2. DICOM settings not configured correctly on Mac-Lab (common)
3. DICOM services not running on CVIS server (common)
4. Network connection lost between Mac-Lab and CVIS (common)

First check

Verify AE Title configuration matches between systems

Test point: Administrative > System Management > DICOM Maintenance Location drop-down
Expected: AE Title in Mac-Lab matches configured value in CVIS (e.g., MLCL_Lab1)

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

Power line frequency noise on ECG traces

ECG traces appear fuzzy, thick, or dull due to 60 Hz or 50 Hz power line noise

Ranked causes

1. Power line filter turned off (common)
2. Bad or worn lead wires (common)
3. Bad or worn patient cables (common)
4. Poor electrode connection with patient (common)

First check

Verify power line filter setting

Test point: ECG filter menu option
Expected: Power line filter set to Fixed or Adaptive

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

CARTO 3 System button inactive

CARTO 3 System interface button is not clickable or grayed out in CardioLab application

Ranked causes

1. CARTO 3 System interface not enabled on CardioLab (common)
2. Interface not accessed from Real-Time window (common)
3. Software option disabled (occasional)

First check

Verify CARTO 3 interface is enabled

Test point: CardioLab Administration settings
Expected: CARTO 3 System interface enabled and checkbox is not grayed out

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

CARTO 3 System movies not transferring to CardioLab

Movie files from CARTO 3 System fail to transfer to CardioLab system despite proper configuration attempts

Ranked causes

1. CARTO 3 System configuration incorrect (common)
2. CARTO System interface user account not created (occasional)
3. File sharing disabled on CARTO adapter (common)

First check

Verify file sharing setting for CARTO adapter

Test point: CARTO Connection Properties
Expected: File and Printer Sharing for Microsoft Networks enabled

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

Mapping points unsynchronized or missing patient safety

CARTO 3 System mapping points not synchronized with CardioLab or missing from display

Ranked causes

1. CARTO 3 System point filter filtering out points (occasional)
2. Points manually deselected in report (occasional)
3. Waveform synchronization off by more than 1 second (occasional)

First check

Verify waveform synchronization timing

Test point: CARTO 3 System waveform and CardioLab recording timestamps
Expected: Synchronization within 1 second or less

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

Mapping system noise on surface ECG traces patient safety

ECG traces appear fuzzy, thick, or dull; power line frequency or magnet noise visible on one or all traces

Ranked causes

1. Power line frequency interference (60 Hz or 50 Hz) (common)
2. Improper grounding of equipment and patient table (common)
3. Inadequate right leg lead connection (common)

First check

Measure power line frequency period with time calipers

Test point: ECG display at high speed
Expected: 16.7ms peak-to-peak for 60Hz or 20ms for 50Hz

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

Over-filtered blocky ECG signals

ECG signal appears over-filtered with squared-off waveform appearance

Ranked causes

1. ECG filter setting too high (e.g., 5 Hz high-pass) (common)
2. Low sampling rate (occasional)
3. Non-optimal screen resolution or contrast/brightness (occasional)

First check

Verify ECG high-pass filter setting

Test point: ECG filter menu option
Expected: Filter set to 0.05Hz or 0.5Hz

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

Patient search returns no results or error message

When attempting Patient Search in Navigator with Centricity Cardiology DMS or Workflow, no patient records are returned or error message displayed indicating configuration or connectivity issue

Ranked causes

1. DICOM configuration settings incorrect on Mac-Lab/CardioLab (common)
2. CVIS system configuration settings incorrect (common)
3. CVIS system not actively listening for connections (occasional)

First check

Run DICOMDiag tool to validate client connectivity

Test point: All configured remote DICOM hosts
Expected: No failures reported; all connection steps successful
Tools: DICOMDiag command-line tool

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

Random spikes or square waveforms in signals when not stimulating

Unwanted spikes or square wave patterns appear in signal traces during non-stimulation periods

Ranked causes

1. Dirty or defective fiber optic cable (common)
2. Defective catheter, catheter extender, or catheter junction box (occasional)
3. Defective catheter input module (occasional)

First check

Clean fiber optic cable contacts

Test point: FOC connectors at amplifier and computer
Expected: Contacts clean and free of debris

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

Unable to connect to remote server via Web service

System cannot establish connection to remote server through Mac-Lab/CardioLab Web service

Ranked causes

1. World Wide Web Publishing Service is not running (common)
2. Internet Information Services (IIS) is not started (common)
3. Default Web service is not running (common)

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

Unipolar high frequency noise on intracardiac signal

Difference in noise level between catheter pole and channel reference (surface WCT or Auxiliary Reference). Unipolar signals more susceptible due to common mode rejection issues.

Ranked causes

1. Bad lead wires or patient cables (common)
2. Poor electrode connection with patient (common)
3. Intracardiac cable proximity to other devices (WCT as reference) (occasional)

First check

Adjust low pass filter to lower setting

Test point: Low pass filter frequency
Expected: 150 Hz (changed from 1000 Hz)
Tools: System software filter control

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

X-ray image Live and Freeze buttons are grayed out

Live and Freeze buttons on Image 1 or Image 2 toolbar are unavailable and cannot be activated

Ranked causes

1. Cardio Image option not enabled; only Image Capture option installed (common)
2. OrionHD image capture board not present or not detected (occasional)
3. OrionHD board driver not properly installed or functioning (occasional)

First check

Verify Cardio Image software option is installed and enabled

Test point: System software options configuration
Expected: Cardio Image option enabled (not Image Capture option only)

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

Amplifier communication or register readback failure

CardioLab II Plus Amplifier shows failures during Register Readback or Walking Ones test, indicating data communication errors between amplifier boards and computer.

Ranked causes

1. Defective amplifier board or PCIe connection (occasional)
2. Firmware version mismatch or corruption (rare)

First check

Read amplifier registers and verify no communication errors

Test point: Amplifier Test > Register Readback tab
Expected: No register read errors; all values stable
Tools: Amplifier Test software

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

Calibration: MLLPService debug logging patient safety

Enable and disable detailed debug logging for troubleshooting MLLPService communication failures

Ranked causes

1. Need to diagnose MLLPService transfer failures in detail (occasional)
2. Patient health information exposure risk from logs (common)

First check

Enable TRACE logging in MLLPService.config

Test point: [Drive]\GEData\config\MLLPService.config first line
Expected: log4cplus.logger.MLCL.Server.MLLPService=TRACE, STDOUT, MLLP

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

CARTO 3 System connection failure

No communication between CardioLab and CARTO 3 System

Ranked causes

1. Defective or disconnected crossover cable (common)
2. Ethernet lights not active (common)

First check

Inspect crossover cable connection

Test point: Ethernet ports on acquisition system and CARTO 3 System
Expected: Crossover cable firmly connected with 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

Computer name resolution fails on GE HealthCare system

Computer name resolution fails even when DNS is properly configured and flushed

Ranked causes

1. NetBIOS disabled by default on GE HealthCare acquisition or review system (common)
2. LLMNR disabled on GE HealthCare system (occasional)

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

DNS name resolution fails

System cannot resolve computer names via DNS

Ranked causes

1. DNS cache is obsolete or corrupted (common)
2. DNS problem on server side (occasional)

First check

Flush local DNS cache

Test point: Local DNS resolver
Expected: DNS cache cleared successfully

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

EtCO2 check airway adapter patient safety

Airway adapter removed, optically blocked, or adapter type changed without zeroing

Ranked causes

1. Airway adapter removed or contaminated with secretions (common)
2. Adapter type changed without re-zeroing sensor (occasional)

First check

Inspect airway adapter for blockage or contamination

Test point: Adapter optical windows
Expected: Clean windows, no mucus or moisture

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

EtCO2 sensor faulty patient safety

Sensor reports capnostat source current failure, EEPROM checksum error, or hardware malfunction detected

Ranked causes

1. Sensor improperly seated or disconnected (common)
2. Sensor hardware failure (rare)

First check

Verify sensor is properly connected

Test point: Sensor connector
Expected: Sensor seated firmly in connector

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

EtCO2 sensor over temperature patient safety

End Tidal CO2 sensor temperature exceeds operating limit, sensor may not function correctly

Ranked causes

1. Sensor exposed to extreme heat source (common)
2. Sensor hardware malfunction (rare)

First check

Check for nearby heat sources

Test point: Sensor environment
Expected: No heat lamps or extreme heat sources within sensor area

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

EtCO2 zero required patient safety

Sensor requires zeroing due to required zero condition or zero error detected during operation

Ranked causes

1. Airway adapter contaminated or requires zeroing after adapter change (common)
2. Hardware error developing (rare)

First check

Inspect airway adapter for contamination

Test point: Adapter windows
Expected: Clean, unobstructed optical windows

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

INNOVA CENTRAL/Touch screen connection status shows Listening

IGS system shows Listening on port message instead of Connected status

Ranked causes

1. INNOVA CENTRAL/Touch screen physically disconnected (common)
2. Port setting is not 889 (common)

First check

Verify port number in INNOVA CENTRAL configuration

Test point: Administration > System Settings > Connectivity > INNOVA CENTRAL/Touch Screen section
Expected: Port = 889

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

Invalid number of groups message when creating or continuing study

Message 'Invalid number of groups' appears when creating or continuing a CardioLab study in the application

Ranked causes

1. CardioLab II Plus Amplifier PCI board not properly installed in slot 6 (common)
2. Study configuration has no amplifier groups configured (common)

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

Lost connection to Study Host during active study patient safety

Error message 'Lost connection to Study Host. No further data can be saved in this Study' displays during active study on acquisition systems and review workstations

Ranked causes

1. Network connection to study host broken (common)
2. NetMsgSender service failed on study host (occasional)

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

MLLPService not functioning properly

MLLP export to external CVIS/EMR systems is not working or data is not being sent

Ranked causes

1. EMR or receiving system is down (common)
2. Network outage preventing data export (occasional)

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

Network Messaging not active when not in a study

Error message 'Network Messaging is not active. Study catalog changes may not be visible' displays at Navigator on acquisition systems and review workstations when not in a study

Ranked causes

1. NetMsgSender background service not running or improperly configured (common)
2. Network connectivity loss to INW server (occasional)

First check

Verify systems can ping each other across network

Test point: All systems on network
Expected: Ping responses successful

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

Patient Search or Schedule Search operation fails

Unable to retrieve patient information or scheduled procedures from CVIS/EMR system

Ranked causes

1. Modality Worklist Host not configured (common)
2. Incorrect patient demographics field locking configuration (occasional)

First check

Verify Modality Worklist Host configuration is complete

Test point: System Settings > Connectivity > Modality Worklist Host section
Expected: AE Title, Hostname/IP, Port number all filled; Cath Modality=HD by default

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

Paucal communication packet loss on amplifier board

Amplifier Test Status section shows COMM_QI values below 1.0, indicating packet loss between amplifier boards, affecting signal integrity.

Ranked causes

1. Loose or defective PCIe connection between amplifier boards (occasional)
2. Defective amplifier board or trace damage (rare)

First check

Verify COMM_QI values for first ten communication cycles

Test point: Amplifier Test > Registers > Status section
Expected: All COMM_QI values equal 1
Tools: Amplifier Test software

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

System cannot establish SSL/TLS secure channel trust relationship

Web service fails to establish secure channel, typically during client connection or data transfer

Ranked causes

1. Mac-Lab/CardioLab certificate is expired (common)
2. Mac-Lab/CardioLab certificate permission issue (occasional)

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

Unable to communicate with cath amplifier

System cannot establish or maintain communication with PDM (Portable Device Module)

Ranked causes

1. System IP address in 192.168.0.xxx range (common)
2. PDM not registered on system (occasional)

First check

Verify system IP address

Test point: Network Properties IP address
Expected: Not in 192.168.0.xxx range

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

Vital signs not displayed in Patient Status Area patient safety

Expected vital parameters do not appear in the Patient Status Area during study

Ranked causes

1. Patient monitor connection issue (common)
2. Respiration rate or temperature display disabled (common)

First check

Verify patient monitor connection cabling

Test point: Connection between patient monitor and workstation
Expected: Proper cabling for monitor family

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

Windows scaling level warning message displayed

System displays a warning message indicating the need to change Windows scaling level

Ranked causes

1. Windows scaling level not set to 125% (common)
2. User session needs refresh after scaling change (common)

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

Acquisition system not powered on

White LED not illuminated on acquisition system front panel

Ranked causes

1. Acquisition system power switch off (common)

First check

Verify acquisition system power status

Test point: Front panel white LED
Expected: LED illuminated

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

Barcode scanner triggers NIBP/NBP measurement

Scanning barcodes during a study causes unwanted NIBP or NBP measurements

Ranked causes

1. Barcode scanner not configured properly (common)

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

Battery charge level indicator shows critical low patient safety

PDM battery LED test button shows one LED flashing, indicating less than 10% capacity remaining.

Ranked causes

1. Battery charge depleted below 10% (common)

First check

Test battery charge status

Test point: TEST button on PDM battery
Expected: 1 LED flashing indicates less than 10% capacity

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

CARTO 3 System IP address conflict

IP addressing issue between CardioLab and CARTO 3 System prevents communication

Ranked causes

1. IP address mismatch or conflict on network (common)

First check

Use ping to test communication between systems

Test point: Network connectivity from CardioLab to CARTO 3 System
Expected: Ping successful from 192.168.5.2 to 192.168.5.1

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

Cath amplifier battery error reported caution

PDM displays battery error message indicating battery problem

Ranked causes

1. Battery overheating or not inserted properly (occasional)

First check

Verify PDM battery insertion and condition

Test point: PDM battery compartment
Expected: Battery properly installed and not overheated

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

Cath amplifier battery is low caution

PDM battery charge level is low and requires charging or replacement

Ranked causes

1. PDM battery insufficient charge (common)

First check

Connect PDM to charging station

Test point: PDM Base Station Plus or PDM Slim Connect
Expected: PDM properly seated in charger

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

Cath amplifier hardware error reported

PDM displays hardware error message and system cannot operate

Ranked causes

1. PDM hardware failure or malfunction (rare)

First check

Check Windows event log for PDM error code

Test point: Windows event log
Expected: PDM error code visible

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

Default Web Site binding configuration issue

Web site binding not properly configured for SSL/TLS communication

Ranked causes

1. SSL certificate not properly selected in binding (common)

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

DirectSight website cannot be reached

DirectSight website is inaccessible to clients

Ranked causes

1. DirectSight website is not running (common)

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

More symptoms

Enclosure leakage current exceeds limit
EP recording disabled on CARTO 3 System
Equipment failure or improper operation from adjacent equipment
EtCO2 device connection attempting
EtCO2 no breaths detected
EtCO2 out of range high
EtCO2 pump life exceeded
EtCO2 pump off
EtCO2 sample line disconnected
EtCO2 sampling line check required
EtCO2 sensor warm-up in progress
Getting Windows ready message appears during startup
HL7 export to CVIS fails
INW server does not pull studies
Isolation transformer not powered on
Matrox Orion HD card firmware update required
MLLPService not running or disabled
Monitor not powered on
Network failures on standalone acquisition system
No data displayed on DirectSight or DirectSnap
Patient lead leakage current exceeds limit - CardioLab amplifier
Patient lead leakage current exceeds limit - PDM
Patient leakage current exceeds limit
Patient leakage current exceeds limit on CardioLab amplifier
Patient monitor connection lost intermittently
Patient monitor not powered on
Patient sink leakage current exceeds limit - CardioLab amplifier
PDM battery does not hold charge
PDM battery requires replacement
PDM does not support invasive pressures
Peripheral devices not powered on
Ping test for network connectivity
Poor color output on acquisition system
Pressure calibration offset detected
Repeated and sporadic network disconnections
Review workstation not powered on
Slow network transfer and ping speed
Studies not transferring to customer system
System does not receive ablation device data
System locks up after first barcode scan
UPS not powered on
Wireless scanner battery unable to hold adequate charge

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

Error codes

Code	Meaning	Trigger	Severity
`Attempting to connect to CO2 Device`	System trying to establish communication link with CO2 device	Power-up, device reconnection, or communication loss recovery	info
`Capnostat in Sleep Mode`	Sensor has been placed into sleep/standby mode unintentionally	Accidental sensor mode change or software command	warning
`Cath Amplifier battery error`	PDM battery problem detected	PDM reports battery error condition	warning
`Cath Amplifier battery is low`	PDM battery charge level insufficient	PDM detects low battery charge during operation or at startup	warning
`Cath Amplifier hardware error`	PDM hardware failure detected	PDM reports hardware error condition	error
`Check Airway Adapter`	Airway adapter removed, optically blocked, or adapter type changed without re-zeroing	Adapter disconnection, occlusion with secretions, or adapter type change without calibration	warning
`Check Sampling Line`	Sampling line pneumatic pressure outside expected operating range	Kinked, occluded, or disconnected sampling line	warning
`CO2 No Breaths Detected`	No respiratory cycles detected for extended timeout period	Timeout condition when breathing ceases or sampling line disconnected	warning
`CO2 Out of Range`	Measured CO2 value exceeds upper limit of 150 mmHg (20.0 kPa, 19.7%)	Patient CO2 level exceeds maximum measurement range	warning
`COM+ Network Access (DCOM-In)`	COM+ component object model network access error preventing remote connection	Review system attempts to connect to remote event logs during diagnostic process	warning
`EventDicomPatientSearchFailedFault`	DICOM patient database search operation failed	DICOM query timeout or database unavailable	warning
`EventDicomScheduleSearchFailedFault`	DICOM schedule database search operation failed	DICOM schedule query timeout or database unavailable	warning
`EventNetMsgSenderNetworkFault`	Failure to connect NetMsgSender	NetMsgSender connection failure	warning
`EventNetMsgSenderNetworkFault`	NetMsgSender communication failure detected	Network connectivity loss or NetMsgSender service crash	error
`EventPdmNotRegisteredOrConnectedFault`	PDM (Patient Data Module) not registered with system or communication disconnected	PDM power-off, network disconnection, or registration loss	error
`EventStudyPullerError64Fault`	StudyPuller service encountered error 64 during operation	Study pull/synchronization operation failure	error
`Initializing CO2 Device`	CO2 device initialization in progress	Device startup or reconnection after power cycle	info
`Pump life has been exceeded`	Pump has reached manufacturer end-of-life after extended operation	Cumulative pump operation hours exceeded rated lifespan	critical
`Pump Off`	CO2 sampling pump is not operating	Pump button toggled off or pump failure	warning
`Sample Line Disconnected`	No sidestream sampling set connected to LoFlo Capnostat	Sampling adapter not attached or became disconnected during operation	error
`Sensor Faulty`	Sensor hardware failure detected: source current failure, EEPROM checksum error, or internal hardware error	Capnostat source current fails, EE-PROM checksum mismatch, or hardware error condition	error
`Sensor Over Temp`	Sensor temperature exceeds 40°C operating limit	Sensor exposed to extreme heat or internal temperature sensor malfunction	warning
`Sensor Warm Up`	Sensor temperature or source current stabilizing during startup	Power-up of sensor or device after power-down	info
`The Cath Amplifier on this system does not support Invasive`	PDM lacks invasive blood pressure measurement capability	System opens Mac-Lab study and PDM does not have IBP option installed	error
`Zero In Progress`	Capnostat zero calibration procedure currently running	User initiated zero command or automatic zero sequence started	info
`Zero Required`	Sensor requires zeroing to recalibrate measurement range	Required zero condition or zero error detected during operation	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.