Tuesday, March 3, 2015

Ranged Expressions using Design Script in DynamoBIM

Generating a number sequence in DynamoBIM using Design Script is easy. It is also easy to forget the "format"...

and then you start asking yourself...what goes first... the amount of steps or the start of the sequence...?

The following image summarizes (most) of what you need to know to generate a ranged expression in DynamoBIM.

Use this image as a cheatsheet next time you want to generate a number sequence in DynamoBIM!

Monday, March 2, 2015

Ever wanted to use the Revit "Repeater" Command on a Loadable family other than an Adaptive Component?

Currently in Revit you are only allowed "repeat" an adaptive component family.

What if you want to repeat a planting family or some other family other than an AC along a path?
It is possible with DynamoBIM!
Its easy and it only takes 6 nodes. Follow the steps below.

  1. Draw a curve or path that you want. 
  2. Create or load any loadable family you want into your project ( in this example a planting family was used)
  3. Open DynamoBIM from your project and add the 6 nodes you see in the image.
  4. Click run and DynamoBIM will repeat your planting family.


In Revit along you ....could nest the planting (or other non AC) family into an AC family and then use the repeater command. 
But the method above (that used DynamoBIM)eliminates the need to nest families into eachother and, as shown in the previous post, the number of repeated families is not limited to 200! So think about using DynamoBIM on your next repeater task and have fun repeating those Loadable families!

Sunday, March 1, 2015

Is the Divided Path and Repeater Limit of 200 in Revit a Problem? Want More? Use DynamoBIM!

Currently in Revit you are only allowed to divide a curve/path between 2 and 200. 
What if you want more divisions? Use DynamoBIM!
Its easy and it only takes 6 nodes. Follow the steps below.

  1. Draw a curve or path that you want. 
  2. Create an adaptive component (AC) that you want to repeat and load it into your project
  3. Open DynamoBIM from your project and add the 6 nodes you see in the image.
  4. Click run and DynamoBIM will repeat your adaptive component family as many times as you want. (The example shown has 300!) 


Good luck adding as many AC repeaters as you like!

Saturday, February 28, 2015

How to Set a Type parameter in a loadable family using DynamoBIM

Setting a Type Parameter in a loadable family is easy.
Its a bit different than Setting an Instance Parameter in a Loadable family.
If you are not familiar with how to "GET" a Type parameter in a loadable family see my previous post.

The "Family Types" node selects all the loadable family TYPES and therefore you could only "SET"  that family's TYPE parameters. SO if you tried to SET an instance parameter from the Family Types Selection Node it would not work... because it only sets types....
The image will summarize this process.



Good Luck Getting and Setting Type Parameters for Loadable families.

What about System families you ask?
In my next post I will explain how to get and set parameters (both type and instance ) from a System family

Tuesday, February 24, 2015

How to set Pilaster Height equal to Grade Beam depth using DynamoBIM (or how to drive an instance parameter with a type parameter in a loadable family)

Someone over at bim forum asked if there is a way to set Pilaster Depth equal to the Depth of a grade beam.
The simple answer is yes.

There are many ways to do this but the simplest way would be to change the grade beam from top justification to bottom and then just get and set parameters....

This example you will need to "get" the depth of the grade beam, which is a type parameter from a loadable family and set it to the pilaster ht, which is an instance parameter of a loadable family. How do you get a type parameter from a loadable family?
Well... take note that....

The "All elements of Family type" node selects all the Loadable Family INSTANCES and therefore you could only "get" that family's instance parameters.

The "Family Types" node selects all the loadable family TYPES and therefore you could only "get"  that family's.................TYPE......... parameters.

See the image and good luck getting and setting type and instance parameters to eachother!




Sunday, February 22, 2015

Want to Select all Loadable Revit Family Instances Using DynamoBIM? Its easy if you could understand the naming used within each node...

I created this post because I wanted to help clear up some of the confusion when DynamoBIM users want to select all the Loadable Revit Family Instances using DynamoBIM.

Its easy and it only takes 2 nodes but the naming found within each node could be very confusing. So first add a Family Type selection node, select the family type, and then wire that to either the FamilyInstance.ByFamilySymbol or All element of Family Type node and click run...

THATS IT!...Well...there is still the issue of the naming....

This process is summarized in the image below and notice... from the image it is clear that the nomenclature used in DynamoBIM is very confusing because two different words could mean the same thing...


The question is....why is DynamoBIM like this? I have no idea.

Stay tuned to this blog....
I will try my best to help clarify confusing naming conversions, in future posts, as I encounter them.  


Saturday, February 21, 2015

What are the real Category Names in DynamoBIM? ... It Depends....

Yes it depends on what node you are using.
For example if you want to use the Category as a string for input into a Category.ByName Node then you would have to NOT call it "Rooms" you would have to call it "OST_Rooms"

To confuse you further the Category names shown in the Category selection node do NOT use the OST prefix.

Confused? I was. Hopefully this image will sum it up for you.

The real question is how was the general DynamoBIM Community supposed to know that the Built in category name should use the "OST_" prefix in some cases and not in others... or for that matter that the prefix was even called "OST_" .... really..... 

As I understand it, "OST_" was a "hold over" from API language that DynamoBIM relies on. But at the very least the names should be consistent... IMHO 

Dont get me wrong I love DynamoBIM and it has made my Revit Life very productive. I am just trying to clarify the "very" confusing DynamoBIM naming conversions.