After importing a model the pipe wall thickness values were found to be very large compared to the pipe size:
why does this occur and how to avoid it?
Let us look at the *.MSG file message that was displayed during the import:
As can be seen in the *.MSG file the following warning was displayed multiple times:
*** Warning: Extremely Large Thickness May Cause Error
Open the actual *. PCF file that was imported in NotePad, and search for "PIPE":
Note the Call out description = "Item-Code 2"
Now perform a new search in the file for "Item-Code 2", (typically located near the bottom of the file):
Open program Help / manual:
See section on Mappings - Attributes, note that the wall thickness information in a PCF file format would be located in COMPONENT ATTRIBUTE 4.
Look back in the actual PCF file for information mapped in COMPONENT ATTRIBUTE 4 = 600-NPA-0300
Therefore, what ever application created this has used Component Attribute 4 for another purpose than what the PCF translator has been set up to handle, The PCF translator will try to read this attribute information as a wall thickness (ex. wall thickness = 600).
Update program creating the PCF file to correctly export the wall thickness to Component Attribute 4 or manually update the PCF file Attribute 4 data as needed.
The following enhancement has been logged :
Enhancement 224511 / 590524: PCF Translator: Fetch Pipe wall thickness from Item Code > Description
Example PCF file:
END-POINT -5000.000 500.000 500.000 42
END-POINT -2000.000 500.000 500.000 42
ITEM-DESCRIPTION PIPE .500 EFW LOTEMP STL A671 CC60 CL 23 S2
DESCRIPTION PIPE .500 EFW LOTEMP STL A671 CC60 CL 23 S2
What Wall thickness will the imported pipe have in AutoPIPE?
Answer: Correct, 0.375 inch
Because a. there was no component-attribute4 data, b. item description was not formatted correctly, and therefore the program defaulted the wall thickness to schedule = STD for that pipe size, from library data equals 0.375 inch.
Original PCF file has been updated with:
DESCRIPTION PIPE S/XS EFW LOTEMP STL A671 CC60 CL 23 S2
Question: What Wall thickness will the imported pipe have in AutoPIPE?
Answer: Correct, 0.500 inch
Because there was no component-attribute4 data, however the description schedule was found to be formatted correctly for a viable schedule pipe size,
Question: What if the schedule was set to S/10 (note that S/10 is not a typical standard for a 42 inch pipe size)?
Answer: the wall thickness would be 0.375 because it could not find S/10 in the library and therefore defaulted to STD wall thickness which for this size pipe equals 0.375 inches.
COMPONENT-ATTRIBUTE4 600-JHPA-0200 ITEM-DESCRIPTION PIPE WT 12.7 S/XS EFW LOTEMP STL A671 CC60 CL 23 S2
Answer: Correct 600 inch
Although the item-description has wall thickness correctly formatted, recall from information above where once the program finds viable information it stops searching. In this case, COMPONENT-ATTIBUTE4 was present and had data (i.e. 600-JHPA-0200). Therefore it stop searching and setting the wall thickness to 600 inches
Question: what if "COMPONENT-ATTRIBUTE4 A600-JHPA-0200" was used instead, where the data value started with a letter
Answer: Because COMPONENT-ATTRIBUTE4 started with a letter the program knows that this is not a numerical value and continues to search item description for a valid wall thickness value. Under Item-Description the application found wall thickness correctly formatted and sets it to 0.500 inch (or 12.7mm)
A new enhancement (876955) has been logged to provide a user interface for customization of mapping of component attributes to AutoPIPE properties (ex. component-attribute4 to Line Number).
DESCRIPTION PIPE WT 0.500 S/XS EFW LOTEMP STL A671 CC60 CL 23 S2
Because there was no component-attribute4 data, item description was not formatted correctly, and If both wall thickness and schedule data are present in the description, order doesn't matter, schedule has precedence over wall thickness. Also note that for a 42 inch pipe S/XS wall thickness would actually be 12.7mm. Again, regardless of wall thickness information, schedule data would be read and used first.
PCF Translator FAQ & troubleshooting