Hi
I want create new component in spec Editor with parametric geometry. I dont know what mean all the abbreviations in box primary end type. There is a index to abbreviations?
thanks for answe.
Jirka
Solved! Go to Solution.
Solved by RSFAdsk. Go to Solution.
Solved by gulnacm. Go to Solution.
Hi Jirka,
The Primary End type is just a filter that is used to help choose a script that is logically asscoiated to an end type. For example the scripts for valves is extensive, we added the end type to help reduce the amount to choose If you want a Flanged type valve, you can choose the FL end type and the selection is reduced. This does not assign port property information in the catalog. You will still need to assign the data in the catalog to describe how the new component is to connect to adjacent objects. Below is some end type definitions.
BV = Beveled or Buttwelded
PL = Plain end
THDM & THDF = Threaded male and female
SW = Socket weld
LAP = Collar Lap joint connections
GRV = Groove
SO = Slip On
PPL / PSW = Plastic Plain and Socket
LFL / LLP = Lined Flanged and Lapped
BELL /SPIG = Bell and Spigot connections
TAP = for tapped connections in pipe and fittings
Hello,
The primary end type descriptions are available here Manage Endcode Dialog Box.
I dont think that the description can be seen directly in the spec editor.
I should mention that you can enter your own value if you need to.
it says in help :-
"Note:Endcodes are saved to the installation of AutoCAD Plant 3D 2012, they are not saved to the Project."
Ok so where exactlly are they stored...i want the new endcodes that ive added using the endcode manager to show up on other machines...do i need to manualy add them to every new install of the program or are they kept in with the content we have pointed to on the server (AutoCAD Plant 3D 2012 Content) like the nozzle.acat etc.
Hello,
The file name is EndCodesConfig.xml, which is stored under %appdata%.
C:\Users\<username>\AppData\Roaming\Autodesk\AutoCAD Plant 3D 2012 - English\R18.2\enu\Support\EndCodesConfig.xml
I believe this does mean that you need to copy EndCodesConfig.xml into each profile.
How do you assign the LFL to show the end type for a flange for the isokey? we added a linedflange end type and when we run the iso, it uses the "missingisosymbolplaceholder" block instead of the "flange" block.
Thanks
Can't find what you're looking for? Ask the community or share your knowledge.