Microlab
®
STAR User Manual
Page 44 of 225 610766/02
³6DYH$V´RU6DYLQJ0HWKRGVDQG'HFN/D\RXWVXQGHU'LIIHUHQW1DPHV
Due to the QQ relation between deck layouts and methods, the “Save as” option needs to be
used in the following way:
To save a method under a different name, still referring to the old deck layout:
• Select “Save As” in the method editor and save the old method A under a new name B.
The new method B is still linked to the old deck layout A.
To save a method and the corresponding deck layout under a new name:
• Start the Method Editor as the (first opened) master editor.
• Select “Save As” to save method A under the new name method B.
• Start the Deck Editor to save deck layout A under the new name deck layout B. Close the
Deck Layout Editor.
• Link method B to deck layout B (Methods->Instruments). Save method B.
6WUXFWXUHRIWKH8VHU6RIWZDUH
The User Software consists of a set of modules and tools (programs) which work together.
These modules and tools are grouped into a general (instrument-independent) and a specific
(instrument-dependent) group. Given that structure, a system with different HAMILTON
instruments (even non-HAMILTON instruments, suitably adapted) can be controlled and
operated in the same manner, in the same environment and at the same time. The general
modules get all the specific information they need about instruments (such as pipetting steps,
or information about the probe head) from the instrument-dependent modules.
The general modules with a common “look and feel” for all HAMILTON instruments include:
• Deck layout editor (for mapping the position of labware on the deck)
• Method editor (for programming methods)
• Sequence editor (for defining pipetting sequences)
• Labware editor (for defining custom labware to be used in deck layouts)
• HSL Method editor (for programming methods using text entry mode)
• Run execution (for running methods on the instrument).
The general tools include:
• Version info.
The Microlab STAR-specific editors include:
• Liquid Editor (for defining liquid classes)
• Configuration Editor (for configuring the User Software to a particular instrument)
The Graphical Method Editor lets the user write methods in a graphical, syntax-free
environment. Technically, this editor is a code generator producing a low-level code which is
then interpreted by the run control. This low level code is called HSL (Hamilton S
tandard
Language), because it provides a common programming approach for all Hamilton
instruments. HSL can be accessed directly using the HSL Method Editor. HSL is a syntax-
dependent language that offers even more flexibility than the Graphical Method Editor. The
instrument-specific steps (e.g. aspiration, dispense - see below) are the same for the
To Next Page
Loading...
