Como controlar a unidade de representação na tag

September 8, 2010 Creating Custom Diffuser Tag

August 19, 2010

How to control the unit representation in tag?

Sometimes, users would like to customize the tag representation such as units, rounding, and unit symbols as per the locale structural engineering custom, e.g. for the below tag,

There are 3 parameters need to be labeled – Depth, SpaceNum, Panel Point Load. And the type for them is defined respectively as:
Depth: Length
SpaceNum: Integer
Panel Point Load: Force
Users would like to report Depth in inches, and no unit symbol show up; use N for the SpaceNum units; use K for the panel point load units, and the precision for it should be one decimal, just like,



However, as we all know, unit settings in Revit will follow the ones that set in project environment rather than in family editor. This is defined by default in the unit setting and it is unchangeable, see below,


In this case, even if we set the units well in the tag family, when users use it in project, they have to change the units setting in project to match to the tag representation.

However, for the tag family, there is an option "Use project settings" for the parameter's unit format which can be used to decide whether project unit setting or family unit setting to be used. This could be defined as below,


08 de setembro de 2010 Criando Custom Tag difusor


19 de agosto de 2010



Como controlar a representação de unidade na tag?

Às vezes, os usuários gostariam de personalizar a representação tag tais como as unidades, o arredondamento, e símbolos de unidades como por o costume de engenharia estrutural localidade, por exemplo, para a tag abaixo,







Existem 3 parâmetros precisam ser rotulados - Profundidade, SpaceNum, Painel de carga pontual. E o tipo é definido por eles respectivamente:



Profundidade: Comprimento



SpaceNum: Integer



Painel de carga pontual: Force



Usuários gostaria de relatar a profundidade em centímetros, e não mostrar-se símbolo da unidade, uso de N para as unidades SpaceNum; K usar para o painel de unidades de carga ponto, a precisão e por isso deve ser uma casa decimal, assim como,



















No entanto, como todos sabemos, as definições da unidade no Revit seguirão os que estabelecem no ambiente de projeto ao invés de no editor de família. Isso é definido por padrão na definição da unidade e é imutável, veja abaixo,















Neste caso, mesmo que definir as unidades também na família tag, quando os usuários usam no projeto, eles têm que mudar a configuração de unidades do projeto para coincidir com a representação de marcas.









No entanto, para a família de marca, existe uma opção "Usar configurações do projeto"para o formato do parâmetro da unidade que pode ser usada para decidir se a configuração do projeto da unidade ou unidade familiar configuração a ser utilizada. Isso pode ser definido como abaixo,
Obrigado

We all know that not all out of the box Revit MEP content meets our company standards, and often that is the result when we are talking about the diffuser tag in RMEP.
I have created a short video on how you can modify the OOTB diffuser tag to pull the neck size and type mark parameters from the diffuser itself.                                                                                                    The finished tag will look like this:

Here is the link to my youtube video. Creating Custom Diffuser Tag
September 8, 2010Creating Custom Diffuser Tag
We all know that not all out of the box Revit MEP content meets our company standards, and often that is the result when we are talking about the diffuser tag in RMEP.
I have created a short video on how you can modify the OOTB diffuser tag to pull the neck size and type mark parameters from the diffuser itself.
The finished tag will look like this:
Here is the link to my youtube video. Creating Custom Diffuser Tag

September 02, 2010

Workset Visibility in Revit 2011

Has this ever happened to you?



"Frankly, I’m annoyed by having to turn on my workset every time I create a new view. "



When a workset is created, there is an option to make it not visible by default. If you've run into the scenario above, this box was unchecked when the workset was created.



One work-around is to create a new workset that is 'Visible in all views', and then delete the original workset. When you delete a workset that contains elements, you have to option to move those elements to another workset, so you can move them to the newly created workset. However, be aware that when you do this, those elements may be visible in views where they weren't previously visible (assuming their category is visible in those views). So, you may need to 'clean up' after yourself, to turn off the worksets where they're not needed.



New in 2011 is the ability to change your mind about the workset visibility default. In the worksets dialow, there is a new column titled 'Visible in all views' where you can toggle this setting.






This setting is then tied to the 'Use Global Setting' option in a view's visibility graphic overrides settings. The Global Setting will indicate Visible or Not Visible as appropriate. You also have the options of Show and Hide as in previous releases.












I have advised against unchecking the 'Visible in all views' option prior to 2011, because if a file had worksets marked as such, there was no way to turn on the worksets when linked into a host model. However, now with 2011, you have the ability to control the visiblity of worksets in linked files.






However, I would still advise to exercise judgement when making something not visible by default. Consider a scenario where roof drains are on a workset marked not visible in all views in the architectural model. The plumbing designer, not knowing any better, doesn't go looking for roof drains in toggled off worksets.. he just expects to see them if they exist in the project. IMO, it is better to have things visible, then turned off by the 'view owner' if/when not needed.



Better control of workset visibility, especially for linked files, is a great enhancement in Revit 2011.

September 08, 2010

Connecting to a Panel

Here's a quick tip that may simplify your circuiting process.



When selecting a panel while circuiting, you may have noticed that the order of the panels on the Options bar is ordered based on the distance from the selected devices to the various panels... i.e., panels on the top of the list are closer than panels near the bottom. As you circuit in various areas of your building, this order likely changes:






With the order changing, it may require a bit of dilligence to make sure you are selecting the proper panel.



However, did you know that instead of selecting from the list, you can select the panel from within the model... even if it is in a different view?



If you are going to be circuiting primarily to a certain panel, you can create a separate view with just that panel in it, then, as you circuit, select the panel in that view (instead of from the list). For example, if you have already defined all your circuits, and now need to select the panel to connect them to, you may configure your views as shown below.






Now, as you circuit your various devices, after you click 'Select Panel', instead of selecting from the list, you click in the panel view to activate it, then select the specific panel. No more paning in the model to find the panel, or searching in the list.

September 14, 2010

UPDATE – Revit MEP Error: Invalid Duct Fitting K-Factor Database

Back in February, I posted an article with a suggested fix to this error that occurs in Revit MEP when selecting or drawing ducts, fittings, or equipment. The fix involved running Revit MEP as an administrator. In other cases, when this issue occurred in 2009/2010, we had users uninstall/reinstall both versions, which resolved the problem most of the time.



Recently, we have had several reports of this error happening in 2011, and in most cases, neither of these recommendations have fixed the problem.



Generally, this error is a result of a 3rd-party DLL not being registered properly when installing Revit MEP 2011. Following are the steps to manually register the DLL, which should clear the above error:







1.Click on Start…Run

2.Type regsvr32 "C:\Program Files\Autodesk\Revit MEP 2011\Program\ASHRAEDUCTDLL.dll" in the window

3.Click OK

A dialog box indicating that the DLL was registered successfully should appear. If not, please proceed to the steps below.



1.Click on Start…Programs..Accessories

2.Right-click on Command Prompt

3.Select Run as…

4.Select Administrator

5.In the command prompt, type CD \ to get back to the root of C:

6.Type cd Program Files\Autodesk\Revit MEP 2011\Program

7.Type regsvr32 “ASHRAEDUCTDLL.dll"

After confirming that the DLL registered successfully, launch Revit MEP to confirm that the error no longer appears.