Get Started
This article will walk you through the setup process to:
Create a new device configuration, where on-deck carriers are set up to disallow lids, and hotel positions are set up to allow lids
Create new plate definitions for lidded plates in device software and in Synthace
These setup steps require one-time configuration for any lidded labware you want to use.
Trigger lid-handling
The configured labware is first selected within the respective Synthace element. In the example below you can see that a lidded plate has been selected as a collection plate in a robocolumns workflow
Lidding and delidding of labware is handled by implicitly by Synthace and Fluent Control when a plate is moved from a carrier position which allows lids to one which does not. See below for details on how to configure i) labware as
lidded
and ii) carrierlid
parameters.Plate movements are automatically scripted by Synthace when:
Moving plates for fraction collection (robocolumns)
Making use of accessible devices, such as a plate reader of washer
Using the
Move Plates
elements
Understanding how lids are handled
When triggered Lid-handling will proceed in the following way:
Labware must start off lidded - typically in a hotel or storage location that is inaccessible to the pipetting arm
For any liquid handling and other operations, plates are moved on deck, onto positions that are configured not to allow lids
As plates are moved, they are also de-lidded. This automatically ensures that the labware is de-lidded before any liquid handling actions.
Plates are lidded again once returned to the hotel - e.g. at the end of a fraction collection stage, in the case of robocolumns, or with a Move Plates element in other workflows.
Part 1: Create a distinct version of the lidded plate in FluentControl
Create a new labware item in Fluent Control. The new labware should have
Vendor Name
andPart Number
completed and matched, and, where required, these parameters should be different from the version of the labware type that represents the same plate but with no lid.
For example:
Note: Learn more about Labware Matching here.It should have a
SynthaceLiddedPlate=true
Custom Attribute.
Part 2: Check FluentControl carrier configurations
The worktable contains carriers that can be used as permanent locations for lidded plates. These are carriers that have the following settings (Synthace automatically puts a lidded plate on such a carrier only):
By contrast, the carriers where lidded plates will be put temporarily during the workflow — namely the plate nest chosen as temporary location in Workflow Builder, Te-Shuttle, etc. — have to have the following settings:
Lid
custom attribute present and set tofalse
.
It is most likely, that hotels already satisfy these requirements. We highly recommend that these sites be used as the starting positions for lidded plates where possible.
Part 3: Create a plate type for the lidded plate in the Synthace Plate Library
Manufacturer
andNumber
should match the ones of the Fluent labware type.Other fields can be copied from the plate type representing the same plate but with no lid.
For example:
Part 4: Generate a new configuration
Instructions for how to generate a new configuration can be found here.
🎉 And that’s it! Once a lidded plate type is used in the workflow, Synthace will put its instances on permanent carriers (eg. hotels), and then FluentControl will de-lid them when they’re temporarily moved on temporary carriers (eg. carriers on deck) — and re-lid them when they’re moved back on their permanent locations.
Note: The current implementation of this functionality has some known limitations
Permanent locations of lidding plates must not be
Accessible to pipetting arm
.Lids are not shown in the Preview.
There is no indication of lid handling in the Fluent commands generated — FluentControl does it implicitly based on the
lid
parameter of the source and destination carriers of a plate movement.Lidding and delidding is intrinsically tied to the movement of plates.