Detail Symbol Formula?

[Anonymous]

Attached is an example of what I will be using to ask this question.

I am part of an electrical firm trying to set up Revit. We are primarily an AutoCAD user, but I have been trying to get all of our symbols to become effective Revit Annotation/Detail families.

One of our symbols is a parabolic light that has different number of cells. I'm trying to make a detail family for this kind of light. My first thought on how to go about this was to use the cell lines (the dark purple ones) as an array, then use parameter formulas to calculate the number of cells based on the dimensions of the light and/or other electrical information. I tried out several different ways to try to accomplish this, but the formulas I use don't seem to be working.

I don't currently have a Revit family to provide that would be useful, so the attached image is all to really go off of. I also don't have a Revit 3D model to provide because we are only working on symbols at the moment.

I was wondering if anybody else has ideas on how this symbol can be done. I want to also try to make it as simple as possible. I also want to avoid using Dynamo or any lisp-like programs (not sure what other terminology to use as a primary AutoCAD user.)

[Secttor]

Hi @Anonymous 

Here's what I did for you.. in terms of annotation rfa. and it's also attached.

I've did a 2 row and your choice number of columns configuration. It's not clear for me where the mid row/or 3'rd row height will come so you have to put it manually/link to your setup if there's no condition.

With the 3'rd row is the same theory..and I let it be a small challenge for you. 🙂

Same procedures also for a detail item.

Hope it helps.

[s.borello]

Just create all those symbols as individual detail items... you would then be able to nest each of them into your light fixture family and set up a visibility state for each so you can toggle which detail family to show.  I envision 1 parabolic light fixture family with several types to give you the graphic flexibility you are looking for. 

[Anonymous]

Thank you for your reply. I'll have to try this out to see if it'll work as intended.

[Anonymous]

I'll try this out as a last resort. My co-workers don't like having too many families for what is essentially the same symbol (with very minor differences).

[Secttor]

That's the power of being parametric..and also save size of the entire project by having smart arrays.

[scbunker]

---

@Anonymous wrote:

I'll try this out as a last resort. My co-workers don't like having too many families for what is essentially the same symbol (with very minor differences).

---

When families are nested into another family, the essentially disappear - unseen by the end user. I use nested families liberally to accomplish my goals. They are not saved-out into the library - they exist only within the family they serve. Most of them are one-off.

The above statement isn't true of Shared families. In general, avoid Shared families unless you specifically need it to be Shared.

Note: I'm not necessarily saying that @s.borello's suggestion is the best solution. Just that there's no real reason to avoid nested families if that's the best way to achieve your goal. 

[Anonymous]

---

@scbunker wrote:

---

@Anonymous wrote:

I'll try this out as a last resort. My co-workers don't like having too many families for what is essentially the same symbol (with very minor differences).

---

When families are nested into another family, the essentially disappear - unseen by the end user. I use nested families liberally to accomplish my goals. They are not saved-out into the library - they exist only within the family they serve. Most of them are one-off.

The above statement isn't true of Shared families. In general, avoid Shared families unless you specifically need it to be Shared.

Note: I'm not necessarily saying that @s.borello's suggestion is the best solution. Just that there's no real reason to avoid nested families if that's the best way to achieve your goal.

---

 I am not sure what you mean by this statement.

The biggest problem I have with nested families is that if you have a lot of variations with the same symbol, then you would just have a lot of families that you would need to maintain if there needs to be changes.