Locate the source, drive and receiving position for this task
Required inputs are the specific sensor configuration, location, liquid/tubing, sampling rate, thresholds and time windows. Confirm liquid contact, pressure and destination along each illustrated section before defining drive and connection responsibilities.
Tubing, velocity and gas-segment length determine the detection window
Specify tubing material, ID/OD, liquid properties, velocity and gas segments to detect. Transit time depends on velocity. Coordinate thresholds and debounce with the operating window, and confirm compatible tubing for the specific model.
| Condition to compare | Information required | Selection affected |
|---|---|---|
| Tubing and liquid | Tubing material, dimensions, optical condition and installation | Establish detection conditions |
| Bubble size | Length, flow velocity and actual transit time | Set time windows and debounce logic |
| Liquid destination during faults | Associate alarms with aspiration or delivery stages | Define stopping, priming and sample handling |
Compare product options against task requirements
The following candidate options match this page's responsibilities. Compare them against the operating conditions described, then check capacity, materials and interfaces on the product pages. Card images show representative configurations; suitability must still be confirmed at actual operating points and by application results.
| Product category | Corresponding role | Confirm before selection |
|---|---|---|
| ABD bubble-detection module | Bubble or liquid-state identification in defined tubing | Validate detection and false alarms for tubing material, dimensions, medium and action window |
Distinguish programmed air segments from unintended air
Set separate logic for priming, aspiration and delivery to avoid treating permitted air segments as faults. After an anomaly, the instrument controller should flag potentially affected doses, reprime and confirm recovery before resuming.
Action records should link commands, valve or interface states and actual received results. When raw material, container or sample identity changes, reconfirm shared paths and conditions permitting the next step. Completion of drive movement alone does not replace task acceptance.
Evaluate detection using the actual tubing and liquid
Test air-segment detection, false alarms, response time and restart with actual liquids and tubing. Changes in liquid state cannot automatically be converted into delivered volume.
| Validation scenario | Measurement or observation | Interpretation and action |
|---|---|---|
| Bubble detection | Cover target bubbles and normal liquid variations | Count missed detections and false alarms together |
| Resuming delivery | Check the first dose or initial flow segment after restoring the liquid column | Alarm clearance alone does not establish result validity |
Record test medium, configuration, installed path and operating sequence; present routine operating points and boundary results separately. Calculations support design discussions, component documentation checks models, and installed measurements confirm the actual task.
After an abnormality or maintenance, first identify which segment needs recovery
Normal air segments, viscosity changes and sampling delays may be misclassified. The controller determines task validity; sensors alone do not prove dose or assay results.
Retain current source, container identity, completed actions, valve or interface state and actual receiving information. Use the table to locate the stage that changed before deciding to retry, continue or restart. After recovery, recheck the relevant operating point before returning an uncertain action to the automatic cycle.