While creating Pipe elements, we may face with situation when we need to preview category elements, that’s in current specification. Continue reading Pipe Component Preview
Usually admins don’t have problems with export to .ATT of a small models or
if they have not demanding customer.
To find clashed elements in CSV format in customizeable way you can you such request. This example search thought pipes under /STABILIZER.
1;# HH CLASH; NOZZLE 2 of EQUIPMENT 1 of ZONE 1 of SITE /AFG-CX01.HVAC; NOZZLE 2 of EQUIPMENT 1 of ZONE 3 of SITE /AFG-CX01.HVAC; at E11299 N1299 U1501;user
2; # HH TOU; NOZZLE 2 of EQUIPMENT 1 of ZONE 1 of SITE /AFG-CX01.HVAC; BOX 1 of EQUIPMENT 1 of ZONE 3 of SITE /AFG-CX01.HVAC; at E11300 N1125 U1500;user Continue reading Clash Report in CSV format
This macro may be used to find out, what END is closer to PANE (or all other types) that is intersects SCTN.
We use clash tool, to find out at what point we have collision and than check which end is closer to it.
If we faced with situation, when we need some object and there is no such in standard PMLLIB.
We can extend it using .NET Library and PMLNetCallable Aveva Pdms layer.
Usually when user haven’t properly exit from Aveva Pdms, they leave phantom users in the system or claim some elements.
In the case you need flow symbol in Draft, you may use this macro.
In command window launch : $M/TpArrowFlowAR.PMLFNC,