Software Manual Freedom EVOware Standard 2.3 Freedom ...

C - Validation of Freedom EVOware Applications
Important Points to Check When Validating Freedom EVOware Applications
initialization errors. If error messages are found, the cause of the error must
be remedied before you start pipetting.
• Before you pipette using real samples, test run the script or process to make
sure that:
– Pipetting takes place at the intended positions on the worktable (e.g.
correct microplate, correct well).
– The correct volumes of liquid are pipetted.
– Pipetting takes place in the correct sequence as required by the
application.
• Freedom EVOware chooses multi-dispensing mode automatically if the
pipetting script specifies an aspirate command followed by several
consecutive dispense commands. In turn, this influences the liquid class
parameters which are used. The decision between single dispensing mode
and multi-dispensing mode is made when the script is validated and not when
the script is run. Scripts are validated when they are modified and also when
they are opened for running without being modified. Validation is done using
default values for the variables (see 11.4.2.1 “Checking the Pipetting Script for
Errors”, 11-5).
If the number of consecutive dispense commands is controlled by a variable
whose value can change during runtime, it is recommended to design the
script with branches or separate groups of commands for single-pipetting
mode (one dispense operation) and multi-pipetting mode (more than one
dispense operation). This ensures that the correct pipetting mode and liquid
class parameters will be chosen at runtime.
• If your script or process uses liquid level detection (e.g. the chosen liquid
class uses liquid level detection or the script or process uses the Detect Liquid
command), make sure that liquid detection is working correctly. The capacitive
detection system is not suitable for all liquid types (e.g. liquids with foam, nonconductive
liquids). Liquid detection can not be used if you are using septum
piercing. To ensure accurate liquid detection, make sure that the labware is
correctly seated on the carriers.
• If your script or process sends firmware commands to the pipetting instrument
or to other devices, make sure that the correct firmware commands have been
specified and that they initiate the intended actions. Sending the wrong
commands can cause invalid results, damage the instrument or objects in its
workspace, hurt yourself or other people and can cause the script or process
to produce invalid results.
• If your script or process uses a microplate reader, check the results (output
data) from the reader to make sure that they are plausible.
• When setting up an assay for a liquid which can clot, make sure that clot
detection is enabled in the liquid classes which are used to handle the liquid.
Refer to the Good Usage information in the Operating Manual for the pipetting
instrument for additional recommendations.
• When setting up an assay which uses a trough (container for a reagent liquid),
make sure that the liquid classes which are used for aspirating from the trough
are configured to immerse the tips in the liquid by at least 3 mm.
• Appropriate tip washing actions must be provided in the script or process to
avoid cross-contamination of samples and/or reagents. Disposable tips can
also be used to avoid cross-contamination of samples and/or reagents.
Design and test run the script or process to make sure that crosscontamination
will not take place.
• If your script or process uses a shaker, make sure that the shaker parameters
(e.g. shaking time, shaking frequency) have been configured correctly and
that the shaker operates as intended.
C - 2 Freedom EVOware Software Manual, 393172, en, V2.3