A client asked how to map custom items in the catalogs from PnID to Plant 3D. In doing some research, I found out some more key settings in Plant 3D.

It turns out that you can’t (AFAIK) customize the Component Categories or Piping components:

The question was how to I map a custom class in PnID to Plant 3D so that it can get validated?  The easiest (and safest) is to map it to a similar class. If this feature is mandatory, we can do it, but we will have to edit an installation xml file, so remember to back it up and implement it with every release.

For example, let’s create a custom flow meter class under valves in PnID.  The PnID structure is really flexible so this step matters the least. We just need to know which class we are trying to map.

Next we need to edit a special xml file.  Now, this file is stored in the installation directory, so you may need to distribute/back up this file if you have to make changes.

We need to edit this file:

C:\Program Files\Autodesk\AutoCAD Plant 3D 2013 – English\P3dEnumeration.xml

Because it’s in the installation directory, you may need to start your xml editor by right-clicking on the application exe and choosing run As Administrator. Also, make sure Plant 3D is closed when you edit this file.

For our example, I added a FlowMeter BodyType.

If you notice, many sections correspond to entries in the Catalog Editor. From this file, we can learn which options are available for the fields:

The screenshot above, show the settings I filled out for a custom flow meters I put in a spec.

Back in Plant 3D, navigate to Plant 3D DWG > P&ID Object Mapping.  Select the new custom Flow Meter class and click Add Mapping.

Here I selected the Valve class and now the FlowMeter subtypes are available for us:

If you select multiple boxes, you will be prompted to pick a subtype when the part is inserted. I ended up just selected FlowMeter-Inline

After choosing the mappings, we need to select the fields that populate and validate. Don’t forget to check the box at the bottom for when to check the 3D to P&ID validation.

Save all the changes we have made.

After inserting the P&ID symbol, our Flow meter will be available in the PnID Palette:

And we will be able to validate it.

Recently, I wrote about mapping custom PnID class to Plant 3D parts.  In that post we discussed an enumeration xml which contains some interesting settings.

This post will detail the default settings that should be populated for valves so that they can pick up the correct mappings for validation.

In addition the file also has operator information:

Valve Body Type

Ball

Butterfly

Check

Corner

Diaphragm

Gate

Globe

Needle

Plug

InclinedSeat

Tank

Float

Cock

MultiPort

Valve Alignment

Inline

Angle

3-Way

4-Way

Valve Detail

Check

Continuous

MixedProof

Throttle

PressureRelief

PressureReducing

Safety

Block

Shuttle

Diverter

Breather

Actuator Type

Diaphragm

ElectricMotor

Gear

HandWheel

HandLever

Spring

Hydraulic

Pneumatic

Solenoid

Operator Type

Manual

Automatic

Recently, we ran into an issue installing the data integrity hotfix for Plant 3D SP 1.  The issue is that when opening the report creator, the PnPDataObjects.dll cannot be loaded. Users get a warning dialog like this:

The source of the problem is that certain actions in Windows can mark some files as unsecure.  Meaning that until you indicate that they are safe, Windows will not load them.  For example, we’ve all seen the warning in Word that a document was downloaded from the internet.

What happens is that if you click through to the contents of the .zip contains the hotfix, and then copy+paste them into the installation directory (C:\Program Files\Autodesk\AutoCAD Plant 3D 2013 – English), the PnPDataObjects.dll is marked as unsafe.

To correctly install the hotfix, you must extract the zip first and then copy+paste the contents.

While there is no button to click to turn off spec breaks in AutoCAD Isometrics, you can do it via the xml.

Locate the Default theme AnnotationsScheme for your style’s isoconfig.xml.

The easiest way is probably to do a search for SpecBreaker.  Under SpecBreaker, you will have to add an Enabled attribute like so:

Generating your iso again will change this:

to this:

Over the last few days, I’ve been digging through Plant and learning about the new features. While there are not many major new features, I’ve been told that 2014 has fixed hundreds of bugs.

Plant 2014 does have some much needed improvements in a couple key areas, and I’ll walk through some of these in the article. I also went through and tried to locate new commands and system variables.  While this list is not exhaustive, it should give you some more information to track down. Not all of these commands or variables have documentation, but I’ve mentioned that to Autodesk, so I’m sure the help will be updated on them.

Major new updates are Vault (rolled in from Extension pack), P&ID Connectors, drawing annotation manager, and orthographics.

A video of the new features is available here:

http://docs.autodesk.com/PLNT3D/2014/ENU/plant/pip/autocadplant3d_video_newfeatures1_v5.html

A list of 3d modeling features:

http://docs.autodesk.com/PLNT3D/2014/ENU/index.html?url=filesPLNT3D/GUID-18292A2A-B50D-4508-BD5D-C60000B74FAD.htm,topicNumber=PLNT3Dd30e5388

A list of PnID new features:

http://docs.autodesk.com/PLNT3D/2014/ENU/index.html?url=filesPLNT3D/GUID-F21F6716-08C3-472A-AFB8-C3F7B6576CD6.htm,topicNumber=PLNT3Dd30e5541

New Commands

PLANTDWGCHECKER

PLANTBENDENABLEALLPIPETYPES -

PLANTDEFINECALCPROPERTIES

PLANTAUDITVAULTPROJECT

PLANTORTHOADDJOG

PLANTORTHOHIDDENLINEMODE

PLANTORTHOMATCHLINEMODE

PLANTORTHONOCENTERLINE

PLANTORTHOPAPERCHECK

PLANTORTHOPIPEGAP

PLANTORTHOSHOWOPENPIPESYMBOL

PLANTORTHOTBCLOSE

PLANTORTHOTEMPLATESETTING

PLANTORTHOWRITECONFIG

PLANTPROJECTTOVAULT

PLANTSELECTIVECOGSWITCH

PLANTSYNCHRONIZETOVAULT

PLANTSYNCHDWG

PLANTVAACEXPLORER

PLANTVAULTCHECKIN
PLANTVAULTCHECKOUT

PLANTVAULTLOGIN

PLANTVAULTLOGOUT

PLANTVAULTUNDOCHECKOUT

One side note is that now the Size property is available in PLANTDEFINECALCPROPERTIES so we’ll have more posts on that subject coming up.

The first thing I noticed when I placed a pipe gap in 2014 is that there was no hatch on the closed part of the gap.  In the companies I’ve worked, the standard gap always include a solid hatch.

Much like the isometric organization, the orthographic drawings have a drawing that contains blocks used.

The drawing, OrthoSymbolStyles.dwg, by default is located under Orthos\Styles\ in the project folder.  This drawing contains a block called PlantPipeGap that we can modify to get the gap we need.

Open up orthosymbolstyles.dwg, type in BEDIT and the command line and select the PlantPipeGap block.

Draw a solid hatch here:

To make the gap a little prettier, I like putting a wipeout in the background so that the flat pipe end is hidden.

Draw a rectangle for a wipeout shape, and then turn it into a wipeout.

Last, send the wipeout to the back so our gap symbol appears on top.

The final edited block will look like this:

Now our gap looks like this:

And regenerating the view shows this:

You can remove some of the whitespace by playing with the wipeout shape, and make sure your line type setting matches what you want to see when plotting.

Recently, a client mentioned that they couldn’t locate threaded plug valves in the catalogs.  Today’s post will show how to create a custom valve from scratch.  Today we will use a Tufline Sleeved Plug valve: http://www.cranechempharma.com/chempharma/products/valves/xomox-sleeved-plug-valves/screwed-end-sleeved-plug-valves&brandid=6FDB472B-D7F3-EA31-D0E970EBF58FA22A

Downloads

Overview

Below is an overview of the process we will use.

1. Locate the data sheet.
2. Select the sizes to create, type of valve, and the drawing script to use.
3. Add General property data.
4. Add size property data.
5. Add modeling dimensions.
6. Test

In the catalog editor tab, click the Create New Component button.

The data sheet includes size for 1/2” to 2” so we will create all of those sizes. Also, choose the Valves Component category, the ValveBody piping component, set the end type, and give a short description. Choosing the ValveBody piping component allows us to define the valve separately from the actuator information which is the way most of the valves are built. For the graphics, there is a plug valve with female threaded ends already, so we will use that script. The script chosen was CPVI010000_OFOF which is important because it lets us define the length of the threaded hub.

The critical information is the Part Family Long Description, and then the information on each of the sizes.  Here’s the critical information I used.  In addition, fill out the alignment, detail, body type, symbol type, and skey to make the valve conform to similar valves and show up correctly on the iso.

The for each size, enter the matching pipe od, a long description size, and the appropriate dimensions. Make sure to check All Ports have the same properties.

Be sure to check out our library of helpful charts:http://www.pdoteam.com/resources/piping-component-library/

For the engagement lengths, use the nipple engagements chart for Plant 3d:

The left side contains data properties for the component:

The right side contains drawing information for how the graphics will look:

For D1 I used the OD of the pipe, for H1, I used the C value from our data sheet, L is the length from the data sheet minus 2 times the engagement, I1=.5 is the nipple engagement from our standard Plant 3D nipple engagements. The length of the threaded hub is L1=0.55.

Once we have those items, filled in, Plant has the information required to create the part.

As with all new versions, the topic of migrating specs comes up.  In my experience, I’ve run into two little tricks that clarify the process of migrating content to a new version.

Migration Location

When you migrate specs, the spec editor is not modifying the spec or catalog that you select, it makes a copy.  The modified catalog is stored in a Migrated Content folder in your Shared Content Location:

Supporting Content

The other part of migrating catalogs has to do with migrating block-based parts.  When you reference a block in a catalog, Plant 3D stores a copy of it in your Shared Content folder in a folder that matches your catalog name.  The default path for a catalog called ECAD Houston would be something like: C:\AutoCAD Plant 3D 2013 Content\CatalogSupportFolders\ECAD Houston\.

If you look in that folder, you will see folders like 200 and DWG.  The 200 folder stores images of the block you created, and the DWG stores a source file for the catalog to use.

When you migrate your catalog, even though the program asks for the content location, it doesn’t use it or migrate it. To finish the migration process, you have to manually move the content to your new shared content folder.

So, I copied the folder C:\AutoCAD Plant 3D 2013 Content\CatalogSupportFolders\ECAD Houston\, to C:\AutoCAD Plant 3D 2014 Content\CatalogSupportFolders\ECAD Houston\. From that point on, my specs, catalogs, and models could find the information required.

Migration Walkthrough

Launch the Migration function.

Click Migrate, noting that the files are going to be moved to the Migrated Content folder.

Select your specs/catalogs. I typically move the catalogs first, and then the specs.

Specify the content folder.  For moving from 2013, I chose C:\AutoCAD Plant 3D 2013 Content\ even though that appears to have no effect.

The catalog is migrated, you can move it out of here if necessary.

Copy the supporting files and folders for block-based content.

The other day a client needed a report of items by Line Number.  A common way to get the report would be to group by the PipeRunComponent_LineNumberTag.  That report ends up excluding all fasteners. So, the typically, an incorrect report by line number would look something like this:

Noticing the Group and Sort panel at the bottom.  The top level group is by the PipeRunComponent_LineNumberTag.

However, by looking at the class structure in Plant, Fasteners will never fall under the PipeRunComponent_LineNumberTag group, because they are outside of the PipeRunComponent class:

So, the way to solve this is to add a class property to Piping and Equipment that acquires the Line Group tag. I made one called GroupLineNumber. For equipment, this will always be blank, but the program will populate it correctly for Fasteners and PipeRunComponents.

Because we’re adding an acquisition property, those values will not be populated on existing model items. So, you can either go through every item, and toggle the property to override and back to acquire (which updates the value), or use our PDO Extended Fields plugin which updates all the acquisition properties for P&ID and Plant in one shot.

Once do that, they can open the report creator, set the report up like this:

And get this:

Ran into a weird support question.  Per the image below the pipe are not connected, but there are no leak symbols. After some system variable sleuthing, the GRIDMODE system variable was causing this snafu.

GRIDMODE=1

It doesn’t create problems with all models, but definitely with the model from the client, there was an issue.

GRIDMODE=0

Autodesk has released a configuration guide we put together for AutoCAD Isometrics.

http://docs.autodesk.com/PLNT3D/2014/ENU/De-mystifying%20AutoCAD%20Plant%203D%20Isometrics.pdf

About 80 pages long, the manual gives both an overview of the isoconfig.xml and some detailed examples for configuration.

One of the key features is a list of the skeys used, available symbol types, and screenshots of the blocks used to make the symbols.

I hope you find it useful!

One of the most frequent questions we get is, “How do I set the service on my Pipe Line group?”  While I answered this for 2012 here: http://www.pdoteam.com/2012/03/changing-line-group-properties-in-autocad-plant-3d/, in 2013, we have a better option. Open the data manager, and in the bottom left-hand corner is a drop down.

Switch the drop down to Order by Area.

Click the Pipe Lines node, and you will get a list of the pipe line groups where you can edit the service for the whole group at one time.  DO NOT pick a line tag as that gives you a list of the components within the line group.

HTH

When using the default styles, elbows will be called out as cutbacks even if they are 45s. To fix this, we need to do a little editing in the isoconfig.xml

Here is a link to an article that explains the xml editor I am using: http://www.pdoteam.com/2012/08/editing-xml-files/

Here’s a screenshot of what we are going to fix:

In the last section, filters, locate and expand the CutbackElbow filter:

The filter can be read like this, for items where the type is elbow or bend, and the ANGLE property is filled in, and the ANGLE-CDEG is not 90 and the ANGLE-CDEG is not 180.  We are going to modify this to also exclude the 45 angle.

So, after <> 18000, you need to add “AND [ANGLE-CDEG] &lt;&gt; 4500 AND [ANGLE-CDEG] &lt;&gt; 13500” which in the end will make the whole thing look like this:

Notice we also had to exclude the 135 angle. The final result looks like this:

The first extension for Plant 3D 2014 is now available.  This extension includes several new features to the Plant 3D program.

Obtaining the Extension

To get the extension, you will need to be up to date on your subscription.  Then, sign into subscription center (http://subscription.autodesk.com )  with your Autodesk single sign on id.

Click the Downloads Link:

Click Product Enhancements:

and you should see Plant 3D 2014 Extension 1.

The readme is available here: http://docs.autodesk.com/PLNT3D/2014/ENU/readme.html

Here’s the description from the Autodesk site:

Autodesk® AutoCAD® Plant 3D 2014 Extension 1 is an extension to the AutoCAD Plant 3D 2014 product that adds the following functionality:

• Bill of Material on orthographic drawings (plans and sections)
• Weight and Center of Gravity calculations
• Project level control over Isometric Advanced options

In addition, there have been numerous improvements to isometric generation:

• Better annotation and dimension layout
• New Fitting to Fitting theme to help reduce unnecessary dimensions
• Gap lines when crossing to improve readability.
• Weight on Isometric BOM
• Insulation graphics on isometrics improvements
• Support for flanged pipe and lined pipe
• Cut lengths for stub ins corrected
• Numerous minor bug fixes

We will have more information available as we dig into this extension.

Sometimes after migrating a spec, you still get a warning to migrate it (or catalogs with it).  The key is usually that the spec is pointing to old catalogs.

An issue that comes up when modifying migrated specs is that your migrated specs still point to their old catalog locations.

To remedy this, we have to get our hands dirty and modify the pspx file manually (until we can get the migrate fixed or an app to fix the catalog reference – hint, hint).

Because the pspx is just a zip file which the extension renamed, we can use a zip editor to update it.  My personal favorite is 7zip, because it’s free, and has a lot of features.  The screenshots and workflow will reflect using 7zip. Also, I will be using Foxe for editing xml.

First let’s take a look at the internals for a pspx file. After installing 7Zip, right click on a pspx, select 7-Zip, and then Open Archive.

Within the pspx there may be an editor folder.  When this folder is present the spec is storing a hard location to a catalog, and needs to be modified.

Within the editor folder, is a CatalogReferences.xml file:

I have Foxe set to be my default xml editor, so when I open it up, I see this:

So, even though I migrated this spec to 2014, it still looks in 2012 locations. After modifying and saving it, the file looks like this:

After closing the file in the xml editor and switching back to 7zip, you should get this dialog, where you click ok.

Close 7zip after you have made the changes. The spec editor will not open the spec if 7Zip has it open.

Assuming the files exist in the new spot and are in the correct format, you should not get warning dialogs.

Out of the box, the line number tag, size and spec are called out on isometrics.

One of the most frequent requests we get is to alter that line callout to match our line number. The difficulty lies in the fact that in the isoconfig.xml, when you tell it which fields to place, you can’t mix and match the component properties with the line group properties.  So, for example, setting up a line number like this Size-Service-Number-Spec, seemed impossible (where size and spec are the component properties.

However, thanks to some recent insight from the forums thanks to Bernd Gerstenberger, we have a workable (though complicated) solution.

The key to our scenario is to use a little know feature called calculated properties (PLANTDEFINECALCPROPERTIES).

Overview

We still have to work with the limitation of placing component fields separately from line group properties, but by using the Calculated properties option, we can create a new field/fields that includes our line group properties in the order we want.  We do have to workaround a limitation in that calculated properties cannot include the size property (from components).

What is a Calculated property?

Before diving headlong into this, we need to understand what a calculated property is.  A calculated property is a combination of existing properties for a class.  Calculated properties may be defined and edited using the PLANTDEFINECALCPROPERTIES command.

Below is a screenshot of a calculated property called “LineDisplay” that was created on the P3dLineGroup class.

In the Data Manager, the LineDisplay Property looks like this:

The format of the calculated property is important.  Typically, everything should be wrapped in the ToString function.  The double bars “||” is a symbol that indicates concatenation. You use single quotes to wrap text.

So, the value used for the LineDisplay property is this: ToString(NominalSize) || ‘-‘ || ToString(Service) || ‘-‘ || ToString(Number) || ‘-‘ || ToString(NominalSpec)

I’m sure I overuse ToString, but it can’t hurt anything.

So, how does this help?  Bernd’s post above shows how to include any component property in an annotation.  So, now we can create a property similar to LineDisplay on our PipeRunComponents class.  The only difference being that due to limitations in calculated properties, we can’t include the Size property.

So, I created a property called LineSuffix on the PipeRunComponent class as shown below:

In our model, the property looks like this:

Now, we need to map the property so that we can use it in our isoconfig.xml.

Open the iso.atr, in the style you want to modify, and add a row that  maps the PipeRunComponent.LineSuffix property.

Now, in the isoconfig.xml, navigate to Themes > Theme (default) > Annotations > AnnotationSchemes > LineNumberScheme.

The attributes we are interested in are the Format, ComponentFormat, and ComponentFields.

In ComponentFields, we indicate that we want to make two properties available (Size and LineSuffix).

In ComponentFormat, we indicate that the format will that the first item (Size) and separate it from the second item (LineSuffix) with a dash.

By default, the Format property puts the LineFormat items first (think Line Group properties), so we use {1} which will only include the ComponentFormat properties. Save that and generate an iso.

Magically, we have the physical size called out with the line number format that matches the LineDisplay property.

Following up the last post, a client asked if there was a better way to put notes on supports other than using the message.

Because we can use any property in our isometrics, this post is going to show how to call out the comment field on the iso (if it’s not blank).

To do this, we will map the comment property, create a filter for non-blank supports, and then create a new annotationscheme to put the callout on the iso.

Map the Comment Property

Open the Iso.atr in the isometric style you are going to use, and add a row under BOM-ATTRIBUTES for EngineeringItems.Comment.

Create a Support Comment Filter

In the isoconfig.xml, add a filter like this:

<Filter Name=”SupportComment” Value=”Type=&apos;Support&apos; AND NOT [Comment] IS NULL” />

This allows us to only have support labeled that have comments filled in.

Create a New AnnotationScheme

Under Themes > Default > Annotations > AnnotationSchemes add a new annotation scheme like this:

<ComponentScheme Name=”SupportComments” AnnotationStyle=”Standard” Format=”{0}” Grouping=”true” Alignment=”FlatHorizontal” LeaderStyle=”Always” Filter=”SupportComment” Fields=”Comment” />

This uses our mapped Comment property, and the filter to label supports.  The final output should look something like this:

One of the new features in Plant 3D 2014 is to use a custom view to create an orthographic. Previously, we were locked into the predefined views – top, left, right, bottom, front, back.

Per the screenshot below I have created a model that has some pipe at an angle. Notice that my ucs is set to World (as proof that the line really is skewed).

After clicking the create orthographic view button, here is the view of my model.

To start setting up my custom view, I need to create a new ucs that is aligned with my pipe. Click the WCS icon and select new UCS.

Use osnaps to get the UCS aligned to the piping.

Then click the navcube to rotate to the isometric view that you want, make sure the Unnamed UCS (which you just made) is selected.

Below are the results

Make sure the current view option is selected in the ribbon:

Click OK to generate the ortho:

For those who have to send a SQL Server project to the field, (or to us for tech support), here is the workflow.

Create a new project in Plant 3D:

Check Copy Settings from existing project, and locate and select the project you wish to send:

On Page 5 of the wizard, choose SQLite local database.

Click Next and then Finish to create the project.

Click out the isometric drawing directories (we generally do not need generated isos). Clean out an extra specs that are not needed to reproduce issues.

Use the Copy Drawing to Project option to bring in drawings from the SQL Server project.

Once you have the new project cleaned and updated, zip it up using your favorite zip application (7-Zip).

Ok, feeling kind of silly for missing one of the biggest small improvements.  Until 2014, we didn’t have a good way to update specs from catalogs, as the descriptions would get overwritten with the catalog descriptions.

In 2014 we have a new settings dialog that allows us to control which properties get updated when running the spec update.

Typically, you should uncheck the Long Description (Family) and Long Description (Size) properties.

If you use the property overrides to create spec items, you should also uncheck the Material, Material Code, and Schedule properties.

Now, we can all enjoy building smaller catalogs! Unless you’re into part numbers of course…