Locate the task in the fluid path first
Arrows indicate task relationships, not that every component is connected in series in one tube. Check valve positions, pump wetted boundaries and operating states for each branch.
Define each liquid action as a traceable state transition: prepare, reserve, execute, confirm and release. Command receipt, valve positioning and actual liquid delivery are different events and need separate roles in interlocks and records.
Common product roles and application guides
| Product category | Role in this instrument |
|---|---|
| Syringe pump | Discrete metering at workstations |
| Air-displacement pipetting pump | Tip-based pipetting at stations |
| Diaphragm pump | Shared platform supply and washing; suitable shared waste aspiration |
| Fluidic valves | Selection of shared fixed-path resources; branch isolation and state interlocks |
| Bubble and pressure detection | Branch signals used by platform control |
| Tubing and fittings | Sealed, maintainable connections between modules |
- Syringe pumps in workstation fluidic integration
- Air-Displacement Pipetting Pumps for Platform Fluidic Integration
- Diaphragm Pumps for Platform Fluidic Integration
- Fluidic valves in workstation fluidic integration
- Bubble and pressure detection in platform fluidics integration
- Tubing and fittings in platform fluidics integration
Operating requirements differ by step
| Stage | Task category | Operating conditions to define |
|---|---|---|
| Fluid-path management: define occupancy and interlocks | Shared pumps, valves, wash stations and waste paths | Active sample and receiving container; resources reserved by each action; allowed concurrency; valve and motion confirmations; when resources can be released |
| Module interfaces: verify both communications and fluid connections | Module identity and the installed liquid path | Controller address and module identity; source-to-outlet tubing direction; interfaces, materials and installed pressure; priming sequence and the first working-volume check after reconnection |
| Alarm recovery: distinguish actions that can and cannot be retried | Recovery at a known dispensing stage | Interruption before, during or after delivery; current container and resource occupancy; measured, estimated or unknown delivered volume; conditions for resuming, discarding or repeating |
Fluid-path management: define occupancy and interlocks
Define resource conflicts for pumps, valves, stations and waste handling. Sequential and concurrent actions should follow the same state diagram. If confirmation is lost, preserve sample identity and completed-step records.
Module interfaces: verify both communications and fluid connections
Correct module identification still requires verification of tube direction, seals and operating parameters. Post-maintenance release criteria should include priming and working-volume verification.
Alarm recovery: distinguish actions that can and cannot be retried
Resending the same command after partial delivery can duplicate an addition. Define stage-specific stop, resume or discard rules, and keep traceable records.
Explore configurations through product application guides
- Syringe pumps in workstation fluidic integration
- Air-Displacement Pipetting Pumps for Platform Fluidic Integration
- Diaphragm Pumps for Platform Fluidic Integration
- Fluidic valves in workstation fluidic integration
- Bubble and pressure detection in platform fluidics integration
- Tubing and fittings in platform fluidics integration
Validate the complete cycle through application results
For a workstation, coordinate shared pumps, wash stations and waste paths with the active container and step. Test interrupted operations separately before delivery, during partial delivery and after completion; the controller must establish the actual state before retrying.
Validate concurrency, restart after interruption and record traceability to prevent sample misassignment or duplicate dosing.
| Step to validate | Measurements or observations | Priority troubleshooting checks |
|---|---|---|
| Fluid-path management: define occupancy and interlocks | Run tasks that request the same resources, including interrupted actions; check that reservations, sample identities and actual receiving locations remain consistent. | A resource released too early or a stale container position can direct a later operation to the wrong sample even when individual commands succeed. |
| Module interfaces: verify both communications and fluid connections | After module replacement, verify physical routing and sealing, prime the path and measure the first intended transfer at its receiver. | A correct module address does not confirm tube direction, priming or delivery; investigate these before changing a metering program. |
| Alarm recovery: distinguish actions that can and cannot be retried | Interrupt dispensing before delivery, partway through and after completion. Compare recorded state with the liquid received and verify the permitted resume or discard action. | Retain uncertainty when delivery cannot be established. Repeating an unverified command can add a second dose to the same container. |
Connectable modules are not automatically plug-and-play. Recovery actions must match the current liquid and sample state.
Common selection and recovery questions
Does a successful communication command prove liquid delivery?
Also verify flow direction, source, receiver and actual liquid results. Associate module recognition and motion completion with the relevant operating-condition records separately.
Can every alarm use the same retry strategy?
Distinguish interruptions before, during and after delivery, and record the current container and resource state. Define stage-specific conditions for resuming or restarting.