CONMED AirSeal iFS

System Will Not Power On or Complete Startup

On this page

Asset Type

Surgical Smoke Evacuator

Manufacturer

CONMED

Model

AirSeal iFS

What This Guide Helps With

Troubleshoots no-power, incomplete startup, or startup interruption caused by external power, connections, accessories, controls, or environmental conditions.

Step-by-Step Troubleshooting

1. Protect the Patient and Maintain Procedure Support

If the AirSeal iFS is needed during an active procedure, provide an alternate verified method for insufflation or smoke evacuation as clinically appropriate before troubleshooting. Do not troubleshoot unreliable equipment while the patient depends on it.

Remove the unit from active clinical use if it repeatedly shuts down, shows physical damage, produces unusual odor or heat, or cannot complete startup reliably.

Expected outcome: The patient and procedure are supported independently of the affected unit before troubleshooting begins.

2. Confirm the Exact Startup Failure

Determine whether the system:

Record any displayed message exactly rather than assuming its cause.

Expected outcome: The failure is clearly identified as no power, interrupted startup, or an accessory-related startup problem.

3. Verify AC Power

Inspect the power cord and accessible connector for damage, looseness, contamination, bent contacts, or evidence of overheating. Confirm the cord is fully seated at the system and wall outlet.

Test the outlet using an appropriate approved method or connect the device to a known-good approved receptacle.

Avoid extension cords, questionable power strips, or damaged receptacles.

Expected outcome: The system receives stable AC power from a verified source. If normal startup completes, troubleshooting can stop after functional verification.

4. Inspect the External Power Path

Check the accessible inlet area and power cord for:

Do not bypass protective devices or open the chassis.

Expected outcome: The external power path is intact and free of visible damage.

5. Disconnect Nonessential External Accessories

With the device removed from patient use, disconnect nonessential external accessories or interfaces that can safely be removed before startup. Reattempt startup in the simplest approved configuration.

Reconnect accessories individually after successful startup.

Expected outcome: The system starts normally with external accessories isolated. If one accessory consistently prevents startup, remove that accessory from use and troubleshoot or replace it separately.

6. Check Front-Panel Controls

Verify that the power control operates normally and is not physically stuck, contaminated, recessed, or damaged. Inspect surrounding controls for evidence of fluid intrusion.

Do not repeatedly cycle power if the unit produces abnormal sounds, odor, excessive heat, or repeated fault behavior.

Expected outcome: The controls respond normally and the system proceeds through startup.

7. Check Environmental Conditions

Confirm that ventilation openings are unobstructed and the unit is not positioned against drapes, walls, equipment, or other materials that restrict airflow.

If the unit has recently been moved from an unusually cold, hot, or humid area, allow it to stabilize in an appropriate clinical environment before testing.

Expected outcome: No obvious environmental condition is interfering with startup.

8. Perform a Controlled Restart

After external conditions have been verified, shut the system down normally if possible, disconnect AC power briefly, reconnect it to a known-good source, and perform one controlled restart.

Do not continue repeated restart attempts if the same failure recurs.

Expected outcome: The AirSeal iFS completes startup and reaches its normal ready condition. If it does, proceed to final verification.

9. Perform Final Functional Verification

Verify the display, controls, alarms, connected approved accessories, and intended operating functions using appropriate manufacturer documentation and approved test methods.

Do not return the device to service solely because it powers on.

Expected outcome: Startup and applicable functional checks complete normally without recurring alarms, shutdowns, or abnormal behavior. Troubleshooting can stop.

10. Escalate an Unresolved Startup Failure

If verified AC power, external connections, accessories, controls, and environmental conditions are normal but startup still fails, stop external troubleshooting.

Expected outcome: The unit is removed from service for bench evaluation rather than subjected to unnecessary disassembly or repeated power cycling.

If the Problem Persists

Common external causes have been ruled out. The remaining problem may involve internal power distribution, startup electronics, software, internal communication, configuration, or another service-level condition.

The device should be:

After service, complete appropriate operational and safety verification before returning the unit to clinical use.

Knowing when to stop external troubleshooting and escalate is proper troubleshooting.

Clinical Use Tip

If AirSeal functionality becomes unreliable during a procedure, transition to an approved alternate method before investigating the equipment.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Clinical staff reported that the CONMED AirSeal iFS would not complete startup before a procedure."

Cause

What was observed during troubleshooting.

Example:
"Clinical Engineering found the system connected to a faulty power source and confirmed normal startup from a verified receptacle."

Resolution

What action was taken.

Example:
"Connected the system to a verified power source, completed startup and functional checks successfully, and returned the unit to service."

Helpful Details to Include (If Known)

Final Thought

Protect the patient first, verify the complete external power and accessory path before assuming an internal failure, and stop when the problem requires service-level evaluation. Clear CCR documentation should show what was reported, what was actually found, and how safe operation was verified.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide