Getinge Magnus Series

Table Movement Functions Inoperative

On this page

Asset Type

Surgical Table

Manufacturer

Getinge

Model

Magnus Series

What This Guide Helps With

Identifies causes of complete loss of table movement, including power, control input, lockout conditions, and connection issues before internal failure is assumed.

Step-by-Step Troubleshooting

Ensure Patient Safety First

Verify Main Power Status

Check Emergency Stop / Lockout Condition

Confirm Battery Charge Level

Test Multiple Control Inputs

Inspect Hand Control / Pendant Connection

Check for IR Remote Issues (if applicable)

Listen for Motor or Relay Activity

Inspect for Obvious Mechanical Obstruction

Check System Status Indicators or Error Messages

Power Cycle the Table

If the Problem Persists

If all external power, control, and obstruction causes have been ruled out, the issue is likely internal (actuator failure, control board, or power distribution fault).

Remove the table from service, label it Out of Service, and send for repair or bench evaluation.

Recognizing when the issue is beyond external troubleshooting is essential to safe and effective Clinical Engineering practice.

Clinical Use Tip

Never attempt to troubleshoot table movement while a patient is on the table.

Always transfer the patient first to prevent injury from unexpected movement or instability.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Table not responding to any movement commands from hand control or remote."

Cause

What was observed during troubleshooting.

Example:
"Loose hand control connection at base prevented control signal transmission."

Resolution

What action was taken.

Example:
"Reseated hand control connector and verified full table movement functionality restored."

Helpful Details to Include (If Known)

Final Thought

Effective troubleshooting starts with simple, external checks and progresses logically. Ensuring patient safety, verifying power and control inputs, and knowing when to escalate prevents unnecessary risk and downtime. Clear documentation supports future reliability and faster repairs.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide