On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting rack movement, sample transport, strip handling, or positioning faults caused by loading, obstruction, contamination, or external setup issues.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Confirm the Urisys 1800 is not actively processing patient samples before troubleshooting.
If testing is needed immediately, have laboratory staff use another validated analyzer or follow approved downtime procedures.
Expected outcome: No patient results are delayed, lost, or reported from an analyzer with an unresolved transport fault.
Stop Additional Testing
Ask staff not to load additional racks until the transport issue is understood.
Confirm whether any specimens were in process when the fault occurred and whether results were completed, aborted, or need repeat testing per lab policy.
Expected outcome: Questionable or incomplete urine results are not released.
Verify the Exact Fault
Review the displayed error message and ask staff when the fault occurs.
Check whether the issue happens:
- When the rack is loaded
- During rack advancement
- At sample aspiration or strip handling
- During startup
- After cleaning or maintenance
- With one rack or all racks
Expected outcome: The failure is narrowed to rack loading, rack detection, sample transport, or general mechanical movement.
Check Rack Loading and Orientation
Confirm the rack is loaded in the correct direction and seated fully in the rack input area.
Verify tubes are placed correctly and are not leaning, oversized, uncapped improperly, or interfering with rack movement.
Expected outcome: The rack moves normally when loaded correctly.
If corrected rack placement resolves the issue, return the analyzer to service after confirming normal operation.
Inspect the Rack for Damage or Contamination
Remove the rack and inspect it for cracks, bent sections, worn guides, missing identifiers, residue, dried urine, label adhesive, or anything that could affect movement.
Try a clean, known-good rack if available.
Expected outcome: The analyzer transports the known-good rack without fault.
If a damaged or contaminated rack caused the problem, remove that rack from use.
Check for Obstructions in the Rack Path
With the analyzer stopped and safe to access, inspect the external rack loading and transport path for:
- Misplaced sample tubes
- Broken caps
- Paper labels
- Dried urine residue
- Cleaning wipes
- Debris
- Misaligned rack guides
Do not force any mechanism or reach into moving parts.
Expected outcome: The rack path is clear and unobstructed.
Clean User-Accessible Transport Areas
If residue or contamination is visible, clean only the user-accessible rack path and surrounding surfaces using facility-approved cleaning materials and the manufacturer-approved cleaning approach.
Allow surfaces to dry before retesting.
Expected outcome: Rack movement is no longer affected by buildup, sticky residue, or debris.
Check Sample Tube and Label Condition
Inspect tubes in the affected rack for poor label placement, loose barcode labels, excessive label thickness, caps not fully seated, or tubes that do not fit the rack properly.
Replace or re-rack any questionable specimens according to lab procedure.
Expected outcome: Tubes sit properly and do not interfere with rack transport or detection.
Confirm the Analyzer Is Level and Stable
Verify the Urisys 1800 is on a stable, level bench with enough clearance around the rack loading and exit areas.
Make sure the analyzer has not been pushed against a wall, cable bundle, printer, waste container, or another device.
Expected outcome: Rack movement is not restricted by bench setup or surrounding equipment.
Check External Power Stability
Confirm the power cord is fully seated at the analyzer and wall outlet.
Verify the outlet is live and not controlled by a wall switch or loose power strip.
Expected outcome: The analyzer has stable power during transport movement.
Why it matters: Intermittent power or low voltage can cause incomplete movement, startup faults, or repeated transport errors.
Restart the Analyzer If Safe
If no samples are in process and lab workflow allows, power the analyzer down using the normal shutdown process.
Wait briefly, then restart and allow the system to complete initialization.
Expected outcome: The analyzer completes startup without rack or transport errors.
Run a Controlled Test With a Known-Good Rack
After clearing obstructions and confirming setup, have staff perform an appropriate non-patient test or QC workflow using a clean, known-good rack.
Observe whether the rack advances smoothly and whether the error returns.
Expected outcome: The rack transport operates normally without hesitation, grinding, repeated stopping, or error messages.
Listen and Observe During Movement
Watch for uneven movement, repeated retries, unusual motor noise, clicking, slipping, vibration, or rack skewing.
Do not bypass covers, defeat safety features, or force movement.
Expected outcome: Any abnormal mechanical behavior is identified without unsafe intervention.
Review Recent Changes
Ask whether the issue started after:
- Rack change
- New tube type
- New barcode labels
- Spill or leak
- Cleaning
- Analyzer relocation
- Power interruption
- Recent service activity
Expected outcome: A likely external trigger is identified before internal failure is suspected.
Determine Whether the Fault Is Isolated or Repeatable
If the fault occurs only with one rack or one sample setup, remove that rack or sample condition from use.
If the fault occurs with multiple clean racks after obstruction, power, bench setup, and sample loading checks are complete, treat the issue as a likely internal transport fault.
Expected outcome: Clinical Engineering has a clear basis for either returning the device to use or escalating for repair.
If the Problem Persists
If the rack or sample transport fault continues after checking rack condition, loading orientation, tube fit, obstructions, contamination, bench clearance, power, and restart behavior, common external causes have been ruled out.
The issue may involve an internal transport motor, rack sensor, drive mechanism, alignment problem, or control fault.
The device should be:
- Removed from service
- Labeled Out of Service
- Sent for repair, vendor service, or bench evaluation
Knowing when to stop is proper troubleshooting. Do not force rack movement, bypass covers, or attempt internal adjustment without approved service documentation and authorization.
Clinical Use Tip
Do not troubleshoot rack movement while active patient samples are being processed. Secure the specimens, move testing to another validated analyzer if needed, and confirm whether any interrupted samples require repeat testing before returning the device to service.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Laboratory staff reported the Roche Urisys 1800 stopped during rack advancement and displayed a sample transport fault."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found dried urine residue and a loose barcode label obstructing the rack path."
Resolution
What action was taken.
Example:
"Removed the obstruction, cleaned the user-accessible rack transport area, verified operation with a known-good rack, and returned the analyzer to service."
Helpful Details to Include (If Known)
- Exact error message displayed
- Whether the fault occurred during startup, loading, or sample processing
- Rack ID or rack type involved
- Whether one rack or all racks were affected
- Sample tube type and label condition
- Any visible obstruction or dried residue
- Whether a known-good rack was tested
- Power outlet or power cord condition
- Unusual motor noise, clicking, grinding, or hesitation
- Recent cleaning, spill, relocation, or service
- Final device status
Final Thought
Rack and sample transport faults should be approached logically and safely. Start with the rack, tubes, labels, obstructions, contamination, power, and bench setup before suspecting internal failure. If the fault repeats after external causes are ruled out, remove the analyzer from service and escalate appropriately. Clear CCR documentation protects patient safety and helps the next technician or vendor understand what was tested.
That is successful troubleshooting.