Quantcast
Channel: AutoPIPE
Viewing all articles
Browse latest Browse all 16073

Wiki Page: Troubleshooting - Import AutoPlant PXF file into AutoPIPE

$
0
0
Notes: 1. Any troubleshooting should start with a complete understanding of the limitations imposed upon the imported model. Please see the following AutoPIPE help section: Help Contents Search Tab enter "Limitations (PXF import)" (include the quotes), press List Topics button, double click on the selected topic from the list provided to see more information.  2.  See the following document: PXF - PXF - Project Exchange Format.pdf   for details about the PXF file. 3. Instructions on " How to Create a Stress Analysis PXF" can be found in AutoPlant's /  OpenPLANT's online help, search for " Stress Analysis PXF".  Problem 1: Going through the process of exporting a pxf file from OpenPLANT Modeler (08.11.09.278) and then importing the pxf file into AutoPIPE, the global coordinates from OpenPLANT do not get carried over into AutoPIPE.  Is there a way AutoPIPE can read in the coordinates from OpenPLANT so that the two models have the same coordinates? Answer: Close all open AutoPIPE sessions. In the AutoPIPE folder is the following file: C:\Bentley\AutoPIPE V8i SELECTseries\ CADAP.MAP Open the file in any text editor (i.e. notepad). Note: Any changes made in the file must be correct, any mistake can and will cause problems with the imported model. Be sure to match column location and format. Starting on line #60 is a list of setting options that you can change at will. To resolve this issue, change :  'SHIFT ORIGIN (0,0,0) TO FIRST POINT IN MODEL      '     'Y' to  'SHIFT ORIGIN (0,0,0) TO FIRST POINT IN MODEL      '     'N' Note: be sure that the coordinates do not exceed AutoPIPE's limitation with significant digits for corrdinate location.   Otherwise the imported model will crash AutoPIPE at some point. Save the CADAP.MAP file and restart AutoPIPE. For complete details on these options, please see the following AutoPIPE help section: Help Contents Search Tab enter "PXF Import Options" (include the quotes), press List Topics button, double click on the selected topic from the list provided to see more information.    Problem 2: The following is shown when importing a PXF file: forrforrtl: severe (59): list-directed I/O syntax error, unit -5, file Internal List-Directed Read Answer: Please see the following WIKI page:   AutoPIPE PXF import crashes AutoPIPE - forrtl: severe (59): Problem 3: Model is imported with large pipe dia:   Answer: Open the PXF file in any text editor program (i.e. Notepad). Change the UNIT from "MMETRIC" or "METRIC" TO "1" in PXF file (please see below snap shot) Save the file and import it into AutoPIPE.   Problem 4: Error importing PXF file: --------------------------- Error ---------------------------  No piping with OD =     1.400 inches is found in PXF file --------------------------- OK   ---------------------------   Answer: In Error and Warning report you may see that it says why it ignores this pipe to be imported. This is due to the default setting in the AutoPIPE cadap.map file. Go into the cadap.map file in the AutoPIPE root directory (Normally C:\Bentley\AutoPIPE V8i SELECTseries..\ .. ) and the default description will read: // IGNORE OUTER DIAMETER (inches) LESS THAN ' '1.40' // OD 1.4 WILL REMOVE ALL 1" (OD=1.315) AND SMALLER PIPES // VALID OD RANGE IS 0-10 INCHES. Scroll down to your options and reset the last one from 1.40 to 0.00 as shown below: 'IGNORE OUTER DIAMETER (inches) LESS THAN ' '0.00' Save changes before exiting. Most clients don’t want their 1 inch and less piping imported unless it is very high pressure or temperature because it would not require computer analysis. Problem 5: Importing Duct work AutoPlant components crashes AutoPIPE, why?   Answer: From the online help:   AutoPIPE recognizes the following components: PIPE pipe component VALV valve FLAN flange ELBO elbow REDU reducer RIGD rigid pipe with specified diameter DEL ignore nodes associated with this component AutoPLANT has more component names in the connectivity file than those listed above, so it becomes important to map any item type used in PXF file into one of the above listed components. In addtion, PXF Item Type Numbers: AutoPLANT PXF file has currently 20 different item types. The item type number is given under the field 2000 / 2100 in the PXF file. These types are listed below: 0     PIPE COMPONENT   1     ELBOW    2     180 DEGREE BEND    3     TEE , Y or Y STRAINER   4     CROSS    5     CONCENTRIC REDUCER   6     ECCENTRIC REDUCER   7     IN-LINE FITTING: COUPLING, UNION, ETC.    8     END OF LINE FITTINGS: CAPS, PLUGS, ETC.    9     OLET, STUB IN   10   SINGLE VALVE   11   ANGLE VALVE   12   3WAY VALVE   13   4WAY VALVE   14   FLANGE    15   GASKET   16   BOLT    17   TRUNNION, BASE ELL/LINE SUPPORT, SPRING, HANGER   18   SHOE, GUIDE   19   WELD GAP   51   EXPANSION JOINT   99   END CONNECTION TYPE   Therefore if your exported PXF file does not contain component item numbers supported by AutoPIPE, the component can not be imported. Thus, crashing the program. Fix: Confirm exported components from AutoPLANT are converted to AutoPIPE components that can be imported into the program.  Note: According to the CADAP.MAP file, all AT_HVAC_xxxxxx components are mapped to (16)  BOLT, which are ignored (i.e. not mapped to an actual AutoPIPE component like Pipe, Elbow, etc..). As already known, ducts are used in heating, ventilation, and air conditioning (HVAC) to deliver and remove air. T he mapping in CADAP.map of all HVAC - BOLT is done intentionally to skip any HVAC components during PXF import. AutoPIPE does not have square pipe data in it's libraries. T here is one enhancement that has not been added to the program related to this issue ( CAE-CR- 3338 ). Only workaround is to import HVAC into  AutoPIPE and map it to circular pipe run and other components. This can be done by removing the mapping of HVAC_ components from the CADAP.map file (delete all occurrence of "AT_DUCT_xxxx" from the CLASS MAPPING TABLE). By doing so the application will display prompts for the user to map components to existing supported components during import. Problem 6: How can I tell what AutoPLANT component in a PXF file is mapped too in an AutoPIPE model?  Answer: See the follwing steps: 1. Open the AutoPLANT PXF file in any text editor (i.e. NotePAD, Ultra EDIT, MS WORD, etc..) 2. Search PXF file for 2000 or 2100, should be first item on a line. example: 2100 AT_PIPE 2100 AT_VALVE_BALL 2100 AT_SUPPORT_BASE etc.. 3. Open AutoPIPE CADAP.MAP file in any text editor (i.e. NotePAD, Ultra EDIT, MS WORD, etc..) 4. Search CADAP.MAP, CLASS MAPPING TABLE for item name listed after 2000 or 2100 (ex: AT_PIPE, AT_VALVE_BALL, etc.. ).       'AT_PIPE                         '     0    'PIPE    '   // Base components 5. Scroll in the file to the top of the listing to see the section details: Example: ////////////////////////////////////////////////////////////////////// // CLASS MAPPING TABLE (MAX. 2000) // COLUMN 1 : AUTOPLANT'97 COMPONENT CLASS SPECIFIED IN CODE 2100 // COLUMN 2 : ITEM TYPE AS USED IN AUTOPIPE.  MUST BE MAPPED TO ONE //            OF THE DESIGNER COMPONENT TYPE (CODE 2000). // COLUMN 3 : MENU REFERENCE KEY USED BY DESIGNER (CODE 2001) // // USRCLASS.MAP COMPLEMENTS THIS TABLE // // NOTE: AUTOPIPE SUPPORTS BOTH THE NEW (AUTOPLANT'97-CODE 2100) AND //       OLD (DESIGNER-CODE 2000) FORMATS.  AUTOPLANT'97 COMPONENTS //       (CODE 2100) ARE MAPPED TO EQUIVALENT DESIGNER COMPONENTS //       (CODE 2000 AND CODE 2001) ////////////////////////////////////////////////////////////////////// Based on this informaiton,Column #2 identifies exactly what component the item is mapped too (ex. 0) 6. Scroll down to COMPONENT MAPPING TABLE, refer to column information and then search column # 1 for item number in above step (ex. 0) note in column #2, AutoPIPE component (ex. PIPE). Ex: 00   'PIPE'  : PIPE OR PIPE BEND, IF RADIUS GIVEN == ELBO 7. Conclusion: AutoPLANT PXF AT_PIPE is mapped to a PIPE component in AutoPIPE. Complete Example in summary of above steps : a. In a PXF file search for 2000 or 2100 shows the following: 2100 AT_PIPE. b. Search the CADAP.MAP file for AT_PIPE find the following: 'AT_PIPE  '     0    'PIPE    '  c. Scrolling to the top of this section to understand column details, as noted see column # 2 =   0 d.  Scroll down to COMPONENT MAPPING TABLE, find 0 in table,  see colume #2 for AutoPIPE component, PIPE. e. PXF AT_PIPE is mapped to a PIPE component in AutoPIPE. Problem 7: Import model (PXF) from OpenPlant shows that model have disconnects in several points and AutoPipe place Anchors in such points. See pictures. Problem is that OpenPlant do not show problems and we even can create ISO drawings. In attach you can find model, PXF and pictures. Why AutoPipe add Anchors in points and how to solve this problem? Answer: One of the reasons for the disconnect was upon closer inspection of the original model, gaskets were found to be missing. See close up of butterfly valve with missing gaskets below: Solution: First modify the original model to add gaskets and try to reimport the model into AutoPIPE. Recommend to run Connectivity Check prior to sending data out to AutoPIPE  If this does not solve the issue, using the latest version of AutoPIPE, there is a new feature on the import OpenPlant / AutoPLANT dialog screen, "Join disconnected pipe" (see online help for details on this feature). By adjusting the tolerance to a higher value the same model was imported with fewer anchors. This import tolerance may require some iterative adjustment until desire results are attained. Problem 8: User faced with issue to export pipes with Tap connection from OpenPLANT to AutoPIPE. Need help with import such Tap connections. In attach you can find initial model, exported pxf file and pictures. How do I fix this issue? Answer: The original PXF file contains some Tap_Connection with incorrect coordinates. This issue was on OpenPLANT side and has been fixed now in OpenPLANT v08.11.09.302 Steps to avoid incorrect graphics for taps in AutoPIPE 1. Open USRCLASS.MAP file in text editor from AutoPIPE installation directory. 2. Delete Tap_Connection class entry (if present) and save the file. 3. Import the PXF file again and when mapping dialog prompted then map Tap connection class to Weld as shown below. Problem #9: Imported model has extra points in AutoPIPE model ? Example: Going through the process of exporting a pxf file from OpenPLANT Modeler (08.11.09.278) and then importing the pxf file into AutoPIPE, unexpected additional points and segments are being added to the AutoPIPE model. For example, in the AutoPIPE file provided, point BH35 has been added to the model and is a part of segment BO. Segment BO only consists of point BH35 and is not connected to any other segments. It is unclear how this segment and point got added, and the desire is for it not to be in the AutoPIPE model. Solution: under construction

Viewing all articles
Browse latest Browse all 16073

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>