ConMed System 5000: troubleshooting and error codes
The ServiceForge knowledge base holds 25 documented symptoms for the ConMed System 5000, with 45 ranked causes, 65 diagnostic checks with test points and expected values, and 88 error codes. Each symptom below shows its causes and the first check; the rest is one connection away. Connect ServiceForge to your AI
Symptoms
No output power high voltage
System does not produce RF output power when activated
Ranked causes
- 1. Internal connections bad (common)
- 2. Faulty accessory with blade not fully seated (occasional)
- 3. Output board jacks not making contact (occasional)
- 4. Low voltage power supply bad (occasional)
- 5. Shorted RF Amplifier MOSFET (occasional)
- 6. HVPS output too low (occasional)
- 7. Improper gate drive (occasional)
Verify internal connector seating
- Test point
- A6J1, A6J2, A6J3, A6J4, A7J1, A7J2 connectors
- Expected
- All connectors fully seated
3 more checks with pass and fail actions, 7 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Display panel blank when powered on
No display visible when system is turned on
Ranked causes
- 1. Power cord not fully seated (common)
- 2. Fuses blown or improperly installed (common)
- 3. Controller board or harness not seated (occasional)
- 4. Low voltage power supply failure (occasional)
Verify power cord connection
- Test point
- Power receptacle on back panel
- Expected
- Fully seated
3 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Dispersive electrode status indicators flashing alternating red patient safety
Single or dual dispersive electrode alarm LEDs flashing red alternately
Ranked causes
- 1. Dispersive electrode not connected (common)
- 2. Dual dispersive electrode not properly applied to patient (common)
- 3. Dispersive electrode connector not fully seated (occasional)
Verify dispersive electrode connection
- Test point
- Dispersive Electrode Receptacle
- Expected
- Electrode connected and seated
1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Display shows A[[ [P xx (control panel error)
Control panel error code displayed on screen
Ranked causes
- 1. Faulty push button on front control panel (occasional)
- 2. Push button pressed during power-on (occasional)
- 3. Faulty cable connection between front panel and display board (occasional)
Verify no buttons pressed during power-on
- Test point
- Control panel buttons
- Expected
- No buttons actuated
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Display shows A[[ xxx (accessory error)
Faulty accessory error code displayed on screen
Ranked causes
- 1. Faulty accessory connected (common)
- 2. Hand-controlled accessory erroneously actuated (occasional)
- 3. Footswitch erroneously actuated (occasional)
Verify no footswitches are stacked
- Test point
- Monopolar and Bipolar footswitch connectors
- Expected
- Footswitches not stacked
1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Incorrect bipolar output
Bipolar output power does not match set value or expected output
Ranked causes
- 1. Bad calibration (common)
- 2. Incorrect load resistor when checking output (occasional)
- 3. Bad voltage or current feedback (occasional)
Perform bipolar output calibration
- Test point
- Bipolar output with calibrated load resistor
- Expected
- Output matches calibration targets per procedure
2 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Incorrect monopolar output
Monopolar output power does not match set value or expected output
Ranked causes
- 1. Bad calibration (common)
- 2. Incorrect load resistor when checking output (occasional)
- 3. Bad voltage or current feedback (occasional)
Perform monopolar output calibration
- Test point
- Monopolar output with calibrated load resistor
- Expected
- Output matches calibration targets per procedure
2 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Real Time Clock battery voltage low or not charged
Date defaults to 01 01 01 or time defaults to 12P 0 1, indicating Real Time Clock battery insufficient
Ranked causes
- 1. Real Time Clock battery voltage below 2V (common)
- 2. Real Time Clock battery not charged from previous service (occasional)
Verify date and time display
- Test point
- Display panel (Last Fault Code Mode)
- Expected
- Date shows actual month-day-year; time shows actual hours-minutes-seconds
3 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
A.R.M. dual electrode lower limit out of range patient safety
A.R.M. does not show green flashing with eight bargraph bars at lower resistance limit
Ranked causes
- 1. A.R.M. circuit calibration error or component fault (unknown)
Verify A.R.M. dual electrode lower limit indicator and bargraph response
- Test point
- Dual Dispersive Electrode Status/Alarm Indicator and Bargraph
- Expected
- Flashing green with eight bars illuminated Ohms
- Tools
- Decade Resistance Box
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
A.R.M. dual electrode upper limit out of range patient safety
A.R.M. does not show green flashing with single bargraph bar at upper resistance limit
Ranked causes
- 1. A.R.M. circuit calibration error or component fault (unknown)
Verify A.R.M. dual electrode upper limit indicator and bargraph response
- Test point
- Dual Dispersive Electrode Status/Alarm Indicator and Bargraph
- Expected
- Flashing green with one bar illuminated Ohms
- Tools
- Decade Resistance Box
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
A.R.M. single electrode upper limit out of range patient safety
A.R.M. does not show steady green indicator without flashing at upper resistance limit
Ranked causes
- 1. A.R.M. circuit calibration error or component fault (unknown)
Verify A.R.M. single electrode upper limit indicator response
- Test point
- Single Dispersive Electrode Status/Alarm Indicator
- Expected
- Green and not flashing Ohms
- Tools
- Decade Resistance Box
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Automatic Return Monitor (A.R.M.) dual electrode alarm limit out of range patient safety
A.R.M. does not flash red in alternating fashion when dispersive electrode resistance is at alarm threshold
Ranked causes
- 1. A.R.M. circuit calibration drift or component failure (unknown)
Verify A.R.M. dual electrode alarm limit indicator response
- Test point
- Single and Dual Dispersive Electrode Status/Alarm Indicators
- Expected
- Red alternating flash Ohms
- Tools
- Decade Resistance Box, dispersive electrode cable adapter
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: A.R.M.™ Dispersive Electrode connection high voltage
Calibrate Automatic Return Electrode Monitoring against two known precision resistances
Ranked causes
- 1. A.R.M.™ requires calibration with paired resistances (common)
Initiate A.R.M.™ calibration
- Test point
- Remote Power Control Key
- Expected
- Resistance value appears in Monopolar Coag Power Digital Display
5 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Bipolar modes high voltage
Calibrate Bipolar Macro mode using measured current or power against a precision resistor
Ranked causes
- 1. Bipolar mode requires power calibration adjustment (common)
Select calibration units (current or power)
- Test point
- Bipolar Power Adjustment Keys
- Expected
- A for current or P for power
3 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Complete and exit calibration mode caution
Exit calibration mode and prepare ESU for normal operation
Ranked causes
- 1. Calibration must be completed before normal operation (common)
Turn off main power
- Test point
- Main power switch
- Expected
- Power indicator extinguished
2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Monopolar modes high voltage
Adjust Monopolar Cut, Blend, Pinpoint Coag, Standard Coag, and Spray Coag modes using measured current or power against a precision resistor
Ranked causes
- 1. Mode requires power calibration adjustment (common)
Select calibration units (current or power)
- Test point
- Bipolar Power Adjustment Keys
- Expected
- A for current or P for power
3 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: System 5000 monopolar and bipolar output power
Verify and adjust output power calibration for Cut, Coag, Blend modes and Bipolar to match target values using load resistance and meter
Ranked causes
- 1. Calibration drift after component replacement or repair (common)
Set calibration system configuration DIP switch
- Test point
- Controller board A4SW2.2 and A4SW2.1
- Expected
- A4SW2.2 ON (UP), A4SW2.1 OFF (DOWN)
6 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Display shows [al (calibration mode)
Calibration mode is displayed on screen
Ranked causes
- 1. DIP switch 2 set to ON and Remote Power Control Key pressed during power-on (common)
Verify DIP switch 2 position
- Test point
- Controller assembly DIP switch position 2
- Expected
- OFF position for normal operation
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Display shows Err xxx (error code)
Error code is displayed on screen indicating a system fault
Ranked causes
- 1. System fault detected during POST or operation (unknown)
Attempt system reset via power cycle
- Test point
- Main power switch
- Expected
- Error clears or POST identifies fault
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Display shows LF[ xxx (last fault code mode)
Last fault code mode is displayed instead of normal operation
Ranked causes
- 1. Remote Power Control Key pressed during power initialization (common)
Power cycle system without pressing buttons
- Test point
- Main power switch
- Expected
- Normal operation display
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Error 140: Calibration memory error
Stored calibration values are corrupted or inaccessible, affecting output power accuracy
Ranked causes
- 1. Calibration memory corruption or Controller board failure (rare)
Verify Err 140 display
- Test point
- Monopolar Cut Power Digital Display
- Expected
- Err 140
1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Error 143: Mode calibration required
One or more operating modes require calibration after board replacement or calibration drift detected
Ranked causes
- 1. Board replacement (Controller, Transformer, or Output) or calibration drift (common)
Verify Err 143 display and affected modes
- Test point
- Monopolar Cut Power Digital Display and mode indicators
- Expected
- nEr with flashing minor mode indicators for modes requiring calibration
1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Flashing decimal points on display
Decimal point indicators on display are flashing
Ranked causes
- 1. Test Mode is active (common)
Verify DIP switch 1 position
- Test point
- Controller assembly DIP switch position 1
- Expected
- OFF position for normal operation
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Leakage current out of specification high voltage
Active RF output to neutral exceeds allowable limit during monopolar operation with footswitch or hand control activation
Ranked causes
- 1. Faulty monopolar active output relay or circuit (unknown)
Measure leakage current from footswitched monopolar active output to neutral with normal line/GND
- Test point
- Active output terminal to neutral
- Expected
- ≤15 μA, max
- Tools
- Leakage current meter, footswitch
2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Output coupling capacitor out of specification caution
Capacitance measured at output coupling does not meet expected values for monopolar or bipolar modes
Ranked causes
- 1. Faulty output coupling capacitor or circuit component (unknown)
Measure baseline output coupling capacitance without activation
- Test point
- Shorting plug adapter to footswitched ReadiPlug Universal Accessory Receptacle
- Expected
- <0.5 nF, max
- Tools
- Capacitance meter (≤1 kHz), shorting plug adapter, ≤6" test leads
2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Error codes
| Code | Meaning | Trigger | Severity |
|---|---|---|---|
100 | Test or CAL mode dip switch with no remote power control key press | Remote Power Control Key not depressed during power initialization or not released before last tone sounds | error |
101 | Controller/Monitor DIP switch mismatch | System Controller and Monitor detect different Configuration Dipswitch settings | error |
102 | Corrupted communications between System Controller and Monitor | Faulty data transmission from System Controller to Monitor through HPI port | error |
103 | Corrupted communications between System Controller and RF Controller | Faulty data transmission from System Controller to RF Controller through HPI port | error |
104 | Monitor TOKEN not incremented, monitor program scrambled | Faulty data transmitted from System Controller to Monitor through HPI port | error |
105 | Controller failed RAM test | Memory errors detected during POST | error |
106 | RF controller bootload program does not match controller ROM table | Faulty program transmission from System Controller to RF Controller at startup | error |
107 | Monitor bootload program does not match controller ROM table | Faulty program transmission from System Controller to Monitor at startup | error |
108 | RF TOKEN not incremented, RF controller program scrambled | Faulty or corrupted program transmission from System Controller to RF Controller at startup | error |
109 | Communications lost during POST tests | Faulty communications through HPI port | error |
112 | Pre-activation handshake, monitor does not read an activation signal | Activation signals detected by System Controller and Monitor do not match | error |
113 | Pre-activation handshake, monitor does not read a tone signal | Activation tone not present when Monitor checks prior to enabling electrosurgical output | error |
114 | Display or keyboard SPI communication failure | Communication failure between Control assembly and Display assembly over SPI bus | error |
117 | 5.0 volt too low | 5-volt power supply voltage drops below specification | error |
118 | 5.0 volt too high | 5-volt power supply voltage exceeds specification | error |
122 | System Controller flash program CRC does not match calculated CRC | Self-check CRC for System Controller not internally consistent | error |
135 | A.R.M. calibration (10/150 Ohm) EEPROM CRC failed | CRC for calibration coefficient memory not self consistent | error |
136 | A.R.M. circuit dropped below 0.4V (circuit failed) | A.R.M. circuit voltage falls below 0.4V | error |
137 | RF controller calibration EEPROM CRC failed | CRC for RF controller calibration coefficient memory not self consistent | error |
138 | Monitor calibration EEPROM CRC failed | CRC for Monitor calibration coefficient memory not self consistent | error |
139 | During calibration, not all points were entered for the mode | Calibration not completed in correct manner | warning |
140 | A calibration EEPROM CRC failed (POST ERROR) | CRC for calibration coefficient memory not self consistent during POST | error |
141 | Test and CAL dip switches are both turned on | Calibration and Test Configuration Dipswitches both in ON position | error |
142 | RF PWM (RF_PROT) gate protection circuit shutdown | Pulse width commanded by RF Controller exceeds maximum allowed for selected mode | error |
143 | Unit or a mode was never calibrated | System or mode never calibrated or Controller replaced without calibration | warning |
144 | RF controller and Monitor power levels do not match | Monitor and RF Controller sense different electrosurgical output power during activation | error |
170 | Controller waveform inhibit failed (will not disable RF) (POST ERROR) | Monitor detects that System Controller cannot disable RF Drive signal during POST | critical |
200 | Modality function timed out while waiting for ADC DMAs to finish | Component failure preventing ADC DMA operations from completing | error |
201 | RF Controller emulation restart | Programming function restart | info |
202 | Inter-processor communications error | Controller Assembly Host Port communication failure | error |
204 | Processor system clock change failed | Microprocessor clock frequencies do not change to correct frequency after initialization | error |
205 | Halt mode active beyond limit | Halt mode operation exceeds time limit | error |
206 | RF Controller discovered runtime bad CRC | Errors found in software downloaded from System Controller to RF Controller during initialization | error |
207 | Unexpected mode change while active | Selected output mode changes while system is activated | error |
236 | Bad CRC on modality coefficients | Modality coefficient CRC check failure | error |
237 | POST memory failure | Errors found in microprocessor memories during power initialization | error |
239 | RF Controller rejected a calibration value | Calibration failed for one or more modes | error |
311 | POST Monitor memory failure | Errors found in Monitor microprocessor memory during power initialization | error |
314 | POST Monitor or RF controller clock failure | RF Controller or Monitor clock oscillator failure detected during POST | error |
315 | POST Monitor activation circuitry failure | Activation request signal states do not match between Monitor and System Controller | error |
320 | Monitor failed program CRC test | Errors found in software downloaded from System Controller to Monitor during initialization | error |
321 | Monitor failed calibration data CRC test | Monitor calibration data CRC check failure | error |
322 | Monitor or RF controller did not return to IDLE state | Activation continues after activation command ceases | error |
330 | POST RF AC voltage cut feedback too low (A/D channel 0) | Monitor senses electrosurgical voltage output too low during POST test | error |
331 | POST RF AC voltage cut feedback too high (A/D channel 0) | Monitor senses electrosurgical voltage output too high during POST test | error |
332 | POST RF AC voltage coag feedback too low (A/D channel 2) | Monitor senses electrosurgical voltage output too low during POST test | error |
333 | POST RF AC voltage coag feedback too high (A/D channel 2) | Monitor senses electrosurgical voltage output too high during POST test | error |
334 | POST RF AC voltage coag feedback too low (A/D channel 1) | Monitor senses electrosurgical voltage output too low during POST test | error |
335 | POST RF AC voltage coag feedback too high (A/D channel 1) | Monitor senses electrosurgical voltage output too high during POST test | error |
336 | Calibration RF AC voltage cut feedback too high | Monitor senses electrosurgical voltage output too high during POST test | error |
337 | Calibration RF AC voltage cut feedback too low | Monitor senses electrosurgical voltage output too low during POST test | error |
338 | Calibration RF AC voltage coag feedback too high | Monitor senses electrosurgical voltage output too high during POST test | error |
339 | Calibration RF AC voltage coag feedback too low | Monitor senses electrosurgical voltage output too low during POST test | error |
340 | Monitor Timer0 interrupt failed | Internal timer failure during operation | critical |
341 | Monitor Timer0 interrupt failed POST | Internal timer failure detected during POST | critical |
342 | Monitor Timer1 interrupt failed POST | Internal timer failure detected during POST | critical |
343 | Monitor has lost communications - controller TOKENS not incremented | Loss of communication between Monitor and Controller | critical |
344 | Monitor Isense DMA or SPI hung | Monitor DMA or SPI interface failure | critical |
345 | Monitor Power DMA or SPI hung | Monitor DMA or SPI interface failure | critical |
350 | Monitor output channel current sensor failure | Current mismatch between output channel and power monitoring sensors | error |
351 | Monitor sensed over power condition for 300mS running average | Over power at electrosurgical output persists for more than 300 ms | error |
352 | Monitor sensed 4x over power condition for short period | Excessive power at electrosurgical output detected briefly | error |
357 | Monitor sensed power @ 0W dial power setting | Monitor detects electrosurgical output power during activation at zero power dial setting | error |
358 | Monitor sensed gate drive in idle @ 0W dial power setting | Drive signal detected while system is not activated | warning |
359 | Monitor sensed peak voltages above the LAP Limit | Voltage peaks exceed limits in Lap Advanced Specialty mode | error |
360 | Monitor program counter landed on an unused interrupt vector | Monitor processor anomaly | critical |
371 | Monitor will not disable RF waveform on the Controller assembly during POST | Monitor cannot disable RF waveform during POST | critical |
372 | Monitor will not disable high voltage during POST | Monitor cannot disable HVPS during POST | critical |
373 | Damping circuit failed POST – damping not detected | Damping drive signal failure detected during POST | error |
374 | Damping circuit failed POST – damping stuck on | Damping drive signal stuck on during POST, no RF output | critical |
379 | RF calibration failed POST | System calibration failure during POST | error |
381 | No tone feedback during POST | Monitor did not detect tones during POST | warning |
382 | Activation without a tone | Monitor did not detect a tone during activation | warning |
383 | RF Current sensed at an unselected output | Current flowing at an output that has not been selected | error |
384 | POST HVDC to 30V failed - supply too low | HVPS output is too low during Power-On Self Test | error |
385 | POST HVDC to 30V failed - supply too high | HVPS output is too high during Power-On Self Test | error |
386 | POST HVDC to 140V failed - supply too low | HVPS output is too low at 140V setting during POST | error |
387 | POST HVDC to 140V failed - supply too high | HVPS output is too high at 140V setting during POST | error |
388 | POST monitor timed out - did not respond to POST command | Monitor did not respond to Power-On Self Test command within timeout period | error |
389 | Dial setting over maximum limit | Front panel power setting exceeds limit for selected mode | warning |
391 | Monitor detected the wrong RF waveform | Monitor detected improper RF Amplifier drive waveform or frequency for selected mode | error |
392 | Monitor detected a pulse mode on-time that was too long | Active pulse mode pulses exceed nominal duration limits | warning |
393 | Vbias signal too high | Reference voltage on one or more ADC channels on Controller exceeds nominal | error |
394 | Vbias signal too low | Reference voltage on one or more ADC channels on Controller below nominal | error |
A[[ xxx | Accessory error code | Faulty accessory connected, hand-controlled accessory erroneously actuated, or footswitch erroneously actuated | error |
Err 100 | Error 100 fault code | Displayed when DIP switch 1 or 2 is ON and Remote Power Control Key is not pressed until Test Tone begins | error |
Err 140 | Calibration memory error; stored calibration values detected as invalid | Unit detects corruption or loss of calibration data in non-volatile memory | error |
Err 143 | One or more modes require calibration; specific modes lack valid calibration data | After board replacement (Controller P/N 61-6431, Transformer P/N 61-6445, Output P/N 61-6461) or calibration drift detected during preventative maintenance | error |
Likely causes and actions for each code are in ServiceForge. Connect ServiceForge to your AI
Community
0 fixes logged by technicians through their AI, with outcomes, for this model.
ServiceForge knowledge base record. Field-unverified unless technicians confirmed it. A teaching summary of the record, not a service manual. Export 2026-10-14.