Corporate Utility - Woman on rooftop

MasterGraphics Weblog

Archive for September, 2007

Improve workstation performance when running AutoCAD MEP

Thursday, September 27th, 2007

Discover tips and techniques from Autodesk that can improve workstation performance when running AutoCAD MEP. This paper explores methods of maximizing workstation performance when using your CAD application on large projects.

For Project Managers and CAD ManagersThe following tips and techniques are for project managers and CAD managers responsible for rolling out software releases, establishing requirements, managing projects, supporting CAD users, and so forth.

Work in the Latest Release

Each new release of AutoCAD MEP is designed to handle larger and morecomplex projects. Each new release contains significant advances in performance as well as new features and enhancements that further streamline work processes. These improvements enable you to work faster and reduce the time it takes to perform complex tasks.

Standardize on Drawing Format

Over the course of a project, team members use different versions of AutoCAD, AutoCAD Architecture, or AutoCAD MEP software to create data, especially if the project uses drawings from a client or subcontractor. However, these drawings are converted to current file format on the fly every time they are opened or referenced through an external reference file (xref). Opening and saving earlier-version project drawings in the current release eliminates this time-consuming conversion, thus freeing resources and shortening the time to open the drawings.

Manage Proxies

Drawings may contain proxies of custom objects created in other AutoCAD-based applications or third-party software. These objects require that proxy graphics be turned on in these drawings, which can significantly increase file sizes and the amount of time required to open those files. For example, a 3.9 MB drawing seen recently in Autodesk Product Support was reduced to 1.8 MB just by turning proxy graphics off.

Avoid Complex MvParts

When developing content for your catalog, carefully consider the complexity of each new part. For example, the round louvered diffuser shown below is much too detailed for most MEP work. It uses curved surfaces for interior vanes, shows all the ribbing between the vanes, and has a neck with an internal curved surface that’s hidden when connected to your ductwork system. This depth of complexity taxes the resources of your workstation for little gain, requiring a high level of system resources every time you need to change views.

Use MvParts that convey the basic intent of what the equipment represents, and avoid making MvParts more detailed than they need to be.

Use Project Navigator Effectively

When using Project Navigator, do not manually insert xrefs into your drawing using the Reference command on the Insert menu. Instead, use the shortcut menus in Project Navigator to attach or overlay reference files within the project.

In versions prior to Autodesk Building Systems 2005 (SP2), drawings that are manually referenced into a project are not resolved in the file structure created through Project Navigator. Accordingly, the referenced path of manually inserted xrefs may be lost when paths change, resulting in missing or incorrect reference files.

Overlay xrefs rather than attaching them. Drawing files that use xref overlay will not reproduce that overlay when it is referenced by another drawing. Drawings with attached xrefs will reproduce that xref, which can lead to duplicate or circular xrefs and confusion as to what actually is in the drawing. This can tax workstation resources and affect performance. For example, a data set recently received by Autodesk Product Support contained drawings with attached xrefs that resulted in nine duplicated referenced drawings.

Avoid Hidden Shares

Earlier versions of Autodesk Building Systems (pre-2006) support only a full UNC path with no mapped drives and no relative paths. Best practices suggest avoiding a project structure that points to hidden shares, especially if the project structure is sent to other members of the extended design team that might not have those same shares.

Manage Temporary Files

Temporary files are created as part of the “Enabled with Copy” demand load strategy built into Project Navigator. These files remain after a system failure or an aborted Project Navigator activity. Deleting the *.ac$ files in the Temp folder can reduce the time required to open most drawing files and significantly improve system performance.

Update the AutoCAD MEP profile to point all AutoCAD temporary files to a specific temporary folder separate from the standard Microsoft Windows temporary folder. Use a login script to clear temporary files on a daily basis.

Hardware Recommendations

Turn off the system’s hardware acceleration, update all graphic drivers to their latest version, and make sure your workstation meets the minimum system requirements for the release you are using. Minimum system requirements can be found in the installer menu and the help files.

 

For CAD Users

The following tips and techniques are for the everyday CAD user responsible managing drawings, adhering to CAD standards, coordinating designs with the extended team, creating construction documents, and so forth.

Use Purge Commands

At the end of a work session, use the purge commands—PURGE and BLDSYSPURGE— to clean up AutoCAD MEP drawings. For example, a 3.2 MB drawing recently came into Autodesk Product Support with complaints of poor system performance. Upon inspection, about two-thirds of the objects in the drawing were not being used (2,166 of 3,153 items). Purging reduced the drawing size to about 1.9 MB. Since AutoCAD MEP always verifies the location of objects relative to new objects being added, purging can dramatically improve system performance.

Use Interference Detection

Turn interference detection on only when you need it. For example, wait until systems are substantially complete and ready to be compared to other nearby systems in the drawing. AutoCAD MEP compares the location of each object to others in a drawing— an activity that uses a lot of system resources. Turning interference detection off when you don’t need it drastically reduces the time it takes to open any drawing.

When checking interferences on a color system scheme, create a new Layout tab and use the Page Setup manager to set all colors, other than the collision marker, to black. The result is a black-and-white screen with colored collision markers that are easy to identify.

Minimize Multiple Sessions

Launching multiple or concurrent sessions of AutoCAD MEP, or other similar third-party products built on AutoCAD software dramatically reduces system performance and possibly the system’s overall stability. Avoid this practice and adopt other work methods. If you cannot avoid multiple sessions, consider using your most capable workstations for these situations.

Let Processes Run Their Course

It is normal for some activities, such as loading xrefs, to take time. These processes need to run their course before additional activities can be initiated, such as dragging drawings from Project Navigator before it has finished loading previous drawings.

Minimize X-Clips and Live Sections

Live sections and x-clipping of xrefs are useful for working with the live model. However, too many x-clips and live sections can cause the drawing to load very slowly.

Use 2D Wireframe

With the high quality of AutoCAD MEP models, it is tempting to create walkthrough models in shade mode. Although such walkthroughs are great for visualizing the systems and their environment, shade mode, including 3D wireframe, taxes your system resources.

In complicated areas such equipment rooms, select the objects you want to view or work with and use the Isolate Objects feature to remove the surroundings. Not only will you see your work more clearly, system performance will greatly increase.

Manage Haloed Lines

Haloed lines generate a lot of additional data. Improve the time-to-open performance of any drawing by ensuring that the Increase Drawing Open Performance option is selected in the Building Systems Crossed Object tab in the AutoCAD Options. However, be cautious when selecting this option because it significantly increases your drawing file size.

Make sure you are getting the best system performance possible with haloed lines by ensuring that the Increase Drawing Open Performance option is selected. However, if you need to email drawing files or save them over a slow network, deselect this option to decrease drawing file sizes.

Manage Duct Hatching

It’s normal practice to use duct hatch on systems marked for demolition. However, hatching increases memory use and slows down all display-related activities such as opening drawings, regenerating models, and switching views.

Posted in Building / AEC | No Comments »

Enabling custom sizing for AutoCAD MEP parametric parts

Monday, September 24th, 2007

To enable custom sizing for a parametric part

  1. On the command line enter AecbContentBuilder to open the Content Builder. Note: This command is available on the CAD Manager Menu in Building Systems 2007 or the MEP Common menu in previous versions.
  2. In the Getting Started – Catalog Screen dialog box, select the part that you want to modify and click the Modify Part Definition icon.

  3. Click the Options icon of the part that you are editing.

  4. Select the Custom Sizing Flag check box and click OK.

  5. Click the Save Part Family icon.

Not all parts are designed to have the Custom Sizing option enabled. Unexpected results may occur if you create custom sizes of such parts.

Posted in Building / AEC | No Comments »

Tool Palette Management in a Network Deployment

Monday, September 24th, 2007

AutoCAD MEP and AutoCAD Architecture use tool palettes differently than normal AutoCAD and the path setting in Options under the Files tab was designed only for use with the AutoCAD tool palettes. This path needs to remain as set by the system in AutoCAD MEP. Changing this path can result in problems. To share tool palettes among multiple users, you need to use the content browser to create shared tool palettes.

Concepts

Understanding a Tool Palette:
An individual tool palette contains the tools (buttons) that are displayed on a palette within ABS. The source file (*.atc) for an individual palette contains the following items:

  1. The name and command that is executed when a tool is selected.
  2. The path to any necessary support files required for the tool to function.
  3. Any settings specific to the type of tool. For instance, layer keys, overrides, and insertion behavior.

Right-click on different tools and look at the Properties for further tool properties.
Other items such as tool icons and source blocks are located in other locations and referenced as mentioned above.

Understanding a Tool Palette Library:
A library of tool palettes consists of multiple tool palettes contained in one folder located on either a local machine or a network. The support files to allow the tools in different tool palettes to function can be located in different places, as long as the paths are correct within each ATC file.

The library represents the tool palettes that can be used in a given ABS workspace. The actual organization of the palettes into groups is not contained in the library. These settings are maintained by the current ABS profile. The profile defines what palettes are available and in what groups they are placed.

Understanding a Tool Catalog:
A tool catalog is a library of tools and tool palettes that can be imported into the workspace or shared among other users. The actual tool catalog file keeps track of the locations of the items it contains, as well as the organization of these items.

Procedures

Preparing a Tool Palette Library for Deployment:
The CAD Manager or other managing user should configure the tool palettes as desired locally on their machine. This can include; creating new palettes that contain custom tools, moving tools from one palette to another for organizational purposes, redefining the settings for a given tool, adding tools for custom content, among other things.

The end result of this process should be that the tool palettes on the manager’s machine contain all the tools desired, and the tools are organized on the palettes.

Creating a New Tool Catalog in the Content Browser:
Content Browser will be your method for publishing and deploying tool palettes in a network environment. You will create a tool catalog that contains your tool palettes, publish that tool catalog to the network, and deploy it to users in the CAD environment. To create the tool catalog in Content Browser, complete the following steps.

  1. Open the Content Browser (AecContentBrowser in the command line).
  2. Create a new tool catalog by clicking on the create new catalog icon in the bottom left corner of the window ..
  3. You want to select the “Create a new catalog” option and name the catalog. You can choose to place the new catalog in any location. I would suggest the default location, as it will be easier to find this “source” tool catalog for later modifications.
  4. The tool catalog will be published to the network later in the process, so there’s no need to have this version on the network.
  5. If you would like your tool palettes to be grouped into categories when you deploy the tool catalog, you need to create a category for each group in your tool catalog. To create a new category, for example “HVAC Equipment”, right-click in the catalog and choose Add Category or click on the Add New Category icon in the bottom left corner.
  6. Categories are useful to organize your palettes into groups for organizational purposes. They also allow you to deploy a group of palettes into a new machine instead of one-by-one.
  7. You now need to transfer your tool palettes to the new tool catalog in Content Browser. With the correct category in your new tool catalog open in content browser, click-and-drag each of the tool palette tabs into content browser.

The tool catalog should now be populated with the tool palettes that you wish to deploy in the CAD environment. If you inadvertently place a tool palette in the wrong category, you can cut and- paste it into the correct category.

Publishing Your New Tool Catalog:
With your new tool catalog populated and organized properly, you’re ready to publish the catalog to the network for deployment.

To publish the catalog, complete the following steps.

  1. In the Home view of content browser, right-click on the new tool catalog you’ve created and select Publish ‘Your Catalog Name’.
  2. Choose to copy the catalog to another location. This allows you to place the catalog on your network, while leaving the original catalog on your local machine. Choose Next.
  3. Choose the network location you’d like to use for sharing of this catalog and the tool palettes contained within. Choose Next.
  4. You will now be prompted to set the path of all the support files needed for the catalog. Make sure the box for “Automatically copy tool dependent files into the above folder to be referenced by the published catalog” is checked. Choose a content directory of your choice. Choose Next.
  5. As explained in the concepts section of this document, there are support files that are needed in order for tool palettes to function properly. The process of publishing rewrites the paths for these support files to a location of your choice. The support files themselves are also copied to this location. This allows for the tool catalog to function by itself on the network.
  6. You now set the path that users will utilize to locate the tool catalog on the network. Both a UNC path and a mapped drive can be used. Make sure that the read-only box is checked. Also make sure that the “Set items not to be refreshable when drag/dropped into the workspace” is unchecked. Select Finish.
  7. Setting items as read-only prevents users from modifying the tool catalog on the network. This is helpful when manager seeks to control the CAD environment.
  8. Navigate to the tool catalog location on your network and set the master ATC file (yourcatalogname.atc) to read-only. This will prevent users from modifying the master file. In the previous step you set the files contained in the tool catalog to read-only. The tool catalog containing your tool palettes has now been published to the network. The support files for those palettes to function have also been placed on the network, and the paths to locate them have been rewritten. At this point your tool palettes are can function on their own and need to be added to the users’ Content Browser Libraries.

Deploying the Tool Catalog to Users’ Content Browser Library:
There are two different methods for deploying your new tool catalog to users’ content browser. The first is a manual addition.

To complete a manual addition, follow these steps:

  1. Open content browser on a user’s machine.
  2. Choose to add a new catalog.
  3. Choose to add an existing catalog and browse to the network location where you published your tool catalog. Select the master catalog file (yourcatalogname.atc).

The second method is to create a registry install file. To complete this process, follow these steps:

  1. Open content browser on the manager’s machine. Select your published catalog.
  2. You can confirm that a tool catalog is located on the network by checking the path to its location, which is located its properties.
  3. Hold the Shift key and right-click on the published catalog. Choose the “Convert to Registry File” option.
  4. Name the registry install file and place it in a network location that other users can access.
  5. Using the appropriate method for your network, run the registry key on users’ machines. The published tool catalog, and all the tool palettes contained within, has been added to the users’ content browsers.


Adding Tool Palettes to the Users’ Workspace:
Even though the tool catalog has been added to the content browser, the tool palettes it contains have not been added to the tool palette library for the workspace. To do this, complete the following:

  1. Open content browser and navigate to the networked tool catalog.
  2. Find the tool palette that you want to add to the workspace. Move your cursor over the i-drop icon and then drag-and-drop the tool palettes anywhere in the workspace.
  3. The tool palettes are linked back to the original network location. You’ll notice that there’s a small icon in the bottom right corner of the tool palette. If the user clicks on this icon the tool palette will be updated according to the published tool catalog.

This should import the tool palette from the network tool catalog. Now the user has a tool palette that’s automatically refreshed each time the program is loaded.

Configuring Tool Palettes in Users’ Machines:
You’ve now imported the tool palettes from the network into the program tool palette library. You need to set the tool palette grouping now using profiles. Remember, tool palette grouping is controlled by profiles.

As part of your management of the CAD environment, you’ve most likely created a profile that sets the various paths and settings that you would like to be active on users’ machines. Activate this profile and organize the tool palettes into groups as desired. If you’ve used categories in your Tool Catalog, then the palette grouping was added to current profile at the time of importing the tool palettes.

To customize the groups, you need to select the Customize option when you right-click on the tool palette border.

When you’ve set the groups to the desired grouping, export the profile for use by the users.

Deploying User Profile:
The link that’s used to start ABS or ADT contains a p-switch, “/p”, followed by the name of a profile to load at startup. This p-switch can be followed by a path to a network location as well. Place the exported file on your network and modify the program shortcut to point towards this ARG file. This allows for easy deployment of future changes to the profile, since the manager simply has to replace the ARG file on the network.

End Result
Using the procedures outlined by this guide, you should be able to organize and deploy tool palettes and profiles to groups of users.

Posted in Building / AEC | No Comments »

Annotation Scaling in AutoCAD MEP 2008

Monday, September 24th, 2007

A new feature that we have been waiting 30 years for is finally here with the new 2008 version. Annotation scaling allows you to plot annotation at the same height or size regardless of the viewport zoom scale. Annotation scales can be associated with annotative objects in AutoCAD MEP so that these objects can be sized properly for specific annotation scales in model space and displayed correctly in paper space. You can also toggle on or off the display of annotation objects that do not participate in the current annotation scale. You no longer need to have multiple objects in your drawing for each possible scale, and turn the scales that you are not using off.

 

Annotative AutoCAD MEP Objects
In AutoCAD MEP, labels are annotative objects if the corresponding label curve style is configured to be annotative. You configure a label curve style to be annotative in one of 2 ways depending on the type of style.

If the label curve style uses block graphics or flow arrow graphics, and Use Annotation Scale for Block is selected in the style, then the style is considered annotative. (As a convenience, this is selected by default when you select a block whose Annotative property is set to Yes, but you can deselect it.)

If the label curve style uses a text style, then the configuration of the text style determines whether the label curve style is considered annotative.

When you modify a label curve style to make it annotative or non-annotative (using the methods described below for block-based styles and text-based styles), all labels using the style are updated accordingly in the drawing. In the case of a block-based style, you cannot make the style annotative or non-annotative by modifying the Annotative property in the underlying block definition.

NOTE:Schedules are not considered annotative. Therefore, they do not scale accordingly when the annotation scale changes. When you insert a schedule into a drawing, it uses the annotation scale that is current at the time of insertion, and its scale does not change.

AutoCAD MEP Objects with Annotative Components
Some AutoCAD MEP objects are not annotative, but they have components that are (or can be) annotative. The following table lists these components.

All Disiplines

  • Rise symbols and drop symbols
  • View blocks of MvParts if Use Annotation Scale is selected in the corresponding MvPart style definition. You select this on a per-view basis on the Views tab in Style Manager.

HVAC

  • Flow markers
  • Annotation pattern on flexible ducts
  • Flow arrows on air terminals if Use Annotation Scale for Block is selected in the MvPart properties. You select this on the Flow tab in the Multi-view Part Properties dialog.

Piping

  • Flow markers
  • Annotation pattern on flexible pipes
  • Placeholder pipe
  • In Graphical 1-Line: rise symbols, drop symbols, in-line/anchored MvParts, and reducers

Electrical

  • Home runs, tick marks, and gaps on wires
  • Pattern on cable trays
  • View blocks of devices and panels if Use Annotation Scale is selected in the corresponding device style or panel style. You select this on a per-view basis on the Views tab in Style Manager.
  • You can use the conversion tools provided with the software to update large numbers of devices to be annotative.

Plumbing

  • Plumbing fittings
  • Plumbing fittings are always scaled according to the current annotation scale in model space.
  • Gaps on plumbing lines

Schematic

  • Schematic symbols.
  • Schematic symbols are always scaled according to the current annotation scale in model space.
  • Start symbols, end symbols, connections symbols, and gaps on schematic lines
  • You can use the conversion tools provided with the software to update large numbers of schematic symbols to be annotative.

The Hatch display component is not an annotative component of an object. Therefore, it does not scale accordingly when the annotation scale changes.

IMPORTANT:Objects with annotative components that are block-based (for example, flow arrows on air terminals, and view blocks for devices) are considered annotative based on whether Use Annotation Scale (for Block) is selected. The Annotative property in the associated block definition has no bearing on whether the object is annotative.

Annotation Tools with Annotative Properties
Use annotation tools to create annotation objects that respond to specific annotation scales. An annotation tool is a customizable AutoCAD MEP tool for adding the following types of annotations to drawings:

  • Multi-line text notes

  • Symbol-based notes with attributes

  • Reference keynotes

  • Sheet notes

  • Callouts

  • Multi-view blocks

  • AEC dimensions

Multi-view blocks derive their annotative properties from their block definition. AEC dimensions derive their annotative properties from their dimension style.

The following are annotation objects created by AutoCAD:

  • Text

  • MText

  • Dimensions

  • Leaders

  • Block References

  • Hatches

  • MLeaders

Specifying Annotation Scale
When you use AutoCAD MEP tools to generate AutoCAD objects such as leaders and callouts, these objects become annotative objects that respond to annotation scaling. When you generate Multi-view blocks and AEC dimensions, these objects are also annotative and respond to annotation scaling with respect to scale and location based on the current annotation scale.

The annotation scale is a setting associated with the model tab and paper space viewports and is also saved with model views. It is controlled by the CANNOSCALE system variable value which sets the current annotation scale. Different annotation scales can be assigned to model views and paper space viewports.

Annotation Scales and Viewports
When working in a paper space viewport, the annotation scale of the viewport controls the scale of the annotative objects created in the viewport. If multiple scale representations are supported, the annotative objects in the viewport are drawn and scaled based on the annotation scale without affecting the scale or display in the model tab or in other paper space viewports.
The viewport and annotation scales are synchronized when the annotation scaling controls are used. For example, when you change the viewport scale, the annotation scale updates to match the new viewport scale. However, as you zoom in or out of a viewport with your mouse wheel or by using the Zoom commands, the viewport scale updates while the annotation scale will remain unchanged.

Scale representations allow for the display of the same annotative object differently in different paper space viewports at the same time. Scale representations allow annotative objects to be drawn at different sizes based on the annotation scale. Each scale representation may also have different values for positional properties, such as a text string base point. The properties that can vary per scale representation depend on the object type.

Whenever an annotation object is identified as annotative as you add it to a drawing, the current annotation scale is added to the object as a participatory scale. AutoCAD MEP objects identified as annotative will scale to match the current annotation scale. The scale point is the insertion point of the block definition.

Any annotation settings within all nested text or dimension styles referred to by an AutoCAD MEP object, such as materials or component hatching, schedule tables, or stairs, will be ignored. Display properties for these objects do not respect annotation scaling.
Annotative objects such as diffuser tags now have a Scale Representation Location Grip. Use this grip to relocate the current scale representation instance. Use the Location grip to relocate all of the scale representations at once. If there is only one scale representation supported for a particular tag, only the Location grip is displayed.

Object Height x Annotation Scale x Annotation Plot Size = Model Space or Paper Space Height
For example, the model space text height for a text string when displayed in a viewport scaled to 1/4″ = 1′ - 0″ is 12″. Assuming an object height of 1 unit, the formula applies as follows:

1 x 48 x 1/4” = 12”

Blocks used by AutoCAD MEP callouts, title marks, and other kinds of annotation must be created relative to a single AutoCAD unit (either an inch or a millimeter, depending upon whether your working in imperial or metric units). Documentation content files, regardless of whether they are based on blocks or multi-view blocks have the additional requirement that they be inserted at a scale relative to your anticipated plot scale, and taking into account the “Annotation Plot Size” setting in the drawing setup dialog box. As a baseline, you can use one AutoCAD unit, and anything in the content file that is one unit in size will be the annotation plot size when plotted at the specified annotation scale. Everything in the block, including geometry and text, must be created relative to the single AutoCAD unit. The entire block is scaled proportionally.

Updating Legacy Annotative Objects
When you are working with previous versions of Building Systems, you can update appropriate objects in AutoCAD MEP so that they are annotative. This sections outlines the procedure for updating three types of objects: AutoCAD objects (text, dimensions, and hatching, for example), AutoCAD MEP blocks, and AutoCAD MEP multi-view blocks and AEC dimensions.

If you choose only one occurrence of an object to make annotative, only that instance of the object will be annotative. To apply an annotative property to all of the objects in a particular style, edit that style and assign an annotative property to all instances of that style. You can also enter ANNOUPDATE on the Command line to update the selected text objects. Leaders, MText, dimensions, and other objects are assigned an annotative property by this same procedure.

Updating Legacy AutoCAD Text to Annotative
Use this procedure to edit a legacy AutoCAD text style and add an annotative property. You can also use this procedure to update AutoCAD dimensions.

  1. Open the legacy Architectural Desktop drawing in AutoCAD Architecture.

  2. Specify the same annotation scale in the new AutoCAD Architecture drawing as in the legacy Architectural Desktop drawing.

  3. From the Format menu, click Text Style.
  4. In the Text Style dialog, from the Styles list, select the appropriate text style.
  5. Under Size, select Annotative.
  6. Click Apply.
  7. On the Command Line, enter ANNOUPDATE to update all annotative objects.
  8. Any text strings of the selected text style are now annotative.

Updating Legacy Building Systems Blocks to Annotative
Use this procedure to edit a legacy Building System blocks, such as callouts or titlemarks, and add an annotative property.

  1. Open the legacy Building Systems drawing in AutoCAD MEP.

  2. Specify the same annotation scale in the new AutoCAD MEP drawing as in the legacy Building Systems drawing.

  3. On the Command Line, enter BEDIT to open the Block Editor.

  4. In the Edit Block Definition dialog, select the block to edit, and then click OK.

  5. On the Properties Palette, under Block, select Yes for Annotative.

  6. On the Block Editor toolbar, click Close Block Editor and then save your changes.

Any blocks of the selected block style are now annotative.

Updating Legacy Building Systems Multi-view Blocks to Annotative
Use this procedure to edit a legacy Building Systems multi-view block and add an annotative property to each block for each view. You can also use this procedure to update legacy AEC dimensions.

  1. Open the legacy Building Systems drawing in AutoCAD MEP.
  2. Specify the same annotation scale in the new AutoCAD MEP drawing as in the legacy Building Systems drawing.
  3. On the Command Line, enter BEDIT to open the Block Editor.
  4. In the Edit Block Definition dialog, select the first block to edit, and then click OK.
  5. On the Properties Palette, under Block, select Yes for Annotative.
  6. On the Block Editor toolbar, click Close Block Editor and then save your changes.
  7. Repeat these steps for the remaining blocks of the remaining views of the multi-view block.
  8. On the Command Line, enter ANNOUPDATE to update the selected blocks.

The selected blocks now have an annotative property

Posted in Building / AEC | No Comments »

Anchor It!

Monday, September 24th, 2007

Once you investigate the use of anchors in your AutoCAD MEP environment, you won’t know how you ever lived without them. In this example we will use anchors to link switches to doors. If a door moves, the switch moves with it. If the door swing changes. The switch updates automatically.

First, let’s take a look at what anchors do for you and what types are available.

An anchor is a general linking mechanism within AutoCAD MEP. AutoCAD MEP and AutoCAD Architecture objects can be anchored to each other, enabling you to create a relationship between objects. Anchoring objects can be useful for positioning air terminals or light fixtures in a ceiling grid, or switches to walls or doors. You can choose from three types of anchors to attach building systems objects.

AutoCAD Architecture Anchors
You can locate these anchor tools in Content Browser / ADT Stock Tool Catalog / Parametric Layout and Anchoring Tools

  • Object anchors are used to attach AEC objects to another AEC object.
  • Curve anchors are used to attach objects to the base curve of other objects.
  • Leader anchors are used to attach nodes on a layout curve with a leader.
  • Node anchors are used to attach nodes on a layout curve or grid.
  • Cell anchors are used to attach objects to positions on a 2D layout curve or grid. You an also attach cell anchors to 3D volume grids.
  • Volume anchors are used to attach objects to a 3D volume grid.

AutoCAD MEP Anchors
You can locate these anchor tools in Content Browser / ABS Stock Tool Catalog / Common / Common Items

  • Curve anchors are used to attach objects to a base curve, typically the centerline of other objects.
  • System anchors are used to attach objects to a system run. Anchored objects can be moved along the entire run to other runs assigned to the same system.
  • Reference anchors are used to attach objects by reference to other objects, such as attaching an end-of-line schematic symbol to a schematic line. When the symbol is moved, the line maintains connectivity and is stretched to the new location.

Anchor Device to a Run

The first example we will try is to anchor a switch to door in the architectural reference file. Yes…you can anchor through to the reference file AEC objects.

Select the AutoCAD Architecture Object Anchor tool and identify your switch symbol and the object you want to anchor. Then press to continue and identify the door you want to anchor the switch to.

Next, we need to simulate the architect moving the door in the floor plan file. To do this I will use the Edit Xrefin- Place command available on the menu.

Move the door you anchored to along the wall to a new location and save the changes back to the reference file.

Your switch should automatically move to the new door location.

Try it for the emergency exit light moving with the door too! You might have to edit some of the run linework on this one! Try it for a ceiling diffuser or a light fixture moving with the ceiling grid.

To remove anchors you can use the grips provided to release the anchor.

Posted in Building / AEC | No Comments »

Adding base AutoCAD menus to the AutoCAD MEP user interface

Monday, September 24th, 2007

You noticed that menus available in the AutoCAD user interface, such as the Viewport or Dimension menu, are not available in the AutoCAD MEP user interface, and you want to add them.

 

You need to transfer the AutoCAD menu items from the acad.cui file to the abs.cui file. Follow these steps:

  1. Right-click any of the toolbars. Click Customize.
  2. Expand the Customize User Interface dialog box by clicking the arrow located in the lower-right corner of the dialog box.
  3. Click the Transfer tab.
    Note that there are now two panels in the Customize User Interface dialog box: a left panel, “Customizations in Main CUI,” which contains the settings for the current user interface, and a right panel, “Customization in New CUI File,” which can be used to load external CUI files.
  4. Click New CUI file menu > Open.
  5. In the Open dialog box, browse to the following file:
    • On Windows XP:
      C:\Documents and Settings\\Application Data\Autodesk\ACD-MEP 2008\enu\Support
    • On Windows Vista:
      C:\Users\\AppData\Roaming\Autodesk\ACD-MEP 2008\enu\Support
  6. Open the file.
  7. Expand the Menus item in both the left and right panels.
  8. Drag the Dimension menu item from the right panel (acad.CUI) into the left panel(abs.CUI). Note that the Dimension menu item is now available in both columns.

If you want to change the order in which menus are displayed in AutoCAD MEP

  1. Click the Customize tab.
  2. Select the Current workspace and click Customize Workspace.
  3. In the Workspace Contents panel, expand the Menus items that are not highlighted in blue.
  4. Drag the Dimensions menu, currently at the bottom of the list, to the desired location between the other menu items.
  5. Click Done.
  6. Click OK.

These changes are stored in the current workspaces and saved in the Main Customization file, which for a default installation of AutoCAD Architecture is .

If you want to use this customized configuration on another computer, replace the Main Customization file on the target computer with the customized one.

Posted in Building / AEC | No Comments »

New Build for Revit MEP 2008

Friday, September 14th, 2007

This download is the most recent build for Revit® MEP 2008 software as part of the AutoCAD® Revit® MEP Suite 2008 software product. The install will look to see if there is a previous installation of Revit MEP 2008 on the computer, and if there is, it will uninstall it before it installs the new build.  This build was released Aug. 29, 2007.

Download new Revit MEP 2008 Build Here

Downloads are applicable only to licenses under subscription, worldwide.

You can also download it and use it as an evaluation program for 30 days. After 30 days, it will become a viewer to view RVT files.

Files saved in new releases of this product are not compatible with previous releases. However, files saved in the same release are compatible across different build numbers.Improvements made in the current Web Update #2 build (20070829_2300):

  • Room Tags on Copy/Monitored Rooms no longer return question marks in certain situations.
  • Improves stability when using the Split Tool on Pipes or Ducts.
  • Multiple Sprinkler Systems can now be copied more consistently.
  • Improves stability when modifying the shape of an Elbow with an open end.
  • The length override for Duct Transitions remains consistent after changes to the connected layout.
  • Improves stability when generating ductwork from a mirrored air system.
  • Improves stability when demolishing a duct with two connected takeoffs.
  • Improves stability after receiving a corrupt element warning when opening a project.
  • Publish to DWF™functions when Rooms are present and are clipped by the viewport.
  • Improves stability when saving a Project with a linked DWG™file that contains an image.
  • Improves stability when applying a view template to a sheet view.
  • Working on Windows Vista™operating system, allows the ability to write to revit.ini, licpath.lic, KeyboardShortcuts.txt, and the Journals folder.
  • Line-based families contained in a group are no longer flipped when the group is mirrored.
  • Improves stability when importing group into Titleblock family.
  • Allows the ability to export renderings to TIFF format.
  • When temporary dimension text too small to read, user can adjust the size of the font through Revit.ini.
  • Linked DWG file added by another user will now show up in Manage Links after reload latest.
  • “Relative” spot elevation updates automatically with the change in Level elevation.
  • When exporting to DWG file, overlapping lines that share a point are no longer missing in the resulting DWG.

Posted in Building / AEC | No Comments »