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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 6: Running a print job<br />

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

133<br />

Related information<br />

For more information about...<br />

See...<br />

Creating constants “Creating a constant” on page 119.<br />

Mechanically setting top and<br />

bottom positions of the plate stage<br />

“About the vertical plate stage<br />

positions” on page 75<br />

Creating a print job<br />

Introduction<br />

This topic defines print jobs, and describes how to create, save and<br />

open them.<br />

About print jobs<br />

A print job sets which schemas will be used to label which sides of the<br />

plate during a batch run. As each schema defines the labels printed on<br />

one side, you can print different labels on different sides of the plate.<br />

You can label more than one type of plate in a print job, even if they<br />

have different heights. However, if they do have heights that require<br />

different drop stage positions, you will need to use a data source in the<br />

schema. The data source will control the drop stage parameter during<br />

the print job.<br />

Before you start<br />

Before defining a print job, you must have:<br />

❑ Created one or more schemas<br />

❑ Created the label format for the print job<br />

❑ Started PlateTag<br />

Creating a print job<br />

To create a print job:<br />

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

Any existing schemas listed in the Data Schema Selection table are<br />

cleared.<br />

2. In the Device Selection group box, select the profile for the VCode<br />

that you want to use to do the printing.

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

Saved successfully!

Ooh no, something went wrong!