PathMaster-REV-L-4.5-1.pdf - 第31页
Machine Operati on Manual Revision L / February 2020 Page 31 of 200 Save for Part Manager When you s elect Save or Save As , t he curre nt proje ct is saved and exp orted to a fold er hierarchy o n the hard d rive. The d…
Machine Operation Manual
Revision L /
February 2020
Page 30 of 200
Database Restoration
To restore the PathMaster® database:
1. Select the
File -> Database -> Restore
option from the main menu.
2. You can restore a *.bck (standard backup) or *.abck (automatic backup) file with this
option.
WARNING! A restore PathMaster® database will completely overwrite all data prior to the
restore. Do not restore partial data with a database restore procedure.
3. When the file dialog box opens, select the location and file you wish to restore.
4. Select the “Open” button.
5. When the “Restore Successful” message displays, select the “OK” button.
6. Restart PathMaster®.
Restoring a database from a PathMaster® 2.3, 3.0 and 4.0
1. Follow the steps outlined above. Upon restart, you will be prompted indicating that
the database has been upgraded.
2. Use the above instructions to restore the database.
Restoring a database from prior to PathMaster® 2.3
It is not possible to restore a database to PathMaster
®
4.1 from versions prior to
PathMaster
®
2.3. Any database from a version of PathMaster
®
before 2.3 does not meet the
minimum requirements for the restore. Contact PVA if a restore is necessary.
Path Programs
A path program is a collection of individual path segments that make up a dispense
program. Path programs are made up of any combination of programming functions. Each
path program can have a unique name of 12 characters or less. The path program name is
shown on the operator interface while the path runs.
Project Files
PathMaster® project files can contain up to 30 individual path programs. A downloaded
project file has all 30 storage areas, even if some are empty. Empty areas will do nothing if
selected to run.
Machine Operation Manual
Revision L /
February 2020
Page 31 of 200
Save for Part Manager
When you select Save or Save As, the current project is saved and exported to a folder
hierarchy on the hard drive. The default location for the folder is in the ‘PathMaster.ini’ file.
PathMaster® can be configured to prompt the user for the folder location.
Example Save (for part manager) folder hierarchy: Project name: MyProject
• Select File -> Save or File-> Save As
A folder called MyProject (Project name) is created in the default project file output
location (C:\Program Files\PVA\PathMaster\Projects). In the MyProjects Folder, 30
individual files are created, one for each program in the project. The files names of the 30
program match the program name. If the program name contains characters that are not
allowed in file names, the character is replaced with the character ‘@’.
Figure 17: Save for Part Manager
INI Settings for ‘Save For Part Manager’
• Default folder location for Save For Part Manager: ProjectFileOutput=C:\Program
Files\PVA\PathMaster\Projects
• Set if the default location is used or if the user is prompted to select a location:
UseDefaultProjectFileOutput=1
CAUTION: The Path specified in the ‘[General]’ section of the ‘PathMaster.ini’ file with the
‘ProjectFileOutput’ key is for PathMaster® use only. This folder is an extension of the
PathMaster® database, for use with PVAPortal’s dependency, PartManager. Any external
data written to this folder or its children will be overwritten by PathMaster®!
Machine Operation Manual
Revision L /
February 2020
Page 32 of 200
Machine Program Transport
PathMaster 4.4 can import data from previous versions of PathMaster, but previous
versions of PathMaster cannot import data from PathMaster 4.4 or newer. This includes all
types of data imports (Machine, Program, Project, Subroutine).
WARNING: Tool Offsets and Workspace Reference positions must be correctly configured
on both the source and destination machine before a Machine Program Transport is done.
Refer to sections 6.4.7 and 6.6.5 for more information.
A machine program transport requires a transfer file (.tfr) from the source machine to be
imported onto the destination machine.
The Transfer file contains program data, Workspace Reference Position and the Z
component of Tool Offsets. The Import Machine Transfer function compares the source
machine Workspace Reference position (X,Y only) to the destination machine Workspace
Reference position (X,Y) and finds an appropriate global offset for the destination machine
programs. The Z component of tool offsets are also compared to find an appropriate Z
offset for each tool on the destination machine.
NOTE: When the configuration of systems is planned for Machine Program Transport, the
systems should be matched mechanically as much as possible. The Tool ID’s should also be
the same from one system to another. For example, if a dispense valve on the source
machine is the first virtual tool (TL_ID 1) and a spray valve is the second virtual tool (TL_ID
2), the destination machine must have the same tool relationship (1st tool = TL_ID 1, 2nd
tool = TL_ID 2), etc.