Beruflich Dokumente
Kultur Dokumente
Release 12.0
Upgrading from PDMS11
Service Pack 6
Disclaimer
Information of a technical nature, and particulars of the product and its use, is given by AVEVA Solutions Limited and its subsidiaries without warranty. AVEVA Solutions Limited and its subsidiaries disclaim any and all warranties and conditions, expressed or implied, to the fullest extent permitted by law. Neither the author nor AVEVA Solutions Limited, or any of its subsidiaries, shall be liable to any person or entity for any actions, claims, loss or damage arising from the use or possession of any information, particulars, or errors in this publication, or any incorrect use of the product, whatsoever.
Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every part of it (including source code, object code, any data contained in it, the manual and any other documentation supplied with it) belongs to AVEVA Solutions Limited or its subsidiaries. All other rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without the prior written permission of AVEVA Solutions Limited Where such permission is granted, it expressly requires that this Disclaimer and Copyright notice is prominently displayed at the beginning of every copy that is made. The manual and associated documentation may not be adapted, reproduced, or copied, in any material or electronic form, without the prior written permission of AVEVA Solutions Limited. The user may also not reverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the product described in this publication may be incorporated into any third-party software, product, machine, or system without the prior written permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal prosecution. The AVEVA products described in this guide are to be installed and operated strictly in accordance with the terms and conditions of the respective licence agreements, and in accordance with the relevant User Documentation. Unauthorised or unlicensed use of the product is strictly prohibited.
AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.
Trademarks
AVEVA and Tribon are registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of the AVEVA or Tribon trademarks is strictly forbidden. AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Limited or its subsidiaries, registered in the UK, Europe and other countries (worldwide). The copyright, trade mark rights, or other intellectual property rights in any other product, its name or logo belongs to its respective owner.
Revision History
August 2010 First issue for PDMS 12.0.SP6
12.0.SP6
Backing page
12.0.SP6
Contents
1
1.1.1 1.1.2
2
2.1
3
3.1 3.2 3.3 3.4 3.4.1
4
4.1 4.2 4.3 4.3.1 4.3.2 4.3.3 4.3.4 4.4 4.5 4.5.1 4.5.2 4.6 4.6.1 4.6.2 4.6.3 4.6.4 4.6.5 4.6.6 4.7 4.8 4.9
5 6 7
7.1 7.1.1 7.1.2
MIXING PDMS 12 AND PDMS 11.6 PROJECTS ................................................... 23 FEATURES REMOVED AT PDMS 12.................................................................... 24 UPGRADING FROM EARLIER PDMS 12.0 RELEASES ....................................... 25
UPGRADE FROM P&ID MANAGER TO SCHEMATIC MODEL MANAGER ............................................25 Setting Schematic Model Manager options ............................................................................26 Upgrading Existing 3D Integrator Projects ..............................................................................26
8
8.1 8.2
COMPATIBILITY .................................................................................................... 28
AUTOCAD ................................................................................................................................28 DATA ACCESS ROUTINES (DARS) ..............................................................................................28
12.0.SP6
Backing page
ii
12.0.SP6
PDMS 12.0 is a major update from earlier releases of PDMS but every effort has been made to simplify the upgrade process. Most of the database updates are automatically applied when using PDMS 12. Please note that once a database has been written using PDMS 12, it will no longer be accessible by PDMS 11. Upgrade scripts are provided to upgrade projects from PDMS 11.6. It is strongly recommended that projects are backed up before commencing the upgrade process. Global projects should be upgraded at all sites simultaneously; the recommended procedure is to consolidate them at the hub, perform the upgrade and re-distribute as required. It should be noted that PDMS 12.0 databases will not be accessible by PDMS 11.x due to format changes. However, the inconvenience should be minimal as PDMS 12.0 can access PDMS 11.6 databases (in read mode) from a foreign project. Users own PML applications from PDMS 11.4 onwards should continue to work, after being amended to use the new application switching mechanism. Please see Chapter 23 of AVEVA PDMS and associated products Release 12.0 User Bulletin. It is possible that some form layouts will be adversely affected by the change at PDMS 11.6 to the standard Windows proportional screen fonts, though this depends on the way the forms have been defined. There is also scope for enhancement by using the new facilities offered by PML, such as toolbars and docking forms. Many of the AVEVA applications have been upgraded in this way, so users who have revised the AVEVA applications should review their changes in the light of this work. Any Data Access Routines (DARs) programs must be re-compiled please see section 8.2.
1.1.1 IT environment
Earlier releases of PDMS 12.0 were supported on Windows 2000 and Windows XP. PDMS 12.0.SP6 is still supported on Windows XP and also brings support on Windows 7, both 32and 64-bit. It is not supported on Windows 2000, which is no longer supported by Microsoft. It requires version 5 of AVEVAs Flexman license server, together with an appropriate license file. It was built using Microsofts Visual Studio 2008 and uses their .NET Framework version 3.5. For full details, please refer to the PDMS 12.0.SP6 User Bulletin.
12.0.SP6
Error attempting to access a PDMS 11 project using PDMS 12 Among other things, the upgrade process will: Enter Admin o o o Delete and re-create the COMMS elements to allow larger MDBs Mark the project as a PDMS 12 project Update the module definitions, including removal of the obsolete DESCOMP module and its COMP databases
Enter DRAFT o Create a new DRAFT (PADD) database (MASTER/STYLWL) with a STYLWL and add it to relevant MDBs
12.0.SP6
o o o o
Read %pdmsdflts%/dra-pens and dra-lindef and create definitions of user defined pens if necessary Run the command UPDATE STYLEATTS on all current Draft (PADD) Databases Create a new directory structure for DRAFT Picture Files Optionally regenerate the picture files to cater for increased accuracy (this is the timeconsuming step)
Notes: DRAFT databases that do not belong to an MDB will be missed, as the process upgrades each MDB containing one or more Draft (PADD) databases. Users are advised to create a temporary MDB for all such orphan databases, if any. For a Global project the sequence should be:o At the Hub (where the STYLWL should be created), go through all Draft (PADD) databases (those that are primary at the Hub will be writeable, those that are nonprimary at the Hub will be read-only); add all necessary pen information to the new STYLWL (which is writeable at this location) Propagate the db containing the STYLWL to all locations. At each location go to each Draft (PADD) db and run the Update Style Attributes command.
o o
If applicable, the user should delete and re-create all Isodraft symbol files. TrueType fonts are available in PDMS 12 but may not be mixed with the older PDMS fonts (font families 1 to 4) in any way. To upgrade libraries or drawings, it is necessary to output them to a Data Listing, edit it to change the fonts and then re-input: libraries and then drawings. Before re-input, the receiving project should have suitable fonts created in Admin as new font families (from 5 onwards). It is advisable to update the spatial map after upgrading a project to PDMS12. This can be achieved using the command MAP BUILD MDB.
12.0.SP6
DESIGN Upgrade
PDMS 12.0 Design database updates are automatically applied when using PDMS 12, even though it is a major update from earlier releases of PDMS. It should be noted that PDMS 12.0 databases will not be accessible by PDMS 11.x due to format changes. However, the inconvenience should be minimal as PDMS 12.0 can access PDMS 11.6 databases (in read mode) from a foreign project. Major changes to PDMS Design databases include many extensions and more accurate (double precision) numbers. The upgrade to increase accuracy is performed on-the-fly by changing data as it is updated in the normal course of design work. It is not necessary to use the database Reconfigurer. The supplied upgrade scripts do not perform any operation on Design Databases. It is advisable to update the spatial map after upgrading a project to PDMS12. This can be achieved using the command MAP BUILD MDB.
Question: Answer:
Following an Upgrade all my Bends are very large or corrupt? With AVEVA PDMS version 12 a new concept of "Implied" BENDS has been introduced, allowing automatic mitring of bends by means of core software rather than by a complex GMSE. When upgrading existing projects that contain 0 (zero) radius, variable angle, bends (commonly used in design to deal with sloping lines) and where no geometry exists for the bend, the catalogue SCOM(s) must be updated so that they have a reference to an empty GMSET. For further information please consult section 11.4 of the AVEVA PDMS version 12 user bulletin. PDMS (12 Series) has a new Mitred Bend which requires no geometry. If a bend has no geometry it is assumed to be a Mitred Bend of the new type.
12.0.SP6
The way in which Line Styles and Colours are used and stored has changed at version 12. There is an upgrade path supplied to assist with moving a project to use the new methodology, however there are some factors that should be considered when planning an upgrade.
3.1 Introduction
At PDMS 11.6 Pen definitions which associated Colours to Line Styles, were held in two defaults files that were loaded on entry to the DRAFT module. DRA-GEN-LINDEF LPICTURE 30 MODE 3 SIZE 6 REP 15 GAP 4 LPATTERN 11 REP 16 DASH 8 GAP 8 DASH 8 GAP 8 DASH 8 DRA-PENS SETPEN 131 Colour 2 SOLID LTHICK 1 LPIC 30 GLYPH 15 STOP SCALE 1 SETPEN 132 Colour 5 LPATT 11 LTHICK 5 LPIC OFF GLYPH OFFSTOP SCALE 1
The defaults file DRA-GEN-LINDEF contains definitions for User-defined Line Pictures and Patterns, while the file DRA-PENS contains User-defined Pen Settings, which linked Colours and Line Styles together to form a Pen Number. In the example above, Pen 131 links the Colour Red to Line Picture 30 and System Glyph 15, while Pen 132 links the Colour Green to Line Pattern 11. These produce the line styles as shown. The major disadvantage of this mechanism was that a new pen number had to be created when a new colour was required.
12.0.SP6
At version 12 the User-Defined Line Styles and Colours are stored in the database.
LSTYNO 1 LSTYNO 2
User-defined line styles are stored in a Style World and are given a Line Style Number, while colours are stored in new attributes at each DRAFT element. For example, a STRA primitive has the attributes NLSTYLE and NLCOLOUR. This is more flexible than at version 11.6 in that the colour can now be changed independently of the line style.
Width at 12 0.2 mm 0.4 mm 0.6 mm LTHICK * 0.2 mm, For example 4 = 0.8 mm 5 = 1 mm etc
12.0.SP6
The example Line Style definitions and Pen settings shown above are converted into line styles in the database and follows.
The Line Style element required to replace the above file definitions is set as follows;
NEW STYLWL NEWLSTYTB NEW LINEST /Diamond-Style LWIDTH 0mm PATNAME SOLID GLYNUMBER SYS 15 DECSIZE 6mm DECGAP 4mm DECREPEAT 15mm DECMODE 3
LSTYNO 1 LWIDTH 0mm The Line Style number, specified by the system The width of the line (in mm or inches). Value 0 is allowed and means the minimum-allowed line width, approximately 0.2mm. This is set using the value given in SETPEN parameter 3, in this case 1 the minimum. The name of a system defined line style. This is derived from SETPEN parameter 2, in this case SOLID
PATNAME SOLID
GLYNUMBER SYS 15 The Glyph number, derived from SETPEN parameter 4, in this case the system glyph number 15
12.0.SP6
DECSIZE 6mm
The size to which the glyph is scaled, derived from LPICTURE parameter b, in this case 6mm. The length of each gap left in the path, derived from LPICTURE parameter d, in this case 4mm. The approximate repeat distance between glyphs, , derived from LPICTURE parameter c, in this case 15mm. A code number to signify how the glyphs are distributed, derived from LPICTURE parameter a, in this case 3, spaced along the line.
DECGAP 4mm
DECREPEAT 15mm
DECMODE 3
Every graphics primitive in DRAFT is drawn in a specific colour and style, determined by the values of the relevant colour and style attributes. In the example below, the newly defined Line Style is used on a STRA element. NEW DEPT NEW REGI NEW DRWG NEW SHEE SIZE A3 NEW NOTE NLCOLOUR 10 NEW STRA FPT X100 Y250 TPT X200 Y250 For a STRA to be displayed exactly the same at it was at 11.6, the relevant STRA attributes for Line Style and Colour are set as follows; NLStyle 1 This is the Line Style Number of the Line Style created earlier, alternatively it could have been set using the Line Style Name /Diamond-Style Note that the NLStyle attribute is not a reference attribute but simply a number that relies upon the existence of a Line Style with that number.
NLColour Red This is the colour, which was defined in SETPEN parameter 1 above, in this case 2 or RED.
Now that the Colour has been separated from the Line Style definition, it can be changed easily without having to define another Pen; for example. NLColour Green
For a full description of Line Styles and Colours, please refer to the manual Draft User Guide or Outfitting Draft User Guide version 12, Section entitled Colour and Styles.
12.0.SP6
Instead of
Create a new Line Style, the style is based on the defaults files as discussed above for Pen Definition 132. Navigate to the line Style /Diamond-Style created earlier. NEW LINEST /SingleChained-Style LWIDTH 1mm PATDEFINITION 8 -8 8 -8 8 PATREPEAT 16mm DECMODE 3 The LINEST /Diamond-Style is modified as follows LINEST /Diamond-Style ALTDEF /SingleChained-Style Changes across the system need to be updating using the UPDATE PENSTYLES command. On the plotted drawing, the STRA will appear in the Alternative Style as defined by Line Style Number 2 and not the Displayed Style as defined by Line Style Number 1.
3.4.1 Limitations
1. If the PLOTPEN was being used to plot a System Defined Pen setting, a new Line Style that was equivalent to the System Line Style would be required. The ALTDEF attribute of this Line Style would be set to the required Plot Line Style. 2. At this time, it is not possible to plot Draft elements in a colour different to that set at the element.
12.0.SP6
Please note that the upgrade macros have been enhanced for 12.0.SP6 To assist with the upgrading from a version 11.6 project to a version 12.0 project, a macro is supplied that will carry out the conversion of the User-defined Line Styles and the setting of Draft Element Colours, similar to the method described earlier in this document. To achieve a satisfactory upgrade the macro carries out several tasks, some of them optional. A new Draft database (MASTER/STYLWL) is created to hold the new Line Style elements All Draft (PADD) databases are added to a temporary MDB The Draft defaults files for Line Definitions and Pen Settings are loaded on entry to the Draft module The system creates the Line Styles in the database created for that purpose All Draft (PADD) databases are scanned and all Draft entities have their Line Style and Colour attributes set as necessary All MDBs that contain Draft (PADD) databases will have the new Line Style database added to it The original 11.6 picture files cannot be used at 12 because of internal changes. They will need to be regenerated; this is optional during the upgrade
10
12.0.SP6
FFSTYL E1
NLSTYL E2
DLSTYL E3
The process is very simple. The upgrade is initiated by running the upgradeMac macro from the Monitor command window, either by typing: $m/C:\AVEVA\Plant\PDMS12.0.SP6\PDMSUI\dra\upgrade\upgradeMac or by dropping the upgradeMac macro on to the command pane. The process is tracked by writing 2 files in %PDMSUSER% as it progresses:1. Logfile<proj code> ALPHA LOG file: echo of the console window 2. UpgradeLog<proj code> Upgrade results file reporting success/failures If these log files show no problems, the project itself should be reviewed to check that all is well. It might also be worthwhile checking the database integrity using DICE. The project should now be ready for use with PDMS 12.
11
12.0.SP6
12
12.0.SP6
The Line Style Number is set by the system as it finds Draft elements to update. Consequently, the number depends on database order (!databases = dbs), so it is likely each location will have different Line Style Numbers for the same Line Style Definitions. This means that it is difficult to centralise the Line Styles to a single database that is distributed and shared across the project. A local STYLWL at each location would be required for the duration of the project. If different locations use different Line Style definitions, there is no choice but to continue with different STYLWLs for the duration of the project, or attempt an amalgamation of the defaults files before the upgrade. If there is a common set of default files used at all locations, creating a dummy drawing containing a STRA element for each User-defined Line Style in the defaults files will force the upgrade to create a set of User-defined Line Styles with the same number at each location. Please refer to Creating a Master set of Styles later in this document. When running the update script at the Hub, new databases will be created: one for each location, containing a STYWL specifically for that location. MASTER/STYLWL MASTER/STYLWL_LOC for the HUB for satellites: 'LOC' varies according to the location id
When running the script at any location (including the HUB), all Draft (PADD) databases that are PRIMARY at the location will be updated for style attributes using a STYWL created for that location, hence using the locally defined 11.6 Line Definition files. Each STYLWL element will be named according to the location id; STYLWL /Project_STYLWL STYLWL /Project_STYLWL_LOC for the HUB for satellites: 'LOC' varies according to the location id
When running the script at any location, only MDBs that contain Draft (PADD) databases that are PRIMARY at that location will have the database that contains the STYLWL for that location added to them and hence be updated. Various other enhancements have also been made at 12.0.SP6 and a test option is available.
4.3.4 Limitations
The project administrator should be aware of some limitations: If he has chosen to upgrade a Global project with the Draft (PADD) databases at their Primary Location, the upgrade macro cannot handle the situation where a location is administered elsewhere. For the upgrade to function correctly, all locations must be administered locally.
13
12.0.SP6
g) Type the command UPDATE STYLEATTS in the Command Window to update all drawings. h) Delete the locally created MASTER/STYWL_LOC MASTER/STYWL or for Global Projects the
14
12.0.SP6
i)
Replace all Draft (PADD) databases in their original MDBs and add the MASTER/STYLWL database to each MDB that contains a Draft (PADD) database. Any drawing that needs to be accessed will require the Picture File updated as otherwise it will be unusable at version 12
j)
3. During the creation of User-defined Line Styles, the system will only create a Line Style if it has been used on a drawing in the current MDB. If the drawings in the project do not utilise all of the Line Styles defined in the defaults files the styles will not get created. To create a set of Line Styles for all lines in the default files refer to Creating a Master set of Styles as described later in the document. This will ensure that all 11.6 defined Line Styles have a corresponding database Line Style. This can be done afterwards but doing it before the upgrade may be simpler.
4. At version 11.6 only the first 16 colours were defined by default. If any User-defined colours
above 16 have been used they will need to be reset to suit the new colour table available at version 12. Please refer to the section later in this document Colour comparison between 11.6 and 12. 5. The upgrade script creates a new database MASTER/STYLWL to store the new Line Style Library. However, this is not included in any MDB unless the option to update the picture files has been chosen. When updating picture files manually later, the database containing the Line Style Library will have to added into the MDB first. Please see the AVEVA PDMS Installation Guide and the AVEVA Global Installation Guide.
4.5 Summary process for upgrading Global projects from PDMS 11 to PDMS 12
4.5.1 Preliminary checks
Ensure that the HUB has an up-to-date view of every non-propagating Draft (PADD) database which is primary elsewhere. This is necessary to gather all required pen data at the project HUB. This may mean issuing manual UPDATE DB commands for non-propagating Draft (PADD) databases which are primary at satellites EXTRACT FLUSH DB for all Draft (PADD) working extracts at satellites (if any) All locations must have their old daemons stopped, and their new Global 12.0 Daemons restarted prior to starting the upgrade process. Make certain that the Daemons are running Stop any update events
15
12.0.SP6
16
12.0.SP6
4.6.2 DRA-GEN-LINDEF
In this example, the file DRA-GEN-LINEDEF contains the following Line Picture and Pattern definitions; LPICTURE 30 MODE 3 SIZE 6 REP 15 GAP 4 LPATTERN 11 REP 16 DASH 8 GAP 8 DASH 8 GAP 8 DASH 8
4.6.3 DRA-PENS
In this example, the file DRA-PENS contains the following Pen Settings;
DEVPEN 130 Colour 10 TCHAIN THICK CROSS SCALE 4 HPATTERN 10 DEVPEN 131 Colour 2 SOLID LTHICK 1 LPIC 30 GLYPH 15 STOP SCALE 1 DEVPEN 132 Colour 5 LPATT 11 LTHICK 5 LPIC OFF GLYPH OFF STOP SCALE 1 DEVPEN 133 Colour 6 SOLID LTHICK 1 LPICTURE 10 GLYPH 6 STAR SCALE 1 HPATTERN 3 DEVPEN 134 Colour 7 LDASH LTHICK 2 RING SCALE 1 HPATTERN 4 DEVPEN 135 Colour 9 LDASH LTHICK 1 CROSS SCALE 1 HPATTERN 5 DEVPEN 136 Colour 12 LPATT 11 LTHICK 5 LPIC OFF GLYPH OFF STOP SCALE 1
Some are equivalent to System-defined while others use System Line Picture and Patterns or those User-defined above. On update, the following will happen; Pen 130 Pen 131 Pen 132 Pen 133 Pen 134 Pen 135 Pen 136 The System-defined Line Style will be used TChainedThick A new User-defined Line Style will be created in the Style World A new User-defined Line Style will be created in the Style World A new User-defined Line Style will be created in the Style World The System-defined Line Style will be used 'LDashedMedium' The System-defined Line Style will be used 'LDashed' As the Line Style definition is the same, with only the colour being different, this will share the User-defined Line Style created for Pen 132
17
12.0.SP6
4.6.4 In DRAFT
The upgrade process can be simulated by creating a drawing sheet within a version 12 PDMS project. 1. Set the environment variable %PDMSDFLTS% to the location of the Draft defaults files, the User-defined Line Style Definitions and the Pen Settings described previously. 2. In the MDB, ensure that there is only one empty STYLWL that is open in WRITE mode. 3. Create the following example drawing, which contains a example STRA with the old attribute NLPEN set to each of the above user-defined pens; NEW DEPT NEW REGI NEW DRWG NEW SHEE SIZE A3 NEW NOTE NLCOLOUR 10 NEW NEW NEW NEW NEW NEW NEW STRA FPT X100 Y250 TPT X200 Y250 NLPEN 130 STRA COPY PREV by Y-10 NLPEN 131 STRA COPY PREV by Y-10 NLPEN 132 STRA COPY PREV by Y-10 NLPEN 133 STRA COPY PREV by Y-10 NLPEN 134 STRA COPY PREV by Y-10 NLPEN 135 STRA COPY PREV by Y-10 NLPEN 136
Because the attributes for style have not been set all of the STRA elements appear with the default Solid and with the colour inherited from the NOTE. If the background was changed to White the Line colour will be switched to Black by the system. 4. At the NOTE enter the command syntax UPDATE STYLEATTS 5. At the NOTE enter the command syntax UPDATE PENSTYLES 6. At the NOTE enter the command syntax UPDATE ANNO The STRA elements will now appear like this;
18
12.0.SP6
The STRA 1, 5 & 6 are set to use a System-defined Line Styles STRA 2,3 & 4 use new User-defined Line Styles whose numbers are in sequence; this was because during the update, the new Line Styles were created and given their numbers in the order that the Draft elements were held in the database. STRA 7 was set at 11.6 with a User-Defined Line Definition that was exactly the same as STRA 3, except for the COLOUR, hence also uses Line Style 2. As colour has now been separated from the Line Style STRA 7 can use the same Line Style Definition but be set to a different colour using the attribute NLCOLOUR. This is completely different to 11.6 where a new pen had to be defined when just the colour was different. DEVPEN 132 Colour 5 LPATT 11 LTHICK 5 LPIC OFF GLYPH OFF STOP SCALE 1 DEVPEN 136 Colour 12 LPATT 11 LTHICK 5 LPIC OFF GLYPH OFF STOP SCALE 1
19
12.0.SP6
One was created for each of the User-defined pens that were different, as described above. The Line Style Number (LSTYNO) for each LINEST is set from 1-3 sequentially. Each STRA described above has its attribute NLSTYLE set to one of these Line Style Numbers, but it is NOT a reference. On entry to the DRAFT module, the system looks for any STYWL and loads the Line Style Numbers and their definitions into memory. When a Draft element is displayed, the relevant definition will be used if its style is set to one of these Line Styles. This means that it is possible to Output (DATAL) Line Styles in and out of databases without worrying about reference attributes.
If any colours have been defined for a number above 16, users should select the nearest colour in the AutoCAD table and modify the DRA-PENS file to suit BEFORE upgrading to version 12. Any DRAFT element that was set to use this colour number will then have its new colour attribute set correctly, otherwise it will be set to a colour that may not be the same as was expected.
20
12.0.SP6
Question:
We have a project which uses the master set of line styles but the project needs to create their own specific ones. How do we arrange for that? If a project wishes to use specific line styles, they can create their own in another STYWL, which would be added to all MDBs that contain Draft (PADD) databases.
Answer:
Question:
Our local project uses the master set and their own set, but we need to overwrite some master ones locally. How do we arrange this? If some Master line styles need changing locally, output (DATAL) the master ones into a local STYLWL, change them as required and then make sure that the order of the STYWLs in the database order in the MDB are Master, followed by Local. The local one will be loaded last and any conflict overwritten.
Answer:
Question: Answer:
We used to plot some lines in a different colour. How do I do this? Unfortunately, this is not possible at the present time.
Question:
How do I easily find the Line Style being used by a Draft element when all I know is the number? At the relevant Draft element, type in the command GOTO NLSTRE
Answer:
21
12.0.SP6
22
12.0.SP6
PDMS 12.0 projects may continue to use PDMS 11.6 databases as foreign databases, so there should be no need to maintain two versions of shared corporate catalogues until all other projects have been upgraded; the corporate catalogue projects can be done last. Any foreign projects that contain Draft Admin elements, for example Back Sheets, etc must be upgraded first. However, PDMS 11.6 projects cannot use PDMS 12 databases, so this does need to be planned carefully. Once the database includes elements that use the newly increased accuracy, its use in PDMS 11.6 will be incorrect and unpredictable, so this is prevented. Any attempt to enter an upgraded project (or a newly created PDMS 12 project) using PDMS 11.6 will result in an error message:
23
12.0.SP6
The syntax in the project creation program MAKE no longer has the command for specifying pathnames for database schema files. This has been obsolete since PDMS 11.3, when these files were moved to PDMSEXE, but was retained through the PDMS 11 lifecycle for upwards compatibility. The COMP database has been removed as the DESIGN COMPARE option is no longer available: it has been replaced by the new SCHEMATIC 3D Integrator.
24
12.0.SP6
$M/%PDMSUI%/ADM/ADMIN/UPGRADESP5.PMLMAC
It does not matter which module the macro is run from; it will leave the user in the ADMIN module. After the macro has been run the user should inspect the following log file:
%PDMSUSER%/upgradeLog<proj code>
Any warnings or errors are logged in this file. As an example, it might not be possible to update a SCOINS object, perhaps because it is locked. This will be logged so that the user can take corrective action in this instance, the user could unlock the SCOINS objects and re-run the macro.
25
12.0.SP6
In all cases
Check that all mandatory UDAs have been made available. Enter Lexicon, click on Schematic Model Manager > UDA Catalogue, make any changes needed to the selection, and press Apply.
If existing projects have their own copy of the HVACStypeTable.xml file in the <project>dflts\ModelManagement folder, this should be deleted. Integrator will then look for this file in the installed executable folder. This file should only be copied to the
26
12.0.SP6
27
12.0.SP6
Compatibility
8.1 AutoCAD
PDMS 12.0 AutoDRAFT and DXF output functions have been designed and tested with AutoCAD 2006 and 2007. No later version of AutoCAD is supported. Final Designer (version 1.3.SP2, available on the PDMS 12.0 DVD) is compatible with PDMS 12.0 and AutoCAD 2006, but not 2007 or later, and is unchanged since PDMS11.6. PDMS 12.0 is not compatible with earlier versions of AutoCAD.
28
12.0.SP6