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.
Normal variation and target faults determine the configuration
List actual pressures, normal variation, target anomalies and required response time for each state. Confirm PDM5 range, interface and medium compatibility for the specific model rather than inferring them from its name.
| Condition to compare | Information required | Selection affected |
|---|---|---|
| Measurement-range requirements | Actual pressure range, medium and wetted configuration | Check the specific model before committing to a pressure range |
| Action-specific baseline | Aspiration, dispensing, switching and normal load changes | Define time windows and permissible ranges separately |
| Diagnostic evidence | Pressure, liquid level, bubble and valve-position information | Do not interpret every fault through one threshold |
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 |
|---|---|---|
| PDM5 pressure-detection module | Pressure-state monitoring at a defined fluidic location | Confirm range and wetted configuration by model; validate normal baseline and abnormalities separately |
Establish baselines and duration criteria for each state
Record separate baselines for normal aspiration, dispensing, switching and washing, then define durations and thresholds. On alarm, preserve sample identity, operating stage and recorded delivery. Check the actual path before restarting.
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.
Validate alarms and recovery with controlled anomalies
Introduce controlled blockage, leakage and empty-source conditions, and observe detection, false alarms and recovery. After pressure normalizes, verify whether delivery or measurement can be released to resume.
| Validation scenario | Measurement or observation | Interpretation and action |
|---|---|---|
| Controlled fault conditions | Test blockage, leakage and empty sources separately | Compare fault discrimination and false alarms |
| Restart state | Recheck pressure, actual delivery and destination | Confirm baseline recovery before releasing valid operating cycles |
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.