On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting situations where the Infinity Delta monitor does not recognize the MMS (Multi-Measurement Server) or parameter module, or displays communication errors. Symptoms may include missing parameters, “module not detected,” intermittent dropouts, or communication alarms. The focus is on external connections, module seating, and configuration before assuming internal failure.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Confirm the patient is safely transferred to another monitor before troubleshooting
- Do not remove or reseat modules while actively monitoring a patient
Verify the Complaint
- Power on the monitor and confirm the exact error message
- Check which parameters are missing (SpO2, NIBP, ECG, etc.)
- This helps determine if the issue is module-wide or parameter-specific
Check Module Seating and Physical Connection
- Remove and firmly reseat the MMS/parameter module
- Ensure it clicks fully into place with no looseness
- Poor seating is one of the most common causes of communication errors
Inspect Connector Pins and Ports
- Visually inspect the module connector and monitor port for:
- Bent or recessed pins
- Debris or contamination
- Damage to the housing
- Even minor pin damage can interrupt communication
Swap with a Known Good Module
- Replace the MMS/parameter module with a known working unit
- If the new module works → original module is likely faulty
- If the issue persists → suspect monitor-side connection or internal issue
Check Parameter Cables and Accessories
- Disconnect all patient cables (SpO2, ECG, NIBP, etc.) and reconnect one at a time
- A faulty accessory cable can sometimes cause module communication faults
Power Cycle the Monitor
- Turn off the monitor, remove AC power, and wait 30 seconds
- Restart the unit and recheck module recognition
- This resets communication between the monitor and module
Verify Software/Configuration Status
- Confirm the monitor is not in a restricted mode or configuration that disables modules
- Check for any error logs if accessible
Check for Intermittent Behavior
- Gently wiggle the module while connected (without forcing)
- If the connection drops in/out → likely worn connector or internal port issue
If the Problem Persists
If the module is properly seated, connections are clean, and a known good module does not resolve the issue, the problem is likely internal (e.g., communication board, connector interface, or system electronics).
- Remove the device from service
- Label it Out of Service
- Send for repair or bench evaluation
Knowing when to stop prevents unnecessary risk and is part of proper troubleshooting.
Clinical Use Tip
Never troubleshoot module communication issues on an active patient. Always transfer the patient to another monitor before removing or reseating modules to avoid loss of vital sign monitoring.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“Monitor displaying ‘MMS not recognized’ and no vital parameters showing.”
Cause
What was observed during troubleshooting.
Example:
“Fault traced to intermittent communication due to worn MMS connector; issue persisted with multiple modules.”
Resolution
What action was taken.
Example:
“Removed monitor from service and sent for repair. Verified normal operation with known good unit prior to removal.”
Helpful Details to Include
- Module swapped with known good unit
- Connector condition (clean/damaged)
- Parameters missing or affected
- Intermittent vs constant failure
- Power cycle performed
- Final device status (removed from service or returned to use)
Final Thought
Effective troubleshooting starts with simple external checks like seating, connections, and accessories before assuming internal failure. Patient safety is always the priority—never risk monitoring continuity. Recognizing when an issue is beyond external correction and documenting it clearly ensures efficient repair and reliable equipment performance.
That is successful troubleshooting.