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
We will need:
- GhostScript (link)
- Plot (placed in %PDMSEXE%\Plot\ + also need %PDMSEXE%\libifcoremd.dll and%PDMSEXE%\libmmd.dll)
- and .bat file
Does your test.dll correctly loaded in PDMS?
You can check this Help->About->Additional Info (this path is for PDMS 12.1 SP4)
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.
Usually when user haven’t properly exit from Aveva Pdms, they leave phantom users in the system or claim some elements.