Automated Handrail using Frame Generator with iLogic rules based on a sketch

[fichri17]

Hi all,

I`m trying to look into if it is possible to create a set of rules that makes me generate a HANDRAIL based on certain specifications from a 2D or 3D sketch... 
I can make a profile(s) in the library for Frame Generator so that I get the rails and the kickplate form the Frame Generator.
What I want also is my code to insert a specific part in a corner based on the angle. Say that I have a 90 deg turn in the sketch, then I want to cut back from the corner say 150 mm in each direction and insert a part from the library named ex Corner90.ipt

Anyone know any tips for this or can point me in the direction of something ?

-Frank

[A.Acheson · Accepted solution]

Hi @fichri17 

The frame generator AddIn doesn't have an API so you have no way to control its function.  This would need to be done without frame generator. If you want to do this without frame generator then can you share some sample assembly to work with and some images? Other members might be able to help.

[CCarreiras]

Hi!

First, create your model in the traditional way.

Then create/rename parameters to create a parametric model (Change parameters to check if the model resist to the changes.)

At the end you can use iLogic to create some tweaks in all model (not specifically at the frame generator only)

[John_L_Hermosa]

I just created a macro to make a handrail. It makes the skeleton or the model, the user can select the best of the options.

https://youtu.be/sPhljXibVSo?feature=shared 

[fichri17]

That looks great @John_L_Hermosa ‌‌
Actually just what I was hoping to achieve...
Any possibility of getting some insight into how the iLogic for that is set up ?? 😉

Br,
Frank

[John_L_Hermosa]

Hi, This is made via macro VBA, no Ilogic. But I think that is not so different.

[fichri17]

Okay thanks @John_L_Hermosa .

I am not so into macro VBA, could you be interested in sharing your script ?


Br,
Frank

[John_L_Hermosa]

Unfortunately I can't share the code because I made it for the company where I work and the code belongs to the company. But I can advise you on what you need.

[CCarreiras]

Like i said...

A parametric model with some basic iLogic rules is more than enough to build that rail...

... and it's not needed great VBA codes.... and frame generator will work for these kind of cases...

 

[fichri17]

I see.

Actually I do not have an issue with creating the handrail itself, the issue is mostly with using lines in a sketch as basis for where you want the handrail.

So if you can point me in the right direction with this, I would really appreciate it.

Br,
Frank

[CCarreiras]

How can i help you if i don't know what you have now, how you did it?

place the model and we will see.

[fichri17]

Hi, 

I can not share the IPT file (company content), but as you can see in the screenshots, I have made the configurations for the different types of handrails.
So basically all I need is the link between this and "pick lines/edges in sketch"
In addition I were looking for the implementation of corners in the handrails based on the sketch, in other words that the handrails follow the entire length of the sketch, but that I think I can manage if I get a fix for the question above....

Br,
Frank 

[CCarreiras]

The Frame Generator will work well regarding dimensioning the components based in the sketch dimensions.
You can use it for the overall parts that are always in the model, with the same family, size, etc.

To suppress/unsuppress the parts, you have to do it outside the frame generator sub assembly* (but you can use components created/controlled by the FG sub-assembly, but placed in the main assembly).

*as mentioned, the frame generator module doesn't have the API opened to use in iLogic for change members, resize, suppress etc, etc...

If you need to change the family components, you cant use Frame Generator, you have to use custom modelled parts.

As an advice: usually we would start to create a unique supermodel with all the options available, but usually it's better and easier to have more than one model to achieve specific situations. You end to have a less complicated models and easier to control, less bugs... etc

When working we just have to open the respective model for the specific situation we need in that job.

Sometimes the rules and conditions applied to a model type will complicate the rules to another model type, but when separated in two different specific models, they are both very easy to set.

So... think about have a couple of simple models instead of a complicated and buggy supermodel.