Solutions

Sample transport robots

LabCarry manufactures sample transport hardware platforms with in-house robot bodies, load platforms, racks and fixtures. We integrate the sourced mobile base and, where specified, a robotic arm, then complete the hardware/firmware connections and agreed platform interface. Your software directs the transfer workflow and manages sample identity and task priorities.

What is a sample transport robot?

The transport unit may carry a rack, tray, cassette or enclosed carrier. A barcode or other identifier can be associated with the mission, but the workflow must define which controller reads it and records the result. Transport and sample identification are separate functions that need an explicit connection.

The transfer task

Manual sample movement can interrupt laboratory work and make transfer status difficult to track. Automating only the journey leaves gaps if the wrong rack is loaded, the destination is occupied or no controller confirms receipt. The design must cover these cases as well as normal travel.

Transfer sequence

Transfer sequence
  1. Release and identify the carrier
  2. Confirm correct loading
  3. Authorize transport
  4. Check the receiving station
  5. Transfer and acknowledge receipt
  6. Record completion or an exception

We agree the handoff signals, permitted movements and recovery steps with your integration team.

Application requirements

Defined transfers between storage, preparation and analysis stations in pharmaceutical, analytical, clinical or materials laboratories, subject to the actual sample-handling requirements.

Modules and interfaces

ModuleFunctionEngineering input
Carrier and retentionDefined container pattern and restraintContainer envelope, closure, loaded mass and permitted orientation.
Identity interfaceCarrier or sample identifier linked to a taskOwner of scanning, identifier format, mismatch handling and record destination.
Handoff moduleManual, fixed mechanism or robotic transferReceiving capacity, station ready signal and confirmed load state.
Mission recordsDispatch, collection, delivery and exceptionsTimestamps, event semantics and reconciliation with the laboratory system.

Hardware built around your carriers

We manufacture the body, carrier platforms, racks, fixtures and specified gripper hardware in-house. The selected mobile base and any robotic arm are externally sourced and integrated into the platform by LabCarry.

Our delivery includes the agreed hardware and firmware interoperability, external platform interface, assembly and calibration. The customer software uses that interface to direct transfers and manage identity, destination selection and laboratory workflow records.

Station and software interfaces

Define how the laboratory system requests a move, how the robot accepts it and how the destination confirms receipt. Set timeouts and escalation responsibilities for an occupied station, unreadable identifier or interrupted mission. Mission completion must describe the agreed handoff state, not merely arrival at a map coordinate.

Agree how the controller handles a repeated command after a connection interruption. A communication retry must be distinguishable from a request for a new physical transfer. Use the transfer record fields to define the required identifiers and acknowledgement rules with the software owner.

Operating conditions and verification

Tell us whether the load needs temperature control, containment or specific material compatibility. We review those requirements with your team before selecting the carrier. Your laboratory or system owner assesses sample integrity and approves the route and handling process.

How should carrier variants be controlled?

Define each permitted loaded configuration, including adapters and inserts. Two carriers with the same external size can differ in retention, identifier visibility or centre of mass. Treat those differences as requirements to review.

Variant informationManufacturing consequenceHandoff check
Carrier identity and revisionLabel location, reader mounting and any keyed mechanical features.The loaded carrier is associated with the intended task.
Insert, lid and retaining mechanismPart selection, assembly sequence and access for removal or cleaning.The system can distinguish the required retained and releasable states.
Loaded mass and distributionPayload support and approved loading arrangement.The agreed carrier remains in its intended position through the defined transfer.
Source and destination fixtureMating dimensions, orientation and transfer height.The receiving station confirms the specified physical receipt condition.

Include a permitted-variants list in the build package and reference it in the test plan. A new insert, changed container closure or altered label position may require a targeted review even if the base platform is unchanged.

What we need to review your project

  • Container and carrier drawings with size, mass and closure.
  • Sample-handling restrictions and acceptable transfer conditions.
  • Identity reading point and the controller that stores each event.
  • Source and destination availability signals.
  • Requirements for temperature, transit time or orientation, if applicable.
  • Exception handling for mismatch, spill concern, failed handoff and blocked route.

Common questions

Does a transport robot need to identify every sample?

The workflow may track a carrier or individual samples. Define the required level and how the carrier contents are associated with the mission.

Does arriving at the station complete the mission?

Only if the agreed definition is arrival. For a completed delivery, the receiving system should confirm the specified handoff state.

Can the robot transport reagents?

We first review the contents, container closure, retention, material compatibility and route with your team. Hazardous materials require a separate suitability assessment before a transport configuration can be agreed.

How should throughput be estimated?

Use the complete cycle, including queuing, loading, travel, access waits, unloading, charging and recovery. Travel speed alone does not determine completed transfers per hour.

What happens when a sample identifier is unreadable?

The project should define a hold state and a responsible recovery process. Avoid silently completing a mission with unknown or conflicting identity.

Can LabCarry build customer-specific racks?

Yes. LabCarry manufactures racks, platforms and related mechanical parts in-house. Provide carrier drawings, tolerances, quantities, materials and acceptance criteria so we can define the part and its platform interface.

Discuss your hardware requirements

Send us your carrier dimensions, workstation layout, software interface requirements and expected quantities.

Discuss an OEM Project