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 5: Creating label formats for printing<br />

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

97<br />

Magnification and<br />

position<br />

If after increasing the magnification or size of the font a field does not<br />

print, check where the field is positioned on the label. The field may<br />

now be positioned off the edge of the label.<br />

As the magnification and size of the font increases, the Y-value in the<br />

label format must increase for you to be able to see it.<br />

Next step<br />

The next step in the workflow for designing and using a new label format<br />

is “Uploading and saving a label format” on page 98.<br />

After uploading the label format, make sure that you test the format<br />

before using it for a batch run.<br />

!! IMPORTANT !! The printer does not always scale bar codes and<br />

fonts consistently. If you change a text field’s magnification, always<br />

perform a test print to make sure that you can still read the text. If<br />

you change a bar code field’s magnification, perform a test read of<br />

the bar code.<br />

Related information<br />

For more information about...<br />

The overall process of designing a<br />

bar code label format<br />

Opening VCode Diagnostics<br />

Performing a test print<br />

Performing a test bar code read<br />

See...<br />

“Workflow for designing a label format”<br />

on page 87<br />

“Starting VCode Diagnostics” on<br />

page 62<br />

“About test printing and applying” on<br />

page 99<br />

“Testing the reader using VCode<br />

Diagnostics” on page 147

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

Saved successfully!

Ooh no, something went wrong!