On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Loss of amplifier detection, communication errors, or inability of the system to acquire EEG signals due to connection or hardware issues.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- If the system is actively being used for patient monitoring or diagnostics, stop the study and transition to another working EEG system.
- Expected: Patient monitoring continues safely on alternate equipment
- Why it matters: Loss of signal or unreliable data compromises diagnostic accuracy
Verify the Reported Error and Behavior
- Confirm the exact error message on the acquisition software.
- Observe:
- “Amplifier not detected” message
- No EEG waveforms displayed
- Software unable to start acquisition
- Expected: Error is consistent and reproducible
- Why it matters: Confirms a true communication issue vs intermittent glitch
Check Amplifier Power Status (Most Common Cause)
- Inspect the amplifier unit for power.
- Action:
- Verify power indicator light is on
- Ensure power cable is connected (if external power is used)
- If battery-powered, confirm battery is charged
- Expected: Amplifier powers on normally
- Why it matters: No power = no communication with system
Inspect Data/Interface Cable Connections
- Check all cables connecting the amplifier to the acquisition computer.
- Action:
- Reseat USB, fiber, or proprietary interface cables
- Disconnect and reconnect firmly
- Inspect for bent pins or damaged connectors
- Expected: Secure, undamaged connections
- Why it matters: Loose or damaged cables are the most common communication failure point
Try a Known-Good Cable or Port
- Rule out cable or port failure.
- Action:
- Swap with a known-good interface cable
- Try a different USB or interface port on the computer
- Expected: System detects amplifier after swap
- Why it matters: Identifies faulty cables or ports without assuming internal failure
Restart the System in Proper Sequence
- Perform a controlled reboot.
- Action:
- Power off acquisition software
- Turn off amplifier
- Restart computer
- Power on amplifier first, then launch software
- Expected: Amplifier is detected during software startup
- Why it matters: Correct initialization sequence can restore communication
Check Software Configuration Settings
- Verify the system is configured for the correct amplifier.
- Action:
- Open acquisition settings
- Confirm correct amplifier model is selected
- Ensure no incorrect device profile is loaded
- Expected: Correct amplifier recognized in software
- Why it matters: Misconfiguration can mimic hardware failure
Inspect for Physical Damage or Environmental Issues
- Look for signs of hardware issues.
- Check for:
- Damaged connectors or ports
- Liquid exposure
- Excessive heat or unusual odor
- Expected: No visible damage
- Why it matters: Physical damage often leads to communication failure
If the Problem Persists
If all external connections, power sources, cables, and configuration settings have been verified, the issue is likely internal to the amplifier or communication interface.
Remove the device from service, label it Out of Service, and send for repair or bench evaluation.
Knowing when to stop prevents unnecessary risk and avoids wasted troubleshooting time.
Clinical Use Tip
Do not troubleshoot amplifier connectivity while electrodes are connected to a patient. Disconnect safely and move the patient to another system before testing.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"EEG system reported amplifier not detected and unable to start acquisition."
Cause
What was observed during troubleshooting.
Example:
"Faulty amplifier interface cable preventing communication with acquisition system."
Resolution
What action was taken.
Example:
"Replaced cable and verified amplifier detection and normal EEG signal acquisition."
Helpful Details to Include (If Known)
- Amplifier power indicator status
- Cable condition and swaps performed
- Port tested (USB/interface)
- Software error message text
- Restart sequence performed
- Any visible damage or environmental concerns
- Final device status (returned to service or sent for repair)
Final Thought
EEG communication issues are most often caused by simple external failures such as cables, power, or configuration. A structured approach prevents unnecessary escalation while ensuring patient safety. When external causes are ruled out, timely removal from service and proper documentation are essential for efficient repair and continued clinical reliability.
That is successful troubleshooting.