17.04.2014 Views

Microplate Barcode Labeler User Guide - Agilent Technologies

Microplate Barcode Labeler User Guide - Agilent Technologies

Microplate Barcode Labeler User Guide - Agilent Technologies

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 6: Running a print job<br />

VCode <strong>User</strong> <strong>Guide</strong><br />

135<br />

Starting a production labelling run<br />

Introduction<br />

After the VCode is completely set up and a print job has been created,<br />

you can perform a production labelling run in which a batch of plates is<br />

labelled on one or more sides.<br />

This topic describes how to open and start a print job.<br />

Before you start<br />

Before starting a production printing job it is a good idea to perform a<br />

test print to make sure that:<br />

❑ All of the data will fit on a label<br />

❑ The text can be read by a person<br />

❑ The bar code can be read by a bar code reader<br />

If PlateTag is not already running, you will also need to start it.<br />

Opening a print job<br />

You can have one print job open at a time.<br />

To open a print job:<br />

1. In PlateTag, navigate to Jobs > Open.<br />

Starting a print job<br />

To start a print job:<br />

1. In the Print Job tab of PlateTag, click Start job.<br />

2. If your schemas do not use a data source, input the correct number<br />

of plates for the run in the Job Size Request dialog box.<br />

If your schemas use a data source, PlateTag assumes that the number<br />

of plates that you want to label is the same as the number of data<br />

rows in the data source.<br />

3. Place a plate on the plate stage and press the green button.<br />

One or more labels are printed and applied to the plate.<br />

Click the Print Job tab to see the progress of batch labelling<br />

operation.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!