I am creating iso's currently and noticed that if I iso a line that has a catalog block it won't see the block and cause an error on the iso and create 2 pages. If I take the same block and create a custom part, I have no issue.
Attached is1 line iso that has been generated with a check valve that has been blocked in a catalog (2 sheets) and the same line that has been blocked through the plantcustomparts command (1 sheet).
The facing and pressure class codes match. This happens to every catalog part I have made.
When you create a custom catalog part you have to make sure it is assigned a valid SKEY (the symbol that isogen uses). Have you checked this on your new components?
I have to go from memory on my explanations of the dialog (cuz my Plant 3D software is at home...and I am not), but...
1) Go to the Catalog editor tab
2) Select your components in the lower section (catalog browser)
3) In the upper section, on the "general properties" tab, on the far right are the "component properties"
4) Scroll down to the bottom of that list
That's where I remember it...
Yes, that's where it is (image attached). Using plantcustomparts is a good way to test the block based geometry before adding it to a catalog. It also provides candidates for Iso TYPE and SKEY values that can be used when creating the catalog component.
A quick place to start is IsoSkeyAcadBlockMap.xml. You can also load IsoSymbolStyles.dwg and BEDIT to see the complete list and symbols. As you assign SKEYs, locating a similar part in the catalog might be the most convienient method.
We don't document the list, but you can export the catalog to excel, Unprotected Sheet, and Remove Duplicates from the Content Iso Symbol Definition column.
Do you know where I can find these files. I can not find any of these files or the drawing when doing a search through windows explorer whether it's in the plant3d directory or in the project directory.
The Iso symbol mapping and library settings are project specific. You can find the files in the Isometric folder in each project (for example: C:\SampleProject\Isometric\IsoSkeyAcadBlockMap.xml).
You keep referring to an ISOMETRIC folder. The closest thing to that in my project folder is an isogen folder which does not contain the files.