Forums >> Revit Structure >> Technical Support >> Creating a Beam Family Where Each Type has a Determined Length
|
|
active
Joined: Fri, Aug 19, 2016
0 Posts No Rating |
I'm trying to create a beam family where each type has the same profile but each type has a different set length. I tried to use the length parameter, but when I load the family into my project it ignores the length parameter and requires me click and drag like any other beam. Is there a way to lock the lengths of the types so that I don't have to manually adjust each time I want to use one of these beams?
|
This user is offline |
|
|
|
site moderator|||
Joined: Tue, May 16, 2006
13079 Posts
|
Length must be an instance parameter and that makes sense.
|
This user is offline |
|
|
active
Joined: Fri, Aug 19, 2016
0 Posts No Rating |
So is there another method you'd recommend?
I exported a .stp file out of solidworks, imported the .stp file into AutoCad, saved it as a .dwg and then imported those files as different types into a beam family. I controlled which .dwg file I want to see with yes/no parameters. I essentially have 7 set length beam types that I can select from just like any other beam family.
The model is a bit slow though, so now I'm wondering there is another way to accomplish this in order to keep my file size down and my model speed up.
|
This user is offline |
|
|
active
Joined: Fri, Aug 19, 2016
0 Posts No Rating |
Here is the family I created if you want to take a look:
|
This user is offline |
|
|
site moderator|||
Joined: Tue, May 16, 2006
13079 Posts
|
I was too short in my answer.... I meant that the family you built is using an instance parameter for the length and that is typical. Why would you make it be a type parameter? That defeats Revits methodology. You pick a beam type that has type based section and the legth is always instance because there are too many values it could be to be type based.
|
This user is offline |
|
|
active
Joined: Fri, Aug 19, 2016
0 Posts No Rating |
Not sure how I can make the length parameter type based in a structural beam family. It's not a parameter I can edit.
I can load my profile into a generic family and make a type based length parameter, but then the members won't schedule correctly.
Please correct me if I'm wrong (since that's why I came here), but it seems like I can have it one way or the other, but not both.
|
This user is offline |
|
|
site moderator|||
Joined: Tue, May 16, 2006
13079 Posts
|
You are correct if you want this beam to schedule with other beams. Reit has built in parameters in many categories and if you want to use those parameters, you have to play by their rules. Changing categories is not a solution as you have discovered. You could always use the beam template and add a new shared parmeter called something other than length. The beam would then schedule with other beams but you will have two different "length" values to contend with.
Again, why re-invent this? The instance based, built-in parameter is logical and less problematic. Maybe if you tell us why you want to do this, we could recommend a better process.
|
This user is offline |
|
|
active
Joined: Fri, Aug 19, 2016
0 Posts No Rating |
I don't disaree with you about the beam family not being faulty.
I'm trying to model parts - they each have specific lengths and part #'s. My ultimate goal is to be able to place these parts (which are essentially beams in my head) into my model and then have them schedule by level, part # and quantity. There are penetrations in each type that are placed in very specific locations, so I want those to model at fine detail, I don't think I can just have a click and drag type family. Hopefully I'm explaining myself well enough.
My disadvantage here is that I recently switched from a job designing large scale steel buildings to a position that is more mechanically driven. I'm used to everything being modeled as beams, columns and braces and they didn't require part #'s or predetermined lengths.
I'm trying to figure out how my skills in the structural engineering design world can translate to the mechanical design field.
|
This user is offline |
|
|
site moderator|||
Joined: Tue, May 16, 2006
13079 Posts
|
OK - This helps.
Are these really beams and are they scheduled with other beams? Or could they be something else?
A better soultion may be to use a group. Groups are transportable between projects and can be stored in a library. You could build your group in a project using your beam stetched to the correct length then add face based voids to cut your holes. A type based tag could identify this and the beam could hold any other data that needs to be scheduled. This goup can be loaded and placed wherever you need it.
If this 'beam' is really something like a pre-enginerred frame, then it is not really a beam.
|
This user is offline |
|
|
active
Joined: Fri, Aug 19, 2016
0 Posts No Rating |
They could be something else, certainly. They are essentially rail sections that are tacked on to a pre-engineered frame. They need to be scheduled, but not necessarily with the actual beams.
If I have hundreds of the groups in my model, using the method you suggest, how will that affect size and speed of the model?
I've used Revit to design 40 story steel structures with no performance issues, but as I'm designing what is essentially a compressed 10 story steel structure, I'm find the models are getting bogged down. I'm hoping my method for creating these parts was wrong and that your solution will help speed me up.
|
This user is offline |
|
|
|
site moderator|||
Joined: Tue, May 16, 2006
13079 Posts
|
Two comments.
If these are NOT beams then just use your generic model (assigned to structural category) and have the parameters you need to schedule.Groups will act pretty much like famies as far as file size and performance goes. But as I said, since it is not a beam, you just might use your family with it's own 'length' shared parameter.
|
This user is offline |
|
|
active
Joined: Fri, Aug 19, 2016
0 Posts No Rating |
I appreciate the time. Thanks for the discussion and the advice!
|
This user is offline |
|
|
|