Since the Plant Store is open, we have some plugins that will be available over the next few weeks. The first plugin that is available is Rename Project.
Originally we posted on the subject here:
http://www.pdoteam.com/2011/11/changing-the-project-name-in-plant-3d/
and here: http://www.pdoteam.com/2011/11/changing-project-names-in-plant-3d/
Now we have the plugin in the Plant Store here:
View the Video here:
Several people have asked about migrating our existing products to 2014. In addition, we have some more plugins that are going to be coming available in the new Plant store.
This applies to the plugins currently sold in our store:http://www.pdoteam.com/store/
Create BOM
PDO Extended Fields (1.0)
Iso Config XML
First, future plans. As the Create BOM functionality is included in Plant 3D Extension 1, we will not be updating or revising this plugin. However, below we will show a tip that you can use to allow it to run on 2014 (and higher) if you wish.
PDO Extended Fields is getting some updates to work with 2014 better, and we will be adding a couple more properties (I had a request for a weld length property). In addition, we now have a license manager which is integrated into this (and the rest of our Plant 3D store plugins). So the version that is going to be available in the Plant store will be PDO Extended Fields 2.0, and you will have to purchase that from the Plant Store. The xml tip below will work, but the To/From information in the PnIDs doesn’t work right in 2014, without the 2.0 version.
I haven’t decided what to do with the Iso Config XML editor, if I get requests, I’ll put it in the Plant Store, but for now, the xml edit will work to load it in 2014.
Since there have been no major api changes a simple XML edit can be made. First locate the ApplicationPlugins folder and navigate to the plugin you wish to modify.
Plugins installed on a per user basis are stored in %APPDATA%\Roaming\Autodesk\ApplicationPlugins\
Plugins installed for all users (and all app store plugins now) are saved in C:\ProgramData\Autodesk\ApplicationPlugins\
Each *.bundle folder will have a file called PackageContents.xml which instructs AutoCAD on what to load and how to load it. Open the file in a text or xml editor:
Locate the value SeriesMax=”R19.0” This indicates that the highest version of AutoCAD to load the plugin is AutoCAD 2013. To allow 2014 to load it change the seriesMax to R19.1, and restart AutoCAD.
Right now in the approval queue, we have several plugins. The Assign Properties plugin has just been cleared, and the Rename Project plugin is available too.
A list of all of our plugins are available here:
http://apps.exchange.autodesk.com/PLNT3D/en/list/search?facet=author/ECAD%2c+Inc.
The plugins in the queue right now are:
DataLink – a method for writing all the Plant 3D data to a Navisworks model.
Dynamic Parts – a way to place dynamic nipples in a model (so you don’t need to create a nipple for every size and end type).
Fix Connector Line Numbers – a fix that updates all connectors in a model (welds) to match the line number of surrounding components.
PDO Extended Fiels 2.0
Selection Lists – Export/Import Selection Lists to Excel, Link a column to a selection list value to display the description, use the Plant 3D spec list in PnID, and synchronize selection lists between Plant 3D and PnID (more articles and a video to come on this one).
We are also working on several other ideas, and we’d love to get your input!
And I do mean, perfect. Line lists have troubled several CAD programs, but now you can get automated line lists from your P&IDs without having to clean them up.
Our Extended Fields plugin is now available in the store: PDO Extended Fields
In addition to updating it for 2014, several other features have been added, with more to come.
Today’s article will highlight the Line List features.
For some reason, P&ID developers (not just Autodesk’s) seem to think that a line list = a list of line segments, or this:
However, when as a drafter learning piping design, I submitted a similar list to the project manager, things didn’t go so well for me.
So, how do we turn this (above), into this (below).
Caveat: This report was created based on the out of the box, sample project which has lines that don’t connect.
The information that gets put into a line list belongs at the Pipe Line Group class level, not in the Line Segment class. For example, design pressures, temperatures don’t vary by line segment; they change with the line group. You need to add any custom properties that you want to see in your report to the Line Group class.
With the PDO Extend Fields plugin, click the Add Fields button to add the EquipmentFrom, EquipmentTo, RelatedDrawings, and manual update fields.
While this step can be done manually, using the PDO Extended Fields plugin simplifies the process.
Click either the P&ID Fields button, or the All Fields button to update the line group data:
Now we have to configure a line group report to display the line group properties.
In the report creator, create a new report based on the Linelist.
Call it Line Group List.
Click Edit query.
Remove the Pipe Line Segments class and add the Pipe Line Group class. Click Ok.
In the report configuration dialog, click Edit Report Layout.
Drag and drop the columns as follows
Tag > Pipe Line Group_Tag
From > Pipe Line Group_EquipmentFrom
To > Pipe Line Group_EquipmentTo
I removed one of the insulation columns, and renamed the other one Drawings.
Drag and Drop Pipe Line Group_RelatedDrawings onto that column.
In addition to automatically populating the fields, you can set individual fields to manually update.For some OPC’s or lines you may want to indicate a group of tanks (vs listing each tank). Simply check the manual update property, and whatever change you input into the Equipment To or From will not be overwritten.
Recently we published a new plugin in the Autodesk Plant App Store: Selection Lists
View all of our plugins here: ECAD Apps
Here are the main features of the selection list plugin:
Display the description of a selection list in a property
Use a selection list in PnID and Plant (Selection list Sync)
Export/Import selection lists to Excel for editing
Import the list of specs from plant 3d for using in PnID.
We have a video showing the plugin in action here:
For the last year, we have been working to streamline the process of converting a CADWorx model to Plant 3D. We are now at the point where we can take advantage of some in-house development tools for converting models. We are excited to announce that we can now convert CADWorx models to Plant 3D models! What does this mean for you?
The price of the conversion will be based on model complexity, model size, and number of specs. Please Contact Us to learn more about pricing or the conversion process. What is the conversion process?
At this point we only have the ability to convert piping, but you can retain the steel and equipment models, and use our properties palette while within Plant 3D. http://apps.exchange.autodesk.com/PLNT3D/en/Detail/Index?id=appstore.exchange.autodesk.com%3acadworxpropertybyecad%3aen
The first stage of the process, converting specs has been hashed out by our team for various clients. We have a couple blog articles about converting specs here: http://www.pdoteam.com/series/converting-cadworx-specs/ As with all modeling, garbage in = garbage out, so the most import piece of converting the model is to get the specs right. In order to verify a successful model conversion, we will convert your specs to populate the CADWorx model with correct part data.
With the specs successfully converted, we can proceed with the model conversion. In order to successfully parse your line number, you should include your CADWorx configuration file. Files necessary for the conversion process are listed here: http://www.pdoteam.com/converting-models/cadworx/ To convert the model, we use some in-house tools to align the components correctly, which lets us select CADWorx items, 
and places Plant 3D components at the correct locations. 
The final step in the process is to fix any disconnected joints, or items that don’t convert. Often CADWorx users may change the description of any item on the fly, or they may modify the spec after a part has already been placed in the model. In these scenarios the parts have to be individually converted since they will not match the converted spec. In some scenarios, piping may have to be re-routed if it cannot be connected. For example, if lines didn’t connect in CADWorx (and wouldn’t run through Isogen), Plant 3D will not be able to connect them either. For these issues as well as troubleshooting the actual conversion, a log file is generated. 
Using the information (CADWorx Object Handle) in the log file, we can quickly locate items in the model for fixing. 
Please Contact Us if you need more information about converting CADWorx models.
When connecting Plant 3d 2014 to Autodesk Vault, you may get an error like this:
The issue is from Plant 3D 2014 working off of a different Autodesk.Connectivity.WebServices than AutoCAD 2014. To resolve the issue, I copied the dll (Autodesk.Connectivity.WebServices.dll) from C:\Program Files\Autodesk\AutoCAD 2014 (making a backup) to C:\Program Files\Autodesk\AutoCAD 2014\PLNT3D\.
At that point, I was able to create and use a new project in AutoCAD Plant 3D 2014 with Vault.
Every now and then, an idea strikes when you go back and look at an old problem. This morning, a potential solution occurred to me as I was going through some old emails.
Several clients have asked if they can have the instrument tag separated out in the instrument bubble on an isometric. Until I learned more about the iso.atr file, no options presented themselves.
While there are a couple of ways to approach this, here is my personal favorite.
The steps are:
One of my favorite commands is quickly becoming PLANTDEFINECALCPROPERTIES. Since we’re talking specifically about instrument bubbles, we will create a property on the instrument class. The property value is Area || ‘\p’ || Type || ‘\p’ || LoopNumber. To the isometric engine, \p means start a new line, so that is the crux of our new feature. The reason I used a calculated property is that I can redefine it at a project level and use it in any iso style (that references the IsoTag property). Otherwise, if my instrument tag format changes, I have to modify all of my iso styles as well.
Open the Iso.atr file in the style you are going to modify, and add a line mapping the IsoTag property we just created. Save the changes.
In the isoconfig.xml, navigate to Themes > Default Theme > Annotations > AnnotationSchemes > ComponentScheme (InstrumentTag) . Modify the format and the Fields to match our new property name.
Now if you have a model with a tagged instrument your generated iso will call out the instrument with a multi-line bubble.
I have tried to figure this particular issue out for a couple years now.
When routing from a pump discharge, you frequently want to get the BOP to a specific elevation like 7’6” or something. Up until last week, I never had found a good way to do that. I’m sure some have figured this out, but I’ll post this for those of us that haven’t.
While doing to onsite work with Sigma Engineering and Construction, that question came up. I know that in the past, I have used the route from BOP and changed the elevation, but it didn’t seem to work consistently.
It turns out, there is a little trick to it. Most of the time, we start routing off of a pump discharge like this.
However, when trying to hit a BOP, the program bases the change in elevation on the compass being flat. So, to hit the correct elevation, first change the compass to flat.
Then, toggle the routing to BOP.
After that, you can use the elevation option to enter your world elevation.
Don’t forget to switch back to COP, otherwise you won’t be able to connect to pumps or other pipes. And yes, I say that mostly as a reminder to myself.
One semi-frequent question is “how do I display underground piping on orthos?”
The easiest way in 2014 I have found consists of a few steps:
In this model I used a box that has a height of 1/4” to represent grade.
For the below grade viewport, put the top of the view box at top of grade.
Use the all hidden lines option.
Use save ortho cube to easily come back to these settings.
Generate the view and place the viewport. Add dimensions and annotation.
Use the settings saved in the previous ortho cube.
Set the bottom of the view box to top of grade and raise the top of the view box to show everything.
Generate the view showing no hidden lines. Annotate and dimension the above ground viewport.
Move the above ground viewport, annotations, and dimensions to align on top of the already annotated below ground viewport. You want to do the annotation and dimensioning first, because when viewports overlay, AutoCAD may have trouble identifying which viewport you are trying to annotate in.
While our blog has been pretty quiet lately, I have been working on some other documentation for AutoCAD. We partnered together and will be releasing a new book (it’s only in pdf form) called Tailoring AutoCAD P&ID and Plant 3D (free!).
The book is laid out with a couple of goals:
This books is a companion of De-Mystifying AutoCAD Isometrics meaning that it does not cover material that is already covered in the Isometrics manual.
In addition to be a compilation of several documents that were frequently given out, Tailoring AutoCAD P&ID and Plant 3D includes content to bring the pieces together.
I hope you find great value from the book, and feel free to contact us with any comments!
I’ll be sure to post when the pdf is available.
Frequently we get asked how to change the color of text in AutoCAD Isometrics Bill of Materials (BOM). By default the text color looks like this:
Go to project setup, Isometric DWG Settings, Title Block and Display, Setup Title Block.
The Bill of Material Table is an AutoCAD table, so we need to select the first row and then set the Content properties to unlocked.
Then we can change the text color to something like ByLayer, or what ever value you want.
When finished, lock the content and format.
Generating the iso again will reflect the changes.
One question we get fairly regularly is “how do I create dynamic parts in Plant 3D?” While the custom parts palette is powerful, for frequently used shapes, it is cumbersome.
The best way to insert standard, modifiable parts is to create them in the custom parts spec (CustomParts Imperial or CustomParts Metric). This spec is modifiable from the spec editor, and you can change information after the component has been placed.
You can modify parts in the spec, or add new ones from the custom parts catalog.
In the spec viewer, choose the custom parts spec, and locate the modified item.
After placing the part, you can modify the properties and end types as needed, but the default values will come from the spec.
You can also change the spec to match the existing line.
You should use the custom parts spec for items like relief valves, control valves, or instruments so you can predefine symbol skeys, types, and dimensions while allowing the part to remain configurable after being inserted.
One of my favorite features of AutoCAD P&ID and AutoCAD Plant 3D is how sharing drawings and/or projects is managed, in a word seamlessly. The topic is discussed here [http://docs.autodesk.com/PLNT3D/2015/ENU/pdf/Tailoring_AutoCAD_PnID_and_Plant_3D.pdf#page=33], but this series will take a more in depth look at it.
First, we should cover sending projects. For projects based on SQLite (the default database option), sending projects is simple. You can simply zip the entire project folder. From there you should have included everything, if you are using the default project format.
Zip a project folder (7-zip shown)
If you are using any external locations, like a network spec folder, or templates, you will have to add those to the zip as well.
Here are a list of items to verify that you have included:
1. Piping Specs
2. Templates
3. External References
4. Tool palettes (mandatory to use custom P&ID symbols)
Of course the amount you include should be governed by how much you want the user to modify. If someone is only looking at the P&IDs, you should only send them P&ID necessary items.
Using SQL Server of Vault complicates matters a little, but the general process is the same. The core of the issue is that you won’t be giving the user access to your server, so you have to get the data into the SQLite project format. If you will be giving the user server access, the procedure is the same as the first section.
For SQL Server the steps will be as follows:
1. Create a new project based on the SQL Server project.
2. Use copy drawings to project to bring in P&ID, model, and ortho drawings.
3. Zip the SQLite project using the same methods as the first section.
In the new project wizard, select the SQL Server project as a reference.
Reference SQL Server Project
On the database setup page, you must select SQLite database.
SQLite Database selection
After the project is created, you have to bring the existing drawings into the new portable project. To do that, use the copy drawings functionality found within the P&ID folder, 3D model folder, and the ortho folder.
Copy P&IDs and 3D models
Copy orthos
Make sure to multi-select to bring in several drawings at once. Do not open any drawings until you have copied all of them into the project, or you may lose off page connector information.
Once the copy process is complete, you may zip the project and include extra files per the first section.
Recently I had a request to create custom drawing names for isometric drawings.
Here is what the client wanted to get for his isometric names:
Size-Spec-Service-Line#-Sht#-Rev# (ex. 2-CS150-FL-0500-01-R0, 2-CS150-FL-0500-02-R0)
My first discovery was that you cannot use multiple properties in the FileNameFormat, PrefixModelProperties, ModelProperty, Name.
This apparently causes an issue and results in seemingly random letters to be used when naming the file or in some cases I’ve also seen where the program just ignores your prefix altogether
To get a full prefix to work we’ll need to start off by opening a Plant 3D drawing in your project. Once you are working on a drawing in the project use the PLANTDEFINECALCPROPERTIES command to open the Calculated Properties Manager. Dave Wolfe has written an article that mentions this tool in the past. http://www.pdoteam.com/2013/07/complex-line-numbers-in-isometrics/
Select the Piping tab to create a new property in the 3D environment. We will make a property to be used for you line groups, so select P3dLineGroup under Class Definitions.
To the right you will need to specify a name for your new property. I called my property thisone, but you can name it something more specific. Once you have named the property you need to specify the type of property. In this case I’ve selected string.
From here I am just going to have to specify what properties to use when building our calculated property.Each property needs to be converted to a string and then added to the next part with the || button. If you want to add a delimiter or other text you need to use an ‘ on either side of the added text.
Here is what I ended with:
ToString(NominalSize) || ‘-‘ || ToString(NominalSpec) || ‘-‘ || ToString(Service) || ‘-‘ || ToString(Number)
If this prefix needs some adjusting you can also add in the properties and the functions by double clicking on them from the tree view below our property. The buttons can also be used to help create your calculated property. The || button is used to combine one string property to the next. If you want to add your own delimiter between strings use apostrophes around the text. Ex. ‘-‘ will add a hyphen as a delimiter.
Once you are finished building your calculated property hit the Apply button.
Now that I have the property made I want to make sure it is populated correctly. To check our values we need to open the data manager and use the Order by Area option from the bottom left corner of the data manager.
Expand the area you are working in. Select the Pipe Lines breakdown and you’ll see all the pipe lines in that area. Scroll to the end and you should see your new property. If some of the calculated properties are not displaying scroll back to the right and make sure the values are all filled out.
Now that we have our prefix working we just need to add it as an attribute to the Iso.atr file. I normally edit the file using Notepad. As you can see below we are just adding a line assigning an attribute with the newly created property. In my case the property is called thisone, but you should replace thisone with the name of your property. If you have used spaces in the property name replace the spaces with underscores as you can see they have done with properties such as Project_Name.
Keep in mind you’ll need to adjust each Iso.atr file for every iso style just like the IsoConfig.xml.
Now that the attribute has been made we can use the property in the IsoConfig.xml. If you are using foxe to edit the .xml expand IsoConfigDefinition, FileNameFormat, PrefixModelProperties, ModelProperty and change the Name value to the new attribute you created in our last step. In my case Attribute10.
Now with these changes we will have the prefix ready to be used, so when I save the .xml and run my iso I get something that looks like this:
This is a good start, but now we need to get the suffix to reflect the revision number as well as adjusting the delimiter.
To show the revision number we need to adjust the FileNameFormat, SuffixModelProperties, ModelProperty, Name value to REVISION then change the Delimiter to -R
After these adjustments I get something like this:
Now the last adjustment my client wanted was to make the sheet numbers two digits long. To do this we had to set the FileNameFormat, SheetNumber, NumberOfDigits to 2.
So this is our final results:
The only issue with this part is that if there is only one sheet the 01 sheet number does not appear.
Today we have a client who has filled in the Item Code property in specs and catalogs, but needs items with different sizes to appear on separate rows. By default, they are combined like this:
I learned something about how the Columns are used in the isoconfig.xml but I haven’t had a using to modify them until now.
For this particular style, the client is using Shop and Field sections, so I’ll be modifying those. To make this work for every BOM type, you should modify all of the BOM Aggregated Lists.
Now for the details.
In the isoconfig.xml, the isometrics uses the Data>Aggregated Lists section to control the data that populates the BOM tables.
To test the fix, I added the Size column to the AggregatedList (ShopMaterials) > Groups (FITTINGS > Columns.
Even though the sections don’t display separated in the BOM, Plant still sorts by the group to populate the table. To fix the rest of the AggregatedList, you should add the Size column to each of the groups. To fix the rest of the style, you should add the Size column to all of the Groups for the Materials and Field Materials Aggregated lists. The rest of the aggregated lists are used for the cut list and weld lists, and aren’t of a concern in this scenario.
The fixed output looks like this:
AutoCAD P&ID and Plant 3D also handles cases where properties or classes do not exist in a current project setup.
In this scenario, PID001 is from a project that has additional properties and some extra ball valve classes. When using Copy drawing to project to bring PID001 into a new project, this dialog is displayed warning us about missing classes and properties.
After that dialog displays, error dialogs for classes that do not exist display.
At the end, you can click to see a log of conflicts.
As is clear from the list, properties are not listed. So, any properties that are in the drawing, are ignored if they don’t match the project.
Mileage will vary as far as symbols that are not in the project. The symbol won’t be included in the project as intelligent items.
I have been curious about how custom parts work for a while. For example, you can put in a custom part from the spec view palette, and it will be dynamic. But if you put a part from the base catalogs in the custom parts spec, it wouldn’t work.
While at AU 2014, I discovered a little trick. It turns out that what makes custom parts special is the Component Designation property. In the spec, all of the custom parts have Component Designation = Custom. You can set this property on any part in any spec and the program will allow it to be changed dynamically.
Here is what the inserted part looks like:
The only wrinkle I found is that while the graphics change and the valve gets longer, the property for Length does not. However, this would only affect the reports, as the isos show the correct dimensions.
My recommendation is to use this feature on control valves, relief valves, and other potentially changing parts, which will give you the flexibility of using default catalog items dynamically within any spec.
Pretty regularly I get asked by clients what they should get for a laptop. So, here are my 2015 recommendations. While this is geared towards AutoCAD, these recommendation exceed the basic requirements for most Autodesk products, and should provide good performance for users. Note that because mobile video cards are not certified, you will not find certified drivers for these products. However, the card chosen is based on a certified video card.
Processor – You generally want to go with the fastest processor for your budget. AutoCAD is single core, so the processor speed has a big impact on performance.
RAM – Due to the 3d graphics getting enhanced, file size will remain the same while the number and quality of object increases. This will hit the RAM and Graphics cards harder, so splurging here is a must. Also, more people are working with point clouds which tend to be large.
SSD and HDD. I’m a big fan of installing key programs on the SSD and maintain bulk file access on the HDD. If you do have the money, buy the largest SSD available, but for our purposes I pretended to have some budget constraints.
Screen Size – While 17.6 is nice, I’ve traveled with one, and it is not fun. I chose 15.6 assuming the laptop would actually have to be moved by a human.
M3800 vs M4800 – The M3800 restricts us on the processor speed and video card, so I only chose it for the low end solution.
Hotdog: Dell Precision M4800 – Listed at $3786.50
Solid mediocre: Dell Precision M4800 – $2534.20
Lowering the bar – Dell Precision M3800.
Ok, so this is more of a personal issue than anything else. For the last little while, I’ve been unable to edit equipment nozzles without the dialog disappearing and pipe starting to get routed.
If this happens to you, make sure GRIPSUBOBJMODE = 0, and your life can go back to normal.
Some of our clients like to have the insulation display along the pipe run in the isometrics. In order to facilitate insulation and heat tracing line work being shown, the Insulation Spec and Tracing Spec properties must be filled out. Since these are separate properties from the Insulation Type and Tracing Type properties, most clients want to only fill out the Insulation Type or Tracing Type properties. There are two main hurdles to overcome, first that while you can add the acquire property to the insulation spec, for some reason, it doesn’t fill out. Second, by default you can’t remove the InsulationSpec or TracingSpec properties to add your own.
1. Make sure the Line Insulation Display is turned on by turning modifying the isoconfig.xml
2. With the project closed (all users out), open the project Piping.dcf database in either SQL management studio (if you are running SQL Server, or SQLite Expert).
3. Locate the PnPColumnAttributes table, and enter P3dLineGroup for the TableName filter and ISREMOVABLE for the AttributeName.
4. Set the TracingSpec and InsulationSpec AttributeValve properties to TRUE.
5. Open the project in Plant 3d and go to project setup. Now you can remove the InsulationSpec and TracingSpec properties.
6. Since we can’t use Acquisition Properties, we have to use calculated fields to get our Insulation Type and Tracing Type in. Start the PLANTDEFINECALCPROPERTIES command at the command line. Switch to the Piping tab, select the P3dLineGroup. Enter InsulationSpec for the property name and select String from the dropdown. You can double-click or type in the Function and property names. Enter ToString(InsulationType) in the expression box and click Apply. Repeat the process for the TracingSpec property using ToString(TracingType) for the expression.
7. Verify that selecting the insulation or tracing type fills out the properties using the Data Manager.
8. Running the iso should yield a similar result to this.
