Elevation From Level. Is their any way to use it as part of a formula?

[jamiemarshallWRH9M]

Hey all,

I'm just trying to find a way to access "Elevation From Level" and use it as part of a formula. Essentially I want to set the height of the "Fly Killer" family via the EFL, which then drives a forumla in the nested socket making it appear at the correct height.

Has anyone found a way to make this work?

Thanks

[jay_colc]

Unfortunately this is not possible but has been noted on an Ideas Board

Elevation from Level - Use in Family Formulas - Autodesk Community

[jamiemarshallWRH9M]

Well that is a shame!

Given how long its been since the original suggestion as well I doubt theirs much hope of this happening anytime soon

Thanks.

[barthbradley]

Sure you can access "Elevation From Level" and use it as part of a formula.  Whether or not it can be used to drive a "Fly Killer" is another matter.  Explain in detail what it is you are trying do.  

[jamiemarshallWRH9M]

I'm just trying to find a way to access "Elevation From Level" and use it as part of a formula.

I need to take this value and feed it into the "Fly Killer" family with a value so it can be used as part of calculations in there

[jamiemarshallWRH9M]

Bump

[jamiemarshallWRH9M]

😅 

[Mike.FORM]

Add a new parameter in the fly killer family you want to use in your formula.

Then add another parameter in the host family (named same or different, doesn't matter) that dimensions from the level up to a reference plane that has the fly killer family locked to. Then link that parameter to the parameter in the fly killer family using the little grey box.

Then whatever value you you have in the host family will push to the fly killer family and drive the formula.

You can do what you want, you just can't do it using the built-in "Elevation from Level" parameter.

[barthbradley]

So, my understanding is that you want to drive the Offset from Level of one component (let’s call it “A”) based on another component’s (let’s call it “B”) Offset from Level.  So, “A”’s EFL is contingent on “B”’s EFL.  Since EFL is a Project Parameter, this relationship can only be made in the Project Environment. So, you are not talking about a nested component obviously.   

If that's accurate, what about pulling a dimension between the base of “B” and the Level “B” is hosted to and labeling that dimension with a Global Reporting Parameter (let’s call it “B EFL”).  Then pull a dimension between the base of “A” and the Level “A” is hosted to and labeling that dimension with a non-reporting Global Parameter (let’s call it “A EFL”).  “A EFL” =(B EFL+[X’-X”]).  

[jay_colc]

Bump 😉

[jamiemarshallWRH9M]

Thanks for your help.

Unfortunately I don't think that will work for us as it would need to be a nested relationship.

Thank you though.

[Mike.FORM]

Edit: Never mind, I think I read your post wrong. You are saying you want it to be a nested relationship.

Do what I had stated in my first post.

The created parameter controlling the height from level of the nested family (so it can be used in a formula) is linked to a created parameter in the host family.

[jamiemarshallWRH9M]

Yes. In fairness I'm probably not explaining myself very well either. Let me give it another shot.

At the top tier of nested families I've got my "Combined Fly Killer" family loaded into the scene. This is where I need to be able to set my Elevation by Level. 

Inside that family I have the fly killer itself modeled, a separate loaded in family which is just a plug socket, and a variable called "Electrical Connection Height". 

What I want is for when my Fly Killer is at "EbL" or 1800, and my "ECH" is set to 2000, I want to do "ECH-EbL", and offset my plug socket off the reference plane by 200, meaning that in the main project it will be displayed both at the correct EbL but the socket is also moved correctly.

The heights in my project are not always set the same so I can't have a bunch of preset heights in there ready to go. Ideally I don't want to be setting this twice, once in the "EbL" and with a second variable as I know they will eventually be different from each other when someone forgets to change them both.

Having access to "EbL" really would have been ideal but I don't think it is possible anymore like this.

[Mike.FORM]

Why not just do it like this. You shouldn't need a formula, both items heights are controlled independently. The test family is attached.

If you want the ECH to always be 2000 then leave it as a type parameter. If you want EBL to be different by instance then make the parameter instance based.

[jamiemarshallWRH9M]

Hey,

Thanks for that Mike. This was my first solution for this problem as well. Why over complicate things when theirs such a simple answer!

Unfortunately it got shot down when bought to the wider team. I need to apply this solution to hundreds of previous families, meaning they would go from models created in the actual family, to a family nested in a family, which then gets moved as one big chunk up and down. Not to mention having to pass through parametric values again.

Thank you though, it is appreciated 🙂

[Mike.FORM]

Alright, here is the more complicated version. The fly killer family is workplane based and hosted to the reference plane controlled by EBL. EBL and ECH is pushed to the nested family which has a parameter called "offset" which uses the formula ECH - EBL.

[barthbradley]

What about Grouping (not nesting) the Components together in the Project Environment, then place the Group and set the Origin Level Offset for the Group Instance.  The Elevation from Level for the Individual Components will be correct.