Canon Aquilion ONE / PRISM Edition

System Will Not Power On or Complete Startup

On this page

Asset Type

CT Scanner

Manufacturer

Canon

Model

Aquilion ONE / PRISM Edition

What This Guide Helps With

Addresses no-power, incomplete startup, or failed initialization caused by power, emergency-stop, workstation, connection, or facility-related conditions.

Step-by-Step Troubleshooting

1. Protect the Patient and Preserve Continuity of Care

Do not troubleshoot the CT system while a patient depends on it for an active or time-critical examination. Remove the patient from the scanner area when necessary and move urgent imaging to another verified system.

Confirm whether the reported problem affects the entire CT system, only the operator workstation, or one subsystem.

Expected outcome: The patient is safe, an alternate imaging pathway is available, and the exact affected portion of the system is identified.

If the system starts normally and remains stable after confirming the reported condition, troubleshooting can stop after functional verification.

2. Confirm the Exact Startup Failure

Ask clinical staff what occurred immediately before the problem. Determine whether the system is completely unresponsive, partially powered, stuck during initialization, repeatedly restarting, or displaying a specific message.

Record any displayed message exactly rather than interpreting it.

Expected outcome: The startup failure is reproducible or clearly characterized.

If the system now completes startup normally and no abnormal condition remains, continue to final verification.

3. Check Facility and System Power

Verify that the scanner's normal facility power sources and accessible disconnects or power controls are in their expected operating state. Check for signs of a recent outage, utility interruption, generator transfer, breaker event, or room power problem.

Do not reset facility electrical equipment unless authorized by site procedure.

Expected outcome: Required power sources are present and no obvious facility power interruption remains.

If facility power was the cause and the CT system starts normally after authorized restoration, troubleshooting can stop after verification.

4. Inspect Emergency-Stop and Safety Controls

Inspect accessible emergency-stop controls and other external safety interlocks for an activated, damaged, or abnormal condition.

Do not bypass or defeat any interlock.

Expected outcome: No emergency-stop or external safety control is preventing normal startup.

If an activated control is safely restored according to approved procedure and startup completes normally, troubleshooting can stop after verification.

5. Inspect External Connections and Workstation Power

Check accessible power cords, workstation power connections, display connections, and external communication cables for looseness, damage, or accidental disconnection.

Reseat only user-accessible or service-approved connections.

Expected outcome: External connections are secure and undamaged.

If restoring an external connection resolves startup, complete functional verification and stop.

6. Verify Operator Workstation and Display Operation

Determine whether the workstation, monitors, keyboard, mouse, and other operator-interface components are powered and responsive.

A blank display can be mistaken for a scanner startup failure.

Expected outcome: The operator interface powers normally and accepts input.

If the scanner was operating but the workstation or display connection was the only problem, correct the external cause and verify normal control.

7. Check Room and Environmental Conditions

Look for excessive heat, blocked equipment-room ventilation, water intrusion, unusual odor, smoke, or evidence of a cooling problem.

Do not continue powering equipment that shows evidence of overheating, electrical damage, water exposure, or burning odor.

Expected outcome: Environmental conditions are suitable for continued evaluation.

If an unsafe environmental condition is present, remove the equipment from service and escalate immediately.

8. Perform an Approved Controlled Restart if Appropriate

If the system is stable, no patient is dependent on it, and site/manufacturer procedures permit it, perform a normal controlled shutdown and restart using approved operating controls.

Do not repeatedly cycle system power in response to recurring failures.

Expected outcome: The CT system completes its normal startup sequence without recurring faults.

If startup completes and remains stable, proceed to final verification.

9. Perform Final Functional Verification

Confirm that the operator workstation is responsive, required scanner subsystems indicate ready status, gantry and table controls are available, and no unresolved startup or safety messages remain.

Use approved operational checks before returning the scanner to clinical use.

Expected outcome: The CT system starts normally and reaches a stable ready condition.

If achieved, troubleshooting is complete.

10. Escalate Persistent Startup Failure

If the system still will not start or initialize, stop external troubleshooting. Do not proceed into power distribution assemblies, cabinets, internal electronics, or restricted service functions without appropriate authorization and documentation.

Expected outcome: An unresolved system is kept out of clinical service and routed for qualified service evaluation.

If the Problem Persists

Common external causes have been ruled out. Remaining possibilities may include internal power distribution, control electronics, initialization faults, subsystem communication problems, cooling dependencies, facility infrastructure, or service-level configuration issues.

The CT scanner should be:

After repair, complete the required operational, safety, and image-system return-to-service checks before releasing the scanner for patient use.

Knowing when to stop external troubleshooting and escalate is proper troubleshooting.

Clinical Use Tip

Arrange alternate diagnostic imaging before extended troubleshooting when CT availability affects emergency, stroke, trauma, or other time-sensitive workflows.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"CT staff reported the Aquilion ONE / PRISM Edition would not complete startup after a facility power interruption."

Cause

What was observed during troubleshooting.

Example:
"Clinical Engineering found facility power had been restored but an accessible system power connection had not returned to its normal operating condition."

Resolution

What action was taken.

Example:
"Restored the approved external power condition, confirmed successful system startup and ready status, and verified normal operator controls before return to service."

Helpful Details to Include (If Known)

Final Thought

Protect the patient first, verify external power and safety conditions before assuming an internal failure, and escalate unresolved startup problems with clear documentation and proper return-to-service testing.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide