1-24 Echo Liquid Handler User Manual
The Echo liquid handler is a client/server system. The “client” is the external
workstation that contains the user interface software to define plate and
protocol information. The “server” is the controller that runs the
instrument motors and sensors. Each subsystem is independent, with its
own system checks. This architecture allows the Echo liquid handler to be
commanded by multiple clients to run concurrent operations, yet ensure
that each operation is “safe” with respect to each other.
For example, one user might command the Echo liquid handler to do a
plate survey, then a liquid transfer protocol. During the source plate survey,
another user might command the Echo liquid handler to extend the source
plate. The plate survey that is in progress will continue to completion, then
extend the source plate. Thus, while the Echo liquid handler guarantees
"safe" operation, it cannot prevent the commands of one user interfering
with those of a second user.Therefore, it is the responsibility of the users to
coordinate their actions to ensure the proper fulfillment of a transfer
protocol.
Also, if more than one user creates, edits, or deletes fluid transfer protocol
definitions or destination microplate definitions, then there must be
communication between users to ensure that the definitions are consistent
with the protocols.
Users should be aware of the following considerations with the client/
server architecture.
An Echo liquid handler is not limited to a single client. One or more
clients can either monitor its status or command it to execute its
functions.
Uncoordinated clients could cause out-of-order execution that
interferes with other users' protocols. For example, client “A” could
delete or edit a protocol or destination microplate definition created
by client “B.” An edited protocol definition would only be detected if
the original definition was stored on client “B” and compared to the
definition in the database.
To Next Page
Loading...
