Describe the symptom precisely
Record what the user expected, what actually happened, when it occurred, which mode was active, whether the symptom repeats, and which system messages appeared. Preserve exact wording and timestamps.
A safety-aware diagnostic framework
Good troubleshooting is structured evidence collection. It narrows the faulty boundary without guessing, creating new hazards, or treating an error code as a parts order.
Record what the user expected, what actually happened, when it occurred, which mode was active, whether the symptom repeats, and which system messages appeared. Preserve exact wording and timestamps.
Determine whether the problem affects one protocol, accessory, detector, workstation, user, room, network destination, or the entire system. Scope often separates a central failure from a local configuration or peripheral.
Map inputs, outputs, power, communication, cooling, motion, calibration, software, and environmental dependencies around the symptom. A block diagram is more reliable than replacing the first part named in an error.
Use approved logs, built-in diagnostics, visual inspection, known-good workflow checks, service history, and documented test tools. Do not create exposures, bypass covers, defeat interlocks, or enter controlled areas without authorization.
Where the approved procedure permits, make one reversible change at a time and record the result. Multiple simultaneous changes destroy evidence and can introduce a second fault.
After corrective work, complete the manufacturer-specified functional, safety, calibration, image-quality, and return-to-service checks. Record results, not only that the task was completed.
Four useful distinctions
Stop and escalate when the work exceeds training or authorization; controlled documentation is missing; safety interlocks, radiation, high voltage, magnet hazards, stored energy, contamination, or heavy motion are involved; required test equipment is unavailable; or return-to-service criteria cannot be met.