On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide helps troubleshoot Error E328 Unintentional Input on the Medtronic Valleylab FT10 electrosurgical unit. This condition may be caused by a stuck, pressed, damaged, contaminated, or falsely detected front panel button input. If unresolved, it can affect confidence in ESU controls, settings, and safe device operation.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Remove the Valleylab FT10 from patient use if Error E328 appears during setup, standby, or active procedure use.
- Stop using the ESU if the front panel input appears unreliable.
- Provide another known-working ESU if the procedure is active or urgent.
- Do not continue using the unit if settings change unexpectedly, buttons respond incorrectly, or the error returns after reset.
Verify the Reported Error and Behavior
- Power the unit on and observe the display.
- Confirm the message is Error: E328 Unintentional Input.
- Note whether the condition appears at startup, after touching the front panel, during setup, intermittently, after cleaning, or only when pressure is applied to the display or front housing.
- Confirm whether the error is reproducible or clearly observed before assuming a device failure.
Inspect the Front Panel for a Stuck or Pressed Button
- Look closely at the front panel buttons and surrounding bezel.
- Confirm no button is physically pressed, stuck, tilted, cracked, or trapped under the front panel overlay.
- Gently release any button that appears depressed.
- Do not pry into the panel or disassemble the front housing during basic troubleshooting.
Check for Fluid, Cleaner Residue, or Contamination
- Look for cleaning solution, gel, dried residue, tape, lint, drape material, or debris around the front panel.
- Clean the exterior according to approved facility cleaning practices.
- Allow the unit to fully dry before retesting.
- Confirm no visible contamination remains around the buttons, display, or front panel seams.
Remove External Pressure From the Display or Chassis
- Confirm nothing is leaning against the front panel.
- Check that the unit is sitting flat on the cart or shelf.
- Verify the front housing is not warped, cracked, pinched, or compressed by mounting hardware.
- Move the ESU to a stable surface and retest.
Power Cycle and Retest
- Turn the Valleylab FT10 off.
- Disconnect it from AC power briefly if appropriate for your facility process.
- Reconnect power and restart the unit.
- Observe whether Error E328 returns.
- If this resolves the issue, complete functional checks before returning the device to service.
Check Power Source and Line Cord
- Plug the FT10 into a known-good hospital-grade outlet.
- Inspect the power cord for damage, looseness, or strain.
- Avoid power strips, loose outlets, or questionable OR boom receptacles during testing.
- Confirm the unit powers on normally without intermittent resets or error recurrence.
Check for Repeatability With No Accessories Connected
- Disconnect handpieces, foot pedals, patient return electrode cables, and other accessories.
- Power the unit on with only AC power connected.
- Observe whether E328 returns.
- This helps separate a front panel or chassis input problem from a separate accessory or setup issue.
Reconnect Accessories One at a Time
- If the error cleared with accessories removed, reconnect accessories one at a time.
- Observe the display after each connection.
- Replace any damaged or questionable accessory.
- E328 should not return during accessory reconnection.
Evaluate for Device-Level Failure
- Document whether the error occurs at startup with no accessories connected, only after button use, after cleaning, when pressure is applied to the front panel, or intermittently during handling.
- Persistent E328 after external checks indicates the issue is likely within the front panel input path, display assembly, chassis, or controller-related circuitry.
- Do not perform internal disassembly during basic clinical troubleshooting.
If the Problem Persists
If Error E328 returns after the front panel is released, cleaned, dried, inspected, power cycled, and tested without accessories, remove the Valleylab FT10 from service.
External and common causes have been ruled out. A persistent E328 condition suggests a device-level fault involving the display/front panel input path, chassis pressure issue, or controller-related failure.
- Remove the ESU from service.
- Label it Out of Service.
- Send it for repair or bench evaluation.
- Do not return it to clinical use until the error is resolved and the unit passes required performance and safety checks.
Clinical Use Tip
Never troubleshoot an ESU with unresolved input errors on an active patient. Move the patient or procedure to a backup device first. A device that detects unintended front panel input should not be trusted for patient use until corrected.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Valleylab FT10 reported Error E328 Unintentional Input during startup/setup. Staff reported a front panel input error and removed the unit from OR use."
Cause
What was observed during troubleshooting.
Example:
"Front panel buttons were inspected for stuck input, contamination, pressure, and chassis damage. Unit was power cycled and tested on a known-good outlet. Error returned with accessories removed, indicating likely internal display/front panel, chassis, or controller input fault."
Resolution
What action was taken.
Example:
"Removed unit from service, labeled Out of Service, and sent for bench evaluation/repair. Device was not returned to clinical use due to recurring E328 condition."
Helpful Details to Include (If Known)
- Alarm behavior
- Accessories swapped
- Power behavior
- Environmental factors
- Indicator lights
- Final device status
Final Thought
Error E328 should be treated as more than a nuisance message. It means the Valleylab FT10 is detecting unintended front panel input, which can affect confidence in device control. Start with patient safety, check simple external causes first, isolate accessories and power, then escalate when the error persists. Clear documentation helps repair teams understand whether the issue is mechanical, environmental, or likely internal.
That is successful troubleshooting.