CONMED System 2450 / 5000 Series

Asset Type

Electrosurgical Unit (ESU)

Manufacturer

CONMED

Model

System 2450 / 5000 Series

What This Guide Helps With

This guide helps troubleshoot Err 352 on a CONMED System 2450 / 5000 Series electrosurgical unit. Err 352 indicates the monitor sensed a short-duration 4x over-power condition. This may point to unsafe RF output, output regulation failure, voltage or current sensing problems, calibration issues, or internal generator failure.

Step-by-Step Troubleshooting

1. Ensure Patient Safety First

• Remove the ESU from patient use immediately if Err 352 appears during setup, activation, or clinical use.
• Have staff switch to another approved ESU if electrosurgery is still needed.
• Do not continue using the generator with an unresolved over-power fault.
• Disconnect the active electrode, return electrode cable, footswitch, and accessories as appropriate.
• Label the device for Clinical Engineering evaluation.

Expected outcome: Patient care continues without relying on an ESU that may deliver excessive or unsafe RF output.

Why it matters: A 4x over-power condition can create a serious risk of unintended tissue damage, burns, or unsafe surgical energy delivery.

2. Verify the Reported Error and Behavior

• Confirm the exact displayed error is Err 352.
• Ask when the error occurred: during startup, during cut activation, during coag activation, only with a specific accessory, or intermittently.
• Ask what mode and power setting were being used when the error occurred.
• Document whether the error clears after power cycling or returns immediately.

Expected outcome: Err 352 is confirmed as the reported fault, and the failure pattern is understood.

Why it matters: Confirming the exact code prevents chasing the wrong ESU fault and helps separate a setup issue from a generator fault.

3. Check External Power and Setup First

• Inspect the AC power cord, plug, outlet, and power entry area for damage, looseness, heat, discoloration, or electrical stress.
• Verify the unit is connected to a proper hospital-grade outlet.
• If outlet power is questionable, test the unit from a known-good outlet.
• Do not use extension cords, damaged power strips, or questionable power sources during testing.

Expected outcome: Power input problems are ruled out before deeper troubleshooting begins.

Why it matters: Poor or unstable power can cause abnormal equipment behavior, but an over-power ESU fault must still be treated seriously.

4. Inspect Accessories and Connections

• Remove all accessories from the ESU.
• Inspect the active electrode cable, return electrode cable, bipolar cable, footswitch, adapters, and connectors.
• Look for damaged insulation, bent pins, contamination, fluid intrusion, loose fit, or signs of overheating.
• Reconnect only known-good accessories needed for controlled bench testing.

Expected outcome: Damaged or questionable accessories are removed from the test setup.

Why it matters: Accessory or cable problems can create abnormal loading, activation issues, or misleading ESU fault behavior.

5. Confirm the Error Under Controlled Bench Conditions

• Move the ESU to a safe bench test area.
• Connect the generator to an appropriate ESU analyzer or fixed test load.
• Use only approved test accessories and a known-good footswitch or handswitch.
• Attempt to reproduce Err 352 under controlled activation.

Expected outcome: The error either repeats during controlled testing or does not return after external variables are removed.

Why it matters: Bench testing helps separate clinical setup problems from a true internal generator problem.

6. Configure the System for Test Mode

• Configure the system for test mode according to approved service documentation and facility procedure.
• Do not perform internal adjustments or repairs beyond your facility’s authorization level.
• Prepare to measure actual RF output power into a fixed load.

Expected outcome: The ESU is ready for repeatable RF output verification.

Why it matters: Err 352 is related to monitored output power. Test mode allows the output and sensing behavior to be evaluated more consistently.

7. Measure Actual Output Power Into a Fixed Load

• Connect the ESU to the specified fixed load or ESU analyzer load.
• Activate the unit at controlled settings.
• Compare measured output power to the expected output for the selected mode and setting.
• Watch for output significantly higher than the selected power, erratic output, output spikes, or error recurrence during activation.

Expected outcome: Output power is stable and within expected limits, or abnormal over-output is confirmed.

Why it matters: Err 352 may indicate true excessive RF output, or it may indicate that the monitoring circuit incorrectly believes output is excessive.

8. Determine Whether the Fault Is True Over-Output or Sensing-Related

• If measured output power is actually excessive, suspect an RF output regulation or power control problem.
• If measured output power is correct but Err 352 still occurs, suspect voltage/current sensing or monitor feedback circuitry.
• Compare measured output behavior against system-reported output behavior when possible.

Expected outcome: The fault path is narrowed to either actual RF output failure or inaccurate sensing feedback.

Why it matters: The repair path changes depending on whether the ESU is truly over-outputting or falsely detecting an over-power condition.

9. Recalibrate the System if Appropriate

• If the system is stable enough for calibration and your facility is authorized to perform it, recalibrate the ESU according to approved service procedure.
• After calibration, repeat output power testing into a fixed load.
• Confirm that measured output remains within expected limits and Err 352 does not return.

Expected outcome: Calibration completes successfully and the error does not return during controlled testing.

Why it matters: Service guidance identifies recalibration as an appropriate corrective step for this fault when conditions allow.

10. Verify Monitor and RF Controller Sensing Path

• If Err 352 persists, evaluate the monitor voltage/current sensing circuits according to approved service procedure.
• Evaluate the RF Controller voltage/current sensing circuits.
• Look for incorrect feedback readings, unstable sensed voltage or current, mismatch between measured output and sensed output, or internal connector issues affecting feedback signals.

Expected outcome: Feedback and sensing circuits are verified or identified as likely fault sources.

Why it matters: The system depends on accurate RF voltage and current sensing to detect over-power conditions correctly.

11. Evaluate Likely Internal Power Section Failure

• If external causes, accessories, test setup issues, and calibration are ruled out, suspect internal generator failure.
• Likely internal fault areas include the HVPS, RF Amplifier, RF Transformer board, RF Output board, or Controller assembly.
• Escalate to qualified bench repair, authorized service, or vendor repair as appropriate.

Expected outcome: The device is identified as requiring internal repair or qualified evaluation.

Why it matters: A persistent 4x over-power fault is not a normal user-correctable issue and should not be cleared casually.

12. Stop When Resolved

• If recalibration or correction of an external/test setup issue resolves the error, repeat functional testing.
• Confirm output power is stable into the proper load.
• Verify Err 352 does not occur during activation.
• Complete any required electrical safety and performance testing before return to service.

Expected outcome: The ESU operates normally and safely without recurring over-power errors.

Why it matters: The unit should only return to service after the fault is resolved and safe performance is verified.

If the Problem Persists

If Err 352 continues after external power checks, accessory checks, controlled bench testing, output verification, and recalibration when appropriate, external and common causes have been ruled out.

A persistent Err 352 strongly suggests an internal RF output regulation, voltage/current sensing, HVPS, RF amplifier, RF output, RF transformer, or controller-related failure.

• Remove the ESU from service.
• Label the unit Out of Service.
• Send the device for repair, vendor service, or qualified bench evaluation.

Do not return the ESU to clinical use until the fault is corrected and required performance testing confirms safe operation.

Clinical Use Tip

Never troubleshoot an ESU over-power fault on an active patient. If Err 352 appears during a case, staff should stop using that generator, move the patient setup to a backup ESU if electrosurgery is still needed, and send the failed unit to Clinical Engineering after it is removed from service.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"CONMED System 2450 / 5000 Series ESU displayed Err 352 during use. Error indicates the monitor sensed a short-duration 4x over-power condition. Unit removed from service due to possible unsafe RF output."

Cause

What was observed during troubleshooting.

Example:
"Err 352 confirmed during evaluation. External power, accessories, and test setup were checked. Output power testing and recalibration were attempted as applicable. Persistent fault indicates likely internal RF output regulation or voltage/current sensing failure involving monitor/RF controller feedback path, HVPS, RF amplifier, RF transformer board, RF output board, or controller assembly."

Resolution

What action was taken.

Example:
"Removed ESU from patient use and labeled Out of Service. Tested with known-good accessories and fixed load. Recalibrated/tested per service procedure as applicable. Unit requires repair or qualified bench evaluation before return to service."

Helpful Details to Include (If Known)

• Alarm behavior
• Accessories swapped
• Power behavior
• Environmental factors
• Indicator lights
• Final device status

Final Thought

Err 352 should be treated as a serious ESU output safety fault until proven otherwise. Good troubleshooting starts with patient safety, confirms the exact system-reported error, rules out simple external causes, verifies output under controlled conditions, and escalates when internal RF power or sensing failure is likely. Clear CCR documentation protects the patient, the technician, and the repair process.

That is successful troubleshooting.