Exporting and importing protocols and associated components

Reasons for exporting and importing files

You can export and import protocols and associated components to transport protocols between computers, back up and recover protocols and associated files, and to facilitate troubleshooting problems with protocols and other files when seeking assistance from Automation Solutions Technical Support.

You can export or import the following:

•	Protocol file

•

Form file

•	Runset file

•	Device file, including the device profile and teachpoint file

•	Macros used in the exported protocol or the entire macro library (.mlb file)

•	Labware definitions

•	Liquid classes

•	Pipette techniques

•	Hit-picking files

•	Plate map files

•	Barcode files

•	Error library

•

Log files

Exporting files

You can export files if you have administrator, technician, or operator privileges.

To export the system files:

1	In the VWorks window, select File > Export. The Export Wizard dialog box opens.

 

2	Follow the instructions in the wizard to do the following:

a	Specify the location and name of the .vzp file, which contains the exported and compressed files.

b	Select the protocol, runset, or form you want to export. You do not need to select the associated device file and other files. The software automatically exports all the associated files with the protocol.

c

Optional. If a form (.VWForm file) is specified in the protocol’s options, verify the Include all Form files specified in Protocol options is selected (default) to include the form in the export. If you do not want to include the form, clear the Include all Form files specified in Protocol options check box.

IMPORTANT Any custom image files that you provide for the form, must be in the same folder as the .VWForm file that you are exporting.

d	Optional. If the protocol is associated with barcode files, select Export barcode files.

e	Optional. If the protocol is associated with an error library file, select Export error library file.

f	Optional. If the protocol is associated with a plate map database, select Export plate map database.

g	Optional. If the protocol contains task macros that have the same names as macros in the Available Macros area in the VWorks window (macro library), do one of the following:

•	Select the Export macro library file check box to export the macro library information for those macros from the protocol that are also in the macro library. After the .vzp file is imported, this set of macros can be added to the macro library on the destination computer.

•	Clear the Export macro library file check box to export the protocol version of the macros only. After the .vzp file is imported, the macros will appear in the protocol only.

Note: The Export macro library file check box is available only for the macros in the protocol that are also in the macro library. If you want to export the entire macro library, you can attach the .mlb file on the Additional files list page of the Export Wizard.

h	Select the log files you want to include.

 

3	When you are finished, click Finish. The .vzp file appears in the specified location.

You can move the .vzp file to another computer and import it into the VWorks software, or send the .vzp file to Automation Solutions Technical Support to report a problem.

Importing files

You can import files if you have administrator or technician privileges.

IMPORTANT Close any open protocols before you import a protocol.

To import the system files:

1	In the VWorks window, select File > Import. A message dialog box opens and asks if you want to back up the existing labware definitions, liquid classes, pipette techniques, and plate-map databases.

2	Do one of the following:

•	Click Yes to back up the information. In the Backup dialog box, type a name for the backup file (.vbk), and then click OK. The .vbk file is created and stored in the …\VWorks\backup folder.

•	Click No to start the import process.

The Import Wizard dialog box opens.

 

3	Follow the instructions in the wizard to:

a	Select the .vzp file you want to import. The .vzp file contains the protocol and associated files.

b	Select the location to store the imported protocol file, device file, barcode files, and runset file, if applicable.

c	Optional. Select the option to import the associated plate-map database.

d	Select the labware entries and classes you want to import. If a labware entry or class has the same name as an existing entry or class in the database, you have the following options:

–	Labware classes only. Append new labware entries to the existing labware class.

–	Replace existing labware entries or classes with newly imported entries and classes.

 

CAUTION Protocols that rely on existing labware entries or classes might be affected.

–

Create a new file for the newly imported labware entries and classes. You can choose to append the import date on the name of either the new labware file or the existing labware file. The imported protocol will use the imported labware definitions. When running existing protocols, you have to use the old labware file.

e	Select the pipette technique files.

f	Select the hit-picking input and format files.

g	Select the device profiles.

h	Select the error handlers and log files.

i	If macros were associated with the exported protocol, review the list of exported macros. An asterisk highlights any macros that are already in the VWorks macro library on the destination computer.

You can choose to overwrite the macros of the same name or append the import date on the name of the imported macros.

4	When you are finished, click Finish. The files are imported in the specified locations. If you selected the option, the imported protocol opens in the VWorks window.

Related information

 

For information about...	See...
Contacting Agilent Technologies and reporting problems	Reporting problems
VWorks software components: protocol, device file, and so on	Relationship of VWorks components
Viewing logs	Viewing logs
Backing up system files	Backing up and restoring files
Macros in protocols	Using macros to create protocols
Protocol forms	Creating protocol forms for operators