Where does the transport task begin and end?
Start with the physical item and two specific locations. “Move samples between instruments” is too broad to manufacture against. A usable task definition identifies the carrier, the pickup position, the receiving position and the condition that counts as a completed handoff.
For a closed rack moving from a preparation bench to an analyzer buffer, we first check who loads and unloads it. If a person loads and unloads the rack, the robot automates travel. If the intended task includes removing individual tubes or accessing the analyzer, additional manipulation or station hardware is needed.
- Preparation releases a rack
- Source confirms loading
- Platform transports the rack
- Receiver confirms handoff
What are the main parts?
| Element | Role | What to define |
|---|---|---|
| Mobile base | Supports and moves the load | Floor conditions, loaded envelope and load distribution. |
| Payload hardware | Retains the rack or carrier | Container geometry, contact surfaces and restraint. |
| Navigation and task control | Executes travel and mission states | Selected technology, site mapping and recovery responsibility. |
| Handoff interface | Coordinates source and destination | Readiness, load state, acknowledgement and timeout behavior. |
How is a mobile manipulator different?
A mobile manipulator adds an arm and task tooling to a mobile base. NIST describes this combination as a way to move a manipulator between workstations and studies its performance measurement. For a laboratory project, the practical distinction is whether the equipment only moves the carrier or must also reach, grasp and place an item.
Do not select an arm simply because it makes a platform appear more capable. First identify the endpoint action. A fixed transfer mechanism or a human handoff may be more appropriate for the defined workflow.
How do you turn a robot idea into a task specification?
Example brief: move an identified, closed rack from a preparation buffer to a receiving buffer, then make the platform available for its next task. A person loads the source buffer; the receiving station confirms the rack has been accepted. We use that task definition to agree the carrier support, station interface and completion signal.
| Definition to complete | Question for the project team |
|---|---|
| Start condition | Is the carrier ready, identified and retained, and which system authorizes dispatch? |
| Movement boundary | Which routes, doors and waiting areas are included, and who controls access? |
| End condition | Is arrival sufficient, or must the receiving station confirm physical possession of the carrier? |
| Human involvement | Who loads, unloads or recovers a task, and at which states? |
| Measured output | Are you counting journeys, carriers or accepted transfers over a defined period? |
This brief lets a hardware team define the payload interface while the integration team defines the station contract: readiness, permission, receipt and recovery. A shared contract prevents a mobile platform and an instrument from making incompatible assumptions about when a task is finished.
What should be checked before selecting a configuration?
Estimate the complete transfer cycle. Walking distance alone does not establish the benefit of a robot: queueing, handoff time, instrument availability and recovery can determine the actual result.
- Container size in mm, loaded mass in kg and permitted orientation.
- Route access, doors, corridors, workstation approach and charging.
- Which controller owns the mission and sample or carrier identity.
- Who performs pickup and unloading, and how completion is detected.
- What happens when the destination cannot accept the load.
Requirements to confirm for your application
A mobile laboratory robot is not automatically suitable for hazardous chemicals, clinical samples or a specified cleanroom class. It does not imply a universal payload, docking accuracy or battery endurance. The actual configuration and environment need review.
We turn the agreed workflow into mechanical drawings, interface definitions and hardware test criteria before releasing the build.
Common questions
Is every laboratory mobile robot autonomous?
The terminology varies. Specify the intended navigation, mission control and human intervention instead of relying on the label alone.
Can transport and sample identification be separate systems?
Yes. Define the interface that associates the physical carrier with the correct task and records its receipt.
What is the first input for an OEM review?
A clear transport task with container details, endpoints and manufacturing scope is more useful than a general request for a laboratory robot.
When should fixed transport be considered?
Evaluate a fixed transfer arrangement when endpoints are stable and its footprint, access and loading method suit the workflow. Compare the complete handoff and facility constraints before choosing mobility.
Does one robot need to know every individual sample identity?
Not necessarily. The integration design may associate a carrier identifier with a sample list maintained in another system. Define which system owns that association and how mismatches or changed contents are handled.
Technical references
How LabCarry supplies the hardware platform
LabCarry manufactures robot bodies, platforms, racks, grippers and other mechanical hardware in-house. Mobile bases and robotic arms are sourced from specialist suppliers. We integrate the selected devices, complete hardware/firmware interoperability and the agreed external platform interface, and perform hardware assembly and calibration.
The customer connects its scheduling software through that interface. Navigation supplied with the base, device-level integration and customer-level scheduling have distinct roles in the complete application.