duminică, 14 iunie 2015

Catalog SNC Constanta

http://marinepdms.blogspot.ro/2015/06/user-defined-attributes-uda.html












#POSNO
Flat Bar 5-Hole
SHOW !!FirstForm 
CALL !!CRTPATH()
Q EVAR 'MRT000'
Q DBFILE
$R6  TRACE PROGR.
C:\AVEVA\Marine\OH12.1.SP4\marine.bat Paragon MRT SYSTEM/XXXXXX /ALL
DELETE REGI MEM
$T8+
DELETE GSURF
DELETE CSURF
Show !!FirstForm 
setup form !!FirstForm 

MONDO TEHNICUS S.R.L.
Str. Burada Theodor, 24, 0757137487 tl
0766611742 cumpana dan

q connection p1
q p2con
q skey
Q RTEXT

Q hcon= to check head connection attached with which branch
Q tcon= to check tail connection attached with which branch

Rem All = Remove All From Display

Q Att =Display The Attributes Of The Current ElementREM CE Remove Current element


















INPUT BEGIN
NEW UWRLD /BL-UDAS

NEW UGROUP /BL-UDAS/PARAGON

NEW UDA /BL-UDAS/ARTNO
DESC 'Article number'
ABLE 4
UTYP TEXT
ULEN 30
RPTX 'ARTNO'
ELEL ADD SCOM SPCO
DFLT '-'
UDNA 'ARTNO'

END
NEW UDA /BL-UDAS/EANCODE
DESC 'EAN Code'
ABLE 4
UTYP TEXT
ULEN 30
RPTX 'EANCODE'
ELEL ADD SCOM SPCO
DFLT '-'
UDNA 'EANCODE'

END
END
END
INPUT END  UWRLD /BL-UDAS
INPUT FINISH

q evar PDMSUI

Environment variable PDMSUI :C:\AVEVA\Marine\OH121~1.SP4\PDMSUI\

q evar pmllib

Environment variable PMLLIB :d:\AVEVA\PMLLIB Y:\AVEVA\Tools\Ger1214\pmllib1214 C:\AVEVA\Marine\OH121~1.SP4\PMLLIB\

DBLIST. FROM COMMAND LINE

Depending on what's in those sites regarding connections, output ce might not suit you totally... That's why in these cases I always use DBlisting: one file without connections and references, than another with only the connections and references... Question is maybe: why you want to db list a complete site? With a bit of clever model setup you can just make a copy of the db file itself...

You can use the following sample code:

file /c:tempdblisting.mac 
/SITE_A $* Change as required 
output ce 
/SITE_B $* Change as required 
output ce 
term
Q TTEXT
( STR ( ATTRIB RPRO BPAR ) + 'x' + STR ( ATTRIB RPRO DPAR ) )
Q RTEXT

Rtext Seamless Hydraulic Tube, EN10305-4


To install this package a number of steps need to be taken and a basic understanding of AVEVA Plant/AVEVA Marine administration is needed.

First enter Lexicon and run the provided bl-udas.txt. This can be done using drag and drop by dropping the file onto the command line or traditionally with a $m command. Note that the file creates a udaworld so it can be run anywhere inside Lexicon. Write access to a DB is needed.

With the UDAs in place go to Paragon. When in Paragon the file dboutput_catalogs.txt needs to be run. This will create the catalog items, any associated connection type worlds and any tables needed.

Enter Outfitting Draft and run the file dboutput_draft.txt. This creates the symbols used by the catalog elements. For companies who already have some symbols this step is needed since only one symbol file can be used at a time.

Add the binary file BL-SYMBOLS to the options file. Example:


SymbolFile /%pdmsuser%/BL-SYMBOLS

To use the provided PML function blsetudas.pmlfnc it must be installed in the PMLLIB path. After copying the file to the PMLLIB directory make sure to issue the command “PML REHASH ALL” before attempting to run the file.
The file componentselection.pmlfrm will need to replace the original version which is included with the program. This is because the BLÜCHER piping components are non-standard bore (e.g. 75mm, 110mm) which cause an error message when using the original file.

The entire directory plots needs to be copied to %pdmsuser% in order for the application to find them. These files are plot files that show what the component looks like in the 3D model. Please note that these plot files can be changed and updated on a per isometric basis, so that they reflect the actual situation where the pipe is to be installed.

1.                  Adding a directory to PMLLIB

As mentioned above the included file componentselection.pmlfrm will need to replace the original file. To find out where to put this file issue the command “q evar pmllib” in a command window in AVEVA Marine. If the response is something like this:
Environment variable PMLLIB: C:\AVEVA\Marine\OH121~1.SP2\pmllib\

Then there is no company specific PMLLIB directory is use. If this is the case a new directory needs to be created, e.g. C:\AVEVA\Marine\oh12.1.local\pmllib. The next step is to edit the evars file used to set variables for AVEVA Marine, in a default installation this file will be called C:\AVEVA\Marine\OH12.1.SP2\evars.bat. Open the file in a text editor and go to the bottom of it and add a line like this:
set PMLLIB= C:\AVEVA\Marine\oh12.1.local\pmllib %pmllib%
Save the file and start up AVEVA Marine, any module, and issue the command “q evar pmllib” again. If the program now responds
Environment variable PMLLIB : C:\AVEVA\Marine\oh12.1.local\pmllib C:\AVEVA\Marine\OH121~1.SP2\pmllib\
then the PMLLIB variable was successfully edited. Now copy the entire directory provided with this package into the newly created directory, and then run the command “pml rehash all”.

1.                  Isodraft settings

A sample options file for Isodraft is provided in the samples directory for review isometrics created in Outfitting or Design. This is a slightly modified version of the file that comes with AVEVA Marine or AVEVA Plant. This file needs to be installed in one of three places:
·        %pdmsuser%\std directory. If the file is present there Isodraft will not search any of the other directories.
·        %xxxiso%\std directory where xxx is the project code. This is the second place where Isodraft searches for the file. If the file is not present here it goes on to search in the next directory which is
·        %pdmsdflts%\std directory. This is where the file is installed when the product is installed.
In any of the cases above the file name needs to be previewisostd.txt, otherwise the application will not find the file.

To use the stand-alone product Isodraft a few settings are suggested but not by any means necessary:
To remove any unnecessary dimension lines add this line to the options file:
-          Dimensions Overall  CENTRELINE  ONLY  STOPPING Branch Connections

To add the needed symbols to Isodraft add the line
-          SymbolFile /%pdmsuser%\bl-symbols
 to the options file unless a symbol file is already in use, in which case the symbol file will need modification. See “Installation” above.

The following line needs to be added in order for Isodraft to add detail plots onto isometric drawings:
-          position detailplot corner bl at x 200 y 20 direction r
Also, in order for this to work the DPFN attribute needs to be set on either a branch component, the SPCO that the piping component points to or on the SDTE that the DETR attribute of the SPCO points to. The two latest are set in the included sample spec /EUROPIPE for reference. Further, the coordinates (x 200 y 20) probably will need tweaking to suit the frame of the isodraft backingsheet.

Usage
Most components included here are perfectly normal piping components and do not need any explanation. There are, however, a few components that might need explanation:
-          There is a tube SCOM size DN65 included in the catalog. BLÜCHER do not use this size in their components but the reason it is included is there are elements with flanges on, and some of these are DN65, see element /854.200.075_S for example. When connecting a branch to a DN65 flange the program will issue a warning unless straight tube is available in that size in the spec. It will still work without adding the tube to the spec but if it is added it will not issue a warning.
-          Penetration ATTA. A penetration atta is included in the catalog for convenience. Most companies have their own, and any penetration atta is OK to use. Please note that when using the penetration atta if the attribute SPKBRK is set to TRUE it will raise an error when running isometrics. If, on the other hand, Spkbrk is set to FALSE then the ATTA can be placed at the top of the floor that is being penetrated even if it happens to be clashing with another component such as a Ftub of type 867.
-          To use the EAN code or the Article number on isometrics just change the line “Itemcode  from SPREF” to “Itemcode  from :EANCODE” or “Itemcode  from :ARTNO” in the used options file.
-          All BENDs and ELBOws are modeled to the correct angle, e.g. 87.5. This means that zero-radius angles should not be needed.
-          P-points on ELBOws and CROSses and TEEs are set to have a tolerance of 3 degrees. This feature is only available in AVEVA Marine 12.1 and later versions.
http://wikihelp.autodesk.com/AutoCAD_Electrical/enu/2012/Help/1040-Advanced1040/1054-Build_yo1054/1055-Build_yo1055
403_FWC-002




http://pdmsmacro.wordpress.com/

How to convert a SLD file to DWG drawing.

Usage: SLD2DXF slidename

0 comentarii:

Trimiteți un comentariu

Share

Twitter Delicious Facebook Digg Stumbleupon Favorites More