naming convention ports

[pschleinzer]

Hi @all,

is it mandatory for fittings entry or end ports to be named port0, port1, port#...

Does it have any influence for non-spec-driven piping? And for driven?

Pls. let me know asap, because right now I'm preparing our custom library parts to be ready for piping module...

br

Peter

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[JimBarrettSmith]

Peter

The name of the port should not have any impact on how spec driven piping works.  It is the parameters on the ports that control the behaviour

Review this documentation http://help.ptc.com/creo_hc/creo30_pma_hc/usascii/index.html#page/pma/piping/Mandatory_Port_Requirements.html

thanks, Jim

[pschleinzer]

Hi Jim,

thanks for Your answer, but I'm not convinced yet.

"Entry ports are specially named coordinate systems that can be referenced by certain piping routing features."

http://help.ptc.com/creo_hc/creo30_pma_hc/usascii/index.html#page/pma/piping/About_Fittings.html

Any clue about it?

thx

Peter

[JimBarrettSmith]

Peter

I have just spoken with development and they have confirmed that the Csys can be any name.  The first CSYS in the model is considered the up stream port, the second the downstream port and then the 3rd a branch port.

I will ask for the documentation to be clarified - thank you for pointing it out!

Cheers, Jim

[gkoch]

Note that the referenced documentation is for non-spec-driven, while Jim referred to spec-driven.