Search these docs, or ask Revo a question — answers link the pages they came from.
Define Labware
Defines and names a labware that is already on the system, and claims it, so that later steps can transfer it wherever they need. The labware is normally defined as being in a virtual store.
Define Labware Defines and names a labware that is already on the system, and claims it, so that later steps can transfer it wherever they need. The labware is normally defined as being in a virtual store.
| Parameter | Type | Description |
|---|---|---|
| Source Type ✱ | ObjectLocationType | What kind of place the labware is already in. Only Virtual Store is supported. Any other source type is rejected when the step runs. |
| Source Location ✱ | string | The virtual store the labware is already in. |
| Labware Name ✱ | string | The labware this step acts on, by the name it was given earlier in the schedule. Accepts a schedule parameter reference, so the name can be decided at run time rather than fixed here. |
| Notes | string | Free-text note kept with this step. It appears on the step in the schedule editor and in the event log, and has no effect on what the step does. Use it to record why the step is here. |
| Enabled | bool | Whether this step runs. Clearing it leaves the step in the schedule, in place and still configured, but skips it at run time. |
✱ Mandatory parameter