CONMED System 2450 / 5000 Series

Error: Err 384 POST HVDC to 30V failed — supply too low.

On this page

Asset Type

Electrosurgical Unit (ESU)

Manufacturer

CONMED

Model

System 2450 / 5000 Series

What This Guide Helps With

This guide helps troubleshoot Err 384 on a CONMED System 2450 / 5000 Series electrosurgical unit when the generator fails POST because the high-voltage DC supply does not reach the expected 30V level.

This error can prevent the ESU from completing startup and should be treated as a real internal power supply, RF amplifier load, controller command, or cable-related fault until proven otherwise.

Step-by-Step Troubleshooting

Ensure Patient Safety First

Expected outcome: Patient care continues with a safe, working electrosurgical generator.

Why it matters: Err 384 indicates the generator did not confirm proper high-voltage power supply startup behavior. An ESU with unresolved power supply faults should not be used clinically.

Verify the Reported Error and Behavior

Expected outcome: Err 384 is confirmed and associated with a POST failure related to the HVDC supply not reaching the expected level.

Power Cycle the System

Expected outcome: The unit either completes POST normally or Err 384 repeats.

If the error clears and does not return during functional testing, document the event and complete normal safety and performance verification before returning the unit to service.

Check External Power and Basic Conditions

Expected outcome: The ESU receives stable AC input power with no obvious external power issue.

Inspect the Unit for Obvious Physical Problems

Expected outcome: No obvious contamination, damage, overheating, or environmental cause is found.

Observe HVPS LED2 During POST

Expected outcome: LED2 behavior helps indicate whether the HVPS is attempting to generate the expected POST voltage.

Isolate the RF Amplifier Load

Expected outcome: If LED2 illuminates after the HVPS-to-RF Amplifier cable is disconnected, suspect the RF Amplifier or related load condition. If LED2 still does not illuminate, continue evaluating the HVPS, controller commands, and cable connections.

Verify Cable Connections

Expected outcome: Cables are properly connected, undamaged, and fully seated.

Verify HVPS Control Signals in Test Mode

Expected outcome: The controller properly commands the HVPS, and the HVPS responds as expected.

Check HVPS Operation

Expected outcome: The HVPS either operates correctly or fails to reach or maintain the required POST voltage.

Determine the Likely Fault Area

Expected outcome: The issue is isolated to the HVPS, RF Amplifier, Controller assembly, cable connection, or an intermittent internal condition.

Stop When Resolved

If the Problem Persists

If Err 384 continues after power cycling, external checks, cable verification, HVPS LED2 observation, RF Amplifier isolation, and control signal checks, external and common causes have been ruled out.

A persistent Err 384 strongly indicates an internal failure involving the HVPS, RF Amplifier, Controller assembly, or related internal cabling.

The device should be removed from service, labeled Out of Service, and sent for repair or bench evaluation. Repair may require replacing or repairing the HVPS, RF Amplifier, Controller assembly, or cabling as indicated by test results.

Knowing when to stop is proper troubleshooting. An ESU with an unresolved HVDC POST failure should not be returned to clinical use.

Clinical Use Tip

Never troubleshoot Err 384 on an ESU that is needed for an active case. Move the patient or procedure to a backup generator first. A startup POST fault means the unit has already failed its internal readiness check, and clinical staff should not rely on it until the fault is corrected and the ESU passes verification.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"CONMED System 2450 / 5000 Series ESU reported Err 384 during startup. Unit failed POST with HVDC to 30V supply too low condition and was removed from service."

Cause

What was observed during troubleshooting.

Example:
"Err 384 confirmed during bench startup. External AC power and power cord checked good. Cable connections inspected. HVPS LED2 behavior checked during POST. Fault isolated to likely internal HVPS, RF Amplifier load, Controller assembly, or related cable issue depending on test findings."

Resolution

What action was taken.

Example:
"Power cycled unit and verified error behavior. Checked external power, inspected cables, observed HVPS LED2 during POST, and isolated RF Amplifier load as applicable. Unit remained Out of Service for repair/board-level evaluation, or defective assembly was replaced and ESU passed POST, safety testing, and functional output verification before return to service."

Helpful Details to Include (If Known)

Final Thought

Err 384 should be treated as a real startup power supply fault until proven otherwise. Start with patient safety, confirm the error, rule out power and connection issues, then logically isolate the HVPS, RF Amplifier, Controller assembly, and cabling. Do not return an ESU to service with an unresolved POST HVDC fault. Clear documentation protects the patient, the user, and the technician.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide