Professional Documents
Culture Documents
Ig51580 PDF
Ig51580 PDF
Ig51580 PDF
Version 11.6.SP1
Windows 2000 and Windows XP
PLEASE NOTE:
All rights reserved. No part of this document may be reproduced, stored in a retrieval
system or transmitted, in any form or by any means, electronic, mechanical,
photocopying, recording or otherwise, without prior written permission of AVEVA
Solutions.
The software programs described in this document are confidential information and
proprietary products of AVEVA Solutions or its licensors.
For details of AVEVA's worldwide sales and support offices, see our website at
http://www.aveva.com
AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge CB3 0HB, UK
Revision History
Date
Version
Notes
Sept 2004
11.6
Updated:
Hardware recommendation; Upgrading; Licensing;
AutoDRAFT chapter (versions supported)
New:
Information on .NET and its effect on PDMS installation;
Background Process Manager
Minor corrections and updates
Added Section 47 Running PDMS in batch
May 2005
11.6.SP1
Updated
Contents
1
Introduction.................................................................................................... 1-1
1.1
1.2
3.2
3.3
3.4
5.2
5.3
6
Hardware............................................................................................. 2-1
2.1.1
Graphics Cards ...................................................................... 2-1
Software and Configuration ............................................................... 2-2
contents-i
Contents
6.2
6.3
7
7.2
8.5
8.6
10
Troubleshooting...........................................................................................10-1
10.1
10.2
10.3
10.4
11
General...............................................................................................10-1
License Manager Errors ....................................................................10-1
Entering PDMS .................................................................................10-2
Problems with Graphics ....................................................................10-3
11.4
contents-ii
Overview ............................................................................................11-1
PDMSEXE..........................................................................................11-1
GUI module structure .......................................................................11-1
11.3.1 Wrappers ..............................................................................11-2
11.3.2 .NET Loading rules..............................................................11-2
11.3.3 Win32 DLLs .........................................................................11-3
Components .......................................................................................11-3
11.4.1 PDMSEXE directory ............................................................11-3
11.4.2 PDMSEXE/Design subdirectory ..........................................11-5
11.4.3 PDMSEXE/Draft subdirectory ............................................11-5
VANTAGE PDMS Installation Guide
Version 11.6.SP1
Contents
11.5
12
contents-iii
Introduction
This guide explains how to install and set up PDMS Version 11.6.SP1 on
a workstation running the Microsoft Windows 2000 or Windows XP
operating system (hereafter referred to jointly as 'Windows'). Local
Administrator rights are required to perform the installation.
This guide assumes you are familiar with the concepts of folder/file
hierarchies for storing data on disks and with basic Windows
terminology and commands. If you are not, you may also need to refer to
your operating system documentation while you carry out the
installation.
The guide also assumes that you have already gained access to the
PDMS installation files via a CD, from the AVEVA Web site, or by some
other route.
1-1
Introduction
Global
Model Management
1-2
2.1
Hardware
Processor
Memory
256 MB minimum,
512 MB, or more, highly recommended.
Graphics Card
Display
Storage
Approximately 670 MB
- see AVEVA web-site for details.
CD drive
Mouse
2.1.1
Graphics Cards
2-1
2.2
PDMS 11.6 will run on Windows XP SP2, but requires changes to the default settings. The Internet
Connection Firewall (ICF) should be turned off or configured to ensure access to the database server.
In addition, Group Policy changes (which alter the registry) are required for VANTAGE Plant Design
Global to ensure that RPC requests do not require authentication. Details are given in the Global
Installation Guide.
2-2
Installing PDMS
3.1 Basic Installation
Local Administrator rights are normally required to install PDMS.
1.
2.
3.
On the File Download form, select Run this program from its current
location (IE 5.0) or Open (IE 5.5 or later) to install the program files
directly from their current location onto your hard disk. Select Yes
on the Security Warning query about an Authenticode signature.
4.
This starts the InstallShield Wizard, which will lead you through
the rest of the installation process.
It is recommended that you use the default settings for folder paths etc.
unless you have good reasons for doing otherwise. You must not use
embedded spaces in folder path names.
The process needs at least 670MB of free disk space for a full installation
of all options. InstallShield checks that there is enough space available
before it starts, and warns you if there is not.
3-1
Installing PDMS
3.1.1
NOTE:
Uninstalling PDMS will not uninstall Microsofts .NET Framework:
this must be removed separately if required.
3-2
Installing PDMS
3-3
Installing PDMS
3-4
Check the settings for your graphics board: See Section 4.2.
You can then run PDMS by clicking on the PDMS shortcut or icon,
which will set up the remaining environment variables required.
4-1
4-2
To set automatically:
Windows 2000 and Windows XP
To check the Registry setting, you will need to use the FLEXMAN utility
lmpath status
744@licserv
4-3
Executable folder
C:\AVEVA\pdms11.6.SP1
PDMSEXEMAIN
CADCENTRE_LICENSE_FILE
License file
PMLLIB
PDMSDFLTS
PDMSPLOTS
PLOTCADC
PDMSHELPDIR
4-4
PDMSWK
PDMSUSER
PDMSREPDIR
PDMSDFLTS
but they should have their own local defaults area. This is
achieved by setting a PDMSDFLTS search path, e.g.
C:\USERDFLTS C:\AVEVA\pdms11.6.SP1\pdmsui\dflts
For each PDMS project, four more environment variables must be set.
For example, for a project ABC:
ABC000
ABCISO
ABCMAC
ABCPIC
Edit the system variable Path to add the PDMS folder (for example,
C:\AVEVA\pdms11.6.SP1) to the list of folders in the Path
variable.
Once the Path variable includes the pdms11.6.SP1 folder, you can run
PDMS by typing pdms at a command prompt.
4-5
You can create a shortcut on your desktop to run your batch file.
With the cursor in the desktop area, click with the right-hand
button and select New>Shortcut. This shows a sequence of dialogs to
help you create the shortcut. Type in the location of pdms.bat, for
example:
C:\AVEVA\pdms11.6.SP1\pdms.bat
then press Next and give the shortcut a name.
Press Finish.
You should now be able to double-click on the shortcut icon to enter
PDMS.
Otherwise, navigate to the folder where the batch file is stored and
type pdms or pdms.bat.
You can set up your own batch files to run PDMS. For example, you may
wish to run design checking utilities every night, or update batches of
drawings overnight.
Begin by creating a batch file, for example, runpdmsmacro.bat.
Type the following line into this file:
C:\AVEVA\pdms11.6.SP1\pdms.bat TTY SAM SYSTEM/XXXXXX /STRUC
$M/mymacrofile
Where:
TTY tells PDMS not to start the PDMS GUI. This gives command line
only operation.
4-6
This will start PDMS, then wait until it has finished before resuming the
script.
The VANTAGE PDMS MONITOR Reference Manual provides more
details on running PDMS batch programs.
4.8 Plotting
To plot in a Windows environment, we recommend that you use the
plotcadc.bat file supplied in the pdms11.6.SP1 folder. Note that you may
have to modify the plotcadc.bat file to suit your local printer installation.
The Network Plotter must be mapped using the NET USE command. See
your network documentation for more information.
To run the plotcadc.bat file, give a command in the format:
C:\AVEVA\pdms11.6.SP1\plotcadc.bat plotfile format printer
options
4-7
Where options are the AVEVA PLOT utility options, and may be omitted.
See the PLOT User Guide for more information. Note that the options
must be enclosed in quotes.
For example:
plotcadc.bat c:\pdms\plot1 ps \\ntserver\NTPostScript
plotcadc.bat c:\pdms\plot1 hpgl \\ntserver\NThpgl 'CE=Y'
4-8
Language Support
By default, your PDMS project can use any language whose characters
are contained within the Latin-1 character set. The Languages covered
by the Latin-1 character set a listed in the table below. If you want to use
any of the other, non-Latin-1 languages supported by PDMS, it is
necessary to configure your PDMS project and the Windows operating
system. This chapter describes how to use PDMS on Windows 2000 and
Windows XP Professional in each of the supported language groups:
Latin-1
Latin-2
Latin-Cyrillic
Far Eastern
Supported languages
Name
Description
Languages covered
Latin 1
Latin 2
Latin Cyrillic
Bulgarian, Byelorussian,
English, Macedonian, SerboCroatian, Ukrainian, Russian
Far Eastern
PDMS does not support any other language character set, nor does it
support the mixing of any of the above, except for mixing one Far
Eastern language with English.
5-1
Language Support
Windows 2000
5.1.2
Windows XP
5-2
Language Support
Languages covered
(default)
The corresponding font family must be selected for Draft and Isodraft
drawings. Use Project>Font Families and select the Font Type appropriate
for you chosen language.
For details, see the VANTAGE PDMS ADMIN User Guide and
VANTAGE PDMS ADMIN Command Reference Manual.
5-3
Language Support
Before you use PDMS, you must set the environment variable
CADC_LANG as follows:
CADC_LANG=Japanese
Kanji
CADC_LANG=Korean
CADC_LANG=Chinese
Simplified Chinese
CADC_LANG= TChinese
Traditional Chinese
In PDMS ADMIN, you must specify the multibyte character set for each
project by using the command corresponding to your required language:
PROJECT MBCHARSET JAP
PROJECT MBCHARSET KOR FILE /<font filename>
PROJECT MBCHARSET CHI
Simplified Chinese
5-4
Due to the way in which PDMS parses its command lines, this format is
also recommended for use with filenames containing Asian characters.
6-1
6-2
PDMS Projects
7.1 The Sample Project
PDMS is supplied with a sample project, which can be used in several
ways:
It provides you with starting points for the tutorials in the following
manuals:
Pipework Design Using PDMS
Pipework Spooling Using PDMS
Structural Design Using PDMS
Industrial Building Design Using PDMS
Support Design Using PDMS
HVAC Design Using PDMS
Reporting from PDMS
Drawing Production Using PDMS
7.1.1
The sample project is loaded automatically when you install PDMS. You
should copy the sample project to your user area and run it as supplied.
7-1
PDMS Projects
The project files are held in two directories: sam000 holds all design
data and catalogue data; sampic holds the DRAFT picture libraries.
7.1.2
Free User
Username/password
CATS
DEMO
EQUI
HANGER
HVAC
PIPE
SAMPLE
STRUC
USERA
USERB
USERC
USERD
USERE
USERF
USERG
CATS/CATS
DEMO/DEMO
EQUI/EQUI
HANGER/HANGER
HVAC/HVAC
PIPE/PIPE
SAMPLE/SAMPLE
STRUC/STRUC
USERA/A
USERB/B
USERCC
USERD/D
USERE/E
USERF/F
USERG/G
7-2
PDMS Projects
7.1.3
This section assumes that you are already familiar with PDMS
databases.
The sample project contains the following MDBs which can be used for
demonstration or training purposes:
CATS
DEMO
A demonstration MDB.
EQUI
HANGER
HVAC
MASTER
SAMPLE
STRUC
TRAINA to
TRAING
7-3
PDMS Projects
md
md
md
md
xyz000
xyzpic
xyziso
xyzmac
XYZ000=pathname\xyz000
XYZPIC=pathname\xyzpic
XYZISO=pathname\xyziso
XYZMAC=pathname\xyzmac
Note: Users converting from UNIX should note that there is no direct
equivalent of the .cshrc file in which these variables can be set.
Use the 'Make PDMS project' icon supplied to start the PDMS Make
program, then enter:
XYZ
$m/%PDMSEXE%/makemac.mac
FINISH
Note: Users converting from UNIX should note that the makemac.mac
file is the same as on UNIX. The executable for each module is
also named identically to that on UNIX, e.g. DESIGN runs
%PDMSEXE%/des. The extension '.exe' needed by Windows is
added automatically.
7.2.1
You can add databases from the sample projects SAM and MAS to your
own projects from within PDMS ADMIN, using the Install options on the
main menu bar. Note that these options are only available if you have
the project environment variables for SAM and MAS set.
Note on DRAFT Libraries:
You must have DRAFT libraries available in your current project before
you can enter the module. You may find it convenient to install the
libraries supplied by AVEVA in the MAS project (using the Install
options), even if you wish to create your own libraries for the project.
7-4
Installing AutoDRAFT
This chapter explains the steps needed to install and configure
AutoDRAFT.
AutoDRAFT may be run in stand-alone mode or it may be run from
PDMS DRAFT or ISODRAFT. You can use the adraftde, adraftbe and
adraftse scripts as described in the VANTAGE PDMS AutoDRAFT User
Guide. The DRAFT and ISODRAFT applicationware generates interface
files for AutoCAD, which are then used by the scripts.
AutoDRAFT generates interface files for DRAFT, which can be imported
using the DRAFT applicationware.
8.1 Compatibility
The version of AutoDRAFT released with PDMS 11.6.SP1 is compatible
with AutoCAD Releases 2002 and 2004.
8-1
Installing AutoDRAFT
autodraftACAD
autodraftfonts
autodraftACADsource
Installing AutoDRAFT
8.4.1
AutoCAD R2002
set PDMS_ACAD=2002
set PDMS_ACAD_PATH=pathname for AutoCAD R2002 files
e.g. C:\Program Files\Acad2002;C:\Program Files\Common
Files\Autodesk Shared
set ACAD_VERSION=%PDMS_ACAD%
set path=location of autodraftACAD directory;%PDMS_ACAD_PATH%;
%path%
Before running AutoDRAFT, you need to run AutoCAD R2002 and add
the following as file paths:
Location of autodraftACAD directory
Location of autodraftACADsource directory
Location of autodraftfonts directory
8.4.2
AutoCAD R2004
set PDMS_ACAD=2004
set PDMS_ACAD_PATH=pathname for AutoCAD R2004 files
e.g. C:\Program Files\Acad2004;C:\Program Files\Common
Files\Autodesk Shared
set ACAD_VERSION=%PDMS_ACAD%
set path=location of autodraftACAD directory;%PDMS_ACAD_PATH%;
%path%
Before running AutoDRAFT, you need to run AutoCAD R2004 and add
the following as file paths:
Location of autodraftACAD directory
Location of autodraftACADsource directory
Location of autodraftfonts directory
8-3
Installing AutoDRAFT
8-4
9-1
9-2
10
Troubleshooting
Here are some suggestions about solving some problems you may
encounter when using PDMS under Windows.
10.1 General
Error:
Explanation:
Error:
Explanation:
Error:
Explanation:
When you start up lmgrd it says <time> (lmgrd) Can't make folder
C:\FLEXlm, errno: 2 No such file or folder, etc.
There is no C: drive for the license manager to write to. As the System
Administrator or a Power User, you need to make a shared disk called
C:. This can be done on a networked or non-networked computer.
Within the Windows Explorers File menu, create a new folder (e.g.
D:\C_drive) and make it current. Select File>Properties and select
the Share tab. Click on the Shared As: radio button and then click OK.
Then from the Tools menu select Map Network Drive. Select C: from
the Drive: drop-down list in the displayed form and type
\\hostname\C_drive
in the Path box. Then click on OK. (C:) should now appear in the list of
available drives in Explorer.
<time> (lmgrd) "<host>": Not a valid server hostname, exiting.
The hostname used by AVEVA to create the license file does not
correspond with the computer on which you are running PDMS. The
hostname comes from the variable COMPUTERNAME, which you can
10-1
Troubleshooting
Error:
Explanation:
Error:
Explanation:
Error:
Solution:
Error:
Explanation:
10-2
Troubleshooting
Error:
Explanation:
Error:
Solution:
Incorrect colours.
Check the setting of your Display. The colour resolution should be set to
True Colour or 16.7 million colours.
Error:
Solution:
10-3
Troubleshooting
10-4
11
From PDMS 11.6.SP1, the GUI uses the Microsoft .NET environment including
the latest WinForms based user interface components. Using this state-of-theart technology enables docking forms and toolbars in PDMS and provides a
robust foundation for the future provision of standard application programming
interfaces.
This does affect the way PDMS is installed: this section gives a brief overview
and the following one outlines how to troubleshoot the installation.
11.1
Overview
This section describes the overall structure and components of the PDMS .NET
installation, and the environment necessary to run it. Each PDMS GUI module
now consists of a thin .NET exe, a .NET Wrapper DLL and a Win32 DLL plus
some other shared components including 3rd party controls from Infragistics.
The .NET components are private assemblies installed under the root directory
%PDMSEXE%.
11.2
PDMSEXE
11.3
Each GUI module is structured in the same way. For Design the structure looks
like this
11-1
des.exe
Wrappers.dll
des.dll
where des.exe and des.dll live in the directory %PDMSEXE% and Wrappers.dll
lives in the Design subdirectory below %PDMSEXE%. So, when running a PDMS
GUI module %PDMSEXE% is used to locate the executable, .NET loading rules
are used to load Wrappers.dll and Win32 DLL loading rules are used to load
des.dll (and other Win32 DLLs on which des.dll depends).
11.3.1
Wrappers
For each GUI module (Design, Draft, Admin, Isodraft and Monitor) there is a
Wrappers.dll in a subdirectory with the same name as the module. Each
Wrapper.dll has a dynamic link to the appropriate Win32 DLL for that module.
.NET loading rules are used to load the appropriate Wrappers.dll for a given
module. So, when running des.exe, the version of Wrappers.dll linked with
des.dll will be loaded. Design and Draft subdirectories also contain a
drawlistWrapper dll which is used by the Drawlist add-in.
11.3.2
All the .NET assemblies are Private assemblies and are installed under
%PDMSEXE% (Assembly Base directory) or a subdirectory below. .NET loads
private assemblies from the base directory of the application. If it cant find the
private assembly here it uses the applications configuration file called
<module>.exe.config to see whether it contains any path hints. Path hints are
stored in the <probing> element. So, for example, des.exe.config has the
following probing path <probing privatePath="Design" />. This means that
Wrappers.dll is loaded from the subdirectory Design below the application
directory.
11-2
11.3.3
Win32 DLLs
Each Wrappers.dll depends on the given modules Win32 DLL, e.g. Designs
Wrappers.dll found in the Design subdirectory depends on des.dll. Win32 DLL
loading rules apply here. These are:
The directory from which the importing component loaded. (e.g. the
Design subdirectory where Wrappers.dll is loaded)
Since the module DLL does not live in the same directory as the Wrappers.dll
then unless you are running from %PDMSEXE%, your %PATH% will be used to
locate the module DLL. (The Wrappers.dll subdirectory is the directory which is
first searched for all the Win32 DLLs on which Wrappers depends i.e.
<module>.dll, sglNet.dll, udDNet.dll, )
11.4
Components
11.4.1
PDMSEXE directory
Design/Spooler
des.exe, des.dll, des.exe.config, des.exe.manifest, DesignAddins.xml,
SpoolerAddins.xml
Draft
dra.exe, dra.dll, dra.exe.config, dra.exe.manifest, DraftAddins.xml
11-3
Monitor
mon.exe, mon.dll, mon.exe.config, mon.exe.manifest
Isodraft
iss.exe, iss.dll, iss.exe.config, iss.exe.manifest, IsodraftAddins.xml
Admin
adm.exe, adm.dll, adm.exe.config, adm.exe.manifest
Shared
Depends.dll, DrawList.dll, DrawListAddin.dll, ExplorerAddin.dll,
ExplorerControl.dll, ForeignLanguage.dll, HistoryAddIn.dll, MyDataAddIn.dll,
ReferenceListAddin.dll, PDMSCommands.dll, PDMSFilters.dll,
PDMSResources.dll, PDMSResources.resources, StartUp.dll,
ApplicationFramework.dll, udNet.dll, DruidNet.dll
Infragistics
This is a third-party GUI tool-kit:
Infragistics.Shared.v3.dll, Infragistics.Win.UltraWinDock.v3.dll,
Infragistics.Win.UltraWinExplorerBar.v3.dll,
Infragistics.Win.UltraWinGrid.v3.dll,
Infragistics.Win.UltraWinStatusBar.v3.dll,
Infragistics.Win.UltraWinTabbedMdi.v3.dll,
Infragistics.Win.UltraWinTabControl.v3.dll,
Infragistics.Win.UltraWinToolbars.v3.dll, Infragistics.Win.UltraWinTree.v3.dll,
Infragistics.Win.v3.dll, Infragistics.Win.Misc.v3.dll
System
msvcp71.dll, msvcr71.dll
Other DLLs required by DRAFT
These DLLs are loaded as required by specific DRAFT commands:
Draft_DXF_LI.dll, Draft_DGN_LI.dll, Draft_Test_LI.dll, Draft_SVG_LI.dll
Other DLLs required by DESIGN
sgl5NET.dll
11-4
11.4.2
PDMSEXE/Design subdirectory
drawlistWrappers.dll, Wrappers.dll
11.4.3
PDMSEXE/Draft subdirectory
drawlistWrappers.dll, Wrappers.dll
11.4.4
PDMSEXE/Monitor subdirectory
Wrappers.dll
11.4.5
PDMSEXE/Isodraft subdirectory
drawlistWrappers.dll, Wrappers.dll
11.4.6
PDMSEXE/Admin subdirectory
Wrappers.dll
11.4.7
Add-ins
These new user interface .NET components are loaded by the Application
Framework. Each module has an addin file which defines the set of add-ins it
will load, e.g. for Design this file is DesignAddins.xml. The toolbar entries to
show and hide each add-in are defined in PML.
11-5
11-6
12
12.1
Version Error
Error:
System.IO.FileLoadException: The located assembly's manifest
definition with name 'PDMSResources' does not match the assembly reference.
Solution: All .Net assemblies must be the same version. Check
File>Properties>Version Assembly Version on all assemblies is 11.6.1.0 or whatever
the current version is.
12.2
Error:
mon.exe.
The directory from which the importing component loaded. (i.e. the Design
subdirectory where Wrappers.dll is loaded in the case of Design)
The Windows directory (default: C:\Windows) (we dont install anything here)
Since the module DLL does not live in the same directory as the Wrappers.dll then
unless PDMS is running from %PDMSEXE% the %PATH% will be used to locate
12-1
the module DLL. (The Wrappers.dll subdirectory is effectively is the directory which
is first looked in for all the Win32 DLLs which Wrappers depends on i.e.
<module>.dll, sglNet.dll, udDNet.dll, )
Make sure that both %PDMSEXE% and %PATH% point to the root directory in
which PDMS is installed.
12.3
Interface incompatibility
Error:
An exception System.MissingMethodException has occurred in mon.exe
Or
An exception System.IO.FileNotFoundException has occurred in mon.exe
Additional information: A procedure imported by 'Wrappers' could not be loaded.
Solution:
The interfaces between components are not compatible. Check
File>Properties>Version Assembly Version on all assemblies is 11.6.1.0 or whatever
the current version is.
12.4
12-2
12-3
12.5
No Add-ins
Problem:
Solution:
Add-ins loaded by each module are defined in the following xml files:
DesignAddins.xml
DraftAddins.xml
IsodraftAddins.xml
SpoolerAddins.xml
If Add-ins are missing, check that these files exist in %PDMSEXE%
12.6
Window Layout
Problem: Window layout is not restored e.g. Add-ins position and/or docked
state,
Solution: The file <module><version>WindowLayout.xml in the %PDMSUSER%
directory stores this information for the each GUI module. If this file is deleted then
the window layout will return to its default.
12.7
Serialization
Serialization is the process used to store the data e.g. history stacks, toolbar state
for the GUI in a .NET environment.
Problem: Information is stored per project and per module in the following files
in the %PDMSUSER% directory:
<project><version>Settings.bin
<module><version>Settings.bin.
Solution: These files may be deleted or transferred between users working on the
same project.
12-4